Ahh. that's good info. There is something somewhere that still expects that COMID on macOS is s5abi or, at least, !=gcc3. That gives me some hint to what to look for.
> On Dec 17, 2020, at 11:34 AM, Rony G. Flatscher (Apache) <r...@apache.org> > wrote: > > On 14.12.2020 13:33, Jim Jagielski wrote: >>> On Dec 12, 2020, at 5:21 AM, Matthias Seidel <matthias.sei...@hamburg.de> >>> wrote: >>> >>> Hi Jim, >>> >>> I have been able to open docx with your version (en-US) on Big Sur. >>> However, I am not sure if this bug ever applied to 4.2.x. >>> >>> The Extension Manager is still broken. But similar behavior is to be >>> seen in 4.2.x on Windows, so the UNO problem is not mac specific. >>> >> Yes... I am also looking into issues w/ 4.2.0-dev and check for updates >> (main level) > > Ah, o.k. that might explain this. Got a minute so tried to test 4.2 beta > w.r.t. issue 127966 [1] > and was not able to get ooRexx functional. When trying to register the oxt > package manually with > unopkg, I got this error message: > > wu114216:~ rony$ "/Applications/OpenOffice.app/Contents/program/unopkg" > add -f --shared > /Library/Frameworks/BSF4ooRexx.framework/Libraries/ScriptProviderForooRexx.oxt > dyld: Library not loaded: @_______URELIB/libuno_cppu.dylib > Referenced from: /Applications/OpenOffice.app/Contents/MacOS/uno.bin > Reason: image not found > > ---rony > > [1] MacOS: Current directory wrongly set to root directory "/" for scripts: > <https://bz.apache.org/ooo/show_bug.cgi?id=127966> > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
