>>>
>>> So running cmake with -DBUILD_OSX_UNIVERSAL_BINARIES=1 should already allow
>>> to create fat/universal versions.
>>>
>>> HTH,
>>>
>>> ---rony
>>>
>>>
>> Will try it out, not sure what effect this will have on the naming of the
>> dmg file. We will see.
> Please let us know.
>
So here goes:
On a Mac Running High Sierra I get the error message (lots of them, until
aborting)
In file included from /usr/include/sys/signal.h:82:
/usr/include/machine/signal.h:34:2: error: architecture not supported
#error architecture not supported
^
So it seems my Clang is not capable of building for the new architecture :-(
here my Clang info
POs-QuadCore-Mac-Pro:workspace po$ clang --version
Apple LLVM version 10.0.0 (clang-1000.10.44.4)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
On the Jeninks build machine I have not applied the fix but I get other weird
errors -> to be found out later
Installing and running an arm64 ooRexx on High Sierra/Intel built on Marks M1
machine I get the error message that it is built for the wrong architecture,
which is logical.
Installing and running a „fat“ binary ooRexx High Sierra/Intel built on built
on Marks M1 machine I get the following error message
POs-QuadCore-Mac-Pro:~ po$ rexx
dyld: Library not loaded: @rpath/librexx.4.dylib
Referenced from: /Applications/ooRexx5/bin/rexx
Reason: no suitable image found. Did find:
/Applications/ooRexx5/bin/../lib/librexx.4.dylib: cannot load
'librexx.4.dylib' (load command 0x80000034 is unknown)
/Applications/ooRexx5/bin/../lib/librexx.4.dylib: stat() failed with
errno=1
Abort trap: 6
So there is still things to do. Any ideas welcome
> ______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
