Dear P.O., On 31.01.2022 15:14, P.O. Jonsson wrote: ... cut ... > Why the urgency to push another ncurses library than the default on macOS?
There is no "urgency to push another ncurses library" here. One of MacPorts ports obviously caused a port of ncurses to be installed on my Apple (not sure when that happened, but I noticed it yesterday for the first time after updating the Apple operating systems and in that context had to update my MacPorts installation). Not sure why they did if there was one from Apple available anyway. It took me a while yesterday to figure out why compiling a universal ooRexx (from a pristine version of ooRexx from trunk) did not fail because unlike all other linking only the ncurses one failed. After finding the cause I tried to report this and ask for information, hints what to do about it such that XCode's SDKs ncurses would be used for linking, not the MacPort one (being installed in /opt/local/lib). Maybe there is a possibility in CMake to tell it to use a certain sequence to locate the libraries that would allow the SDKs libraries to be found before those ---rony P.S.: MacPort on my x86_64 is x86_64 only, trying to install all ports with "+universal" did not have the effect of getting universal versions of the MacPort ports. There are no links in the /usr branch to /opt/local/lib files. _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
