Re: [Oorexx-devel] Question ad MacOSX El Capitan and creating symbolic links in /usr/* ...

Are you able to get around the rexx.cat by coding an NLSPATH in the environment? So we would need PATH, LD_LIBRARY_PATH, and NLSPATH. As to opening a bug, seems like the right thing to do. > On Mar 13, 2016, at 11:13 AM, Rony G. Flatscher > wrote: > > Hi Bruce, > >

Re: [Oorexx-devel] Question ad MacOSX El Capitan and creating symbolic links in /usr/* ...

Hi Bruce, you are the best! :) Thanks to your findings I got a few ideas to test (copied the quarantined /usr/bin and /usr/lib entries to /usr/local/bin and /usr/local/lib). Can run the ooRexx interpreter again. There is a problem still with dynamic loading the BSF4ooRexx dynalib from Java's

Re: [Oorexx-devel] Question ad MacOSX El Capitan and creating symbolic links in /usr/* ...

Later it says: "Scripting Languages Developers using Perl, Python, Ruby, or any other scripting languages that ship with OS X, are encouraged to manage their own installations of the language and dependencies in /usr/local/. When distributing programs written with a scripting language,

Re: [Oorexx-devel] Question ad MacOSX El Capitan and creating symbolic links in /usr/* ...

I just googled “Library SystemMigration History” and got this as the second hit. Where it says: The following directories can only be

[Oorexx-devel] Question ad MacOSX El Capitan and creating symbolic links in /usr/* ...

Not having worked much on Apple lately, I was informed by students who tried to install ooRexx for MacOSX by installing BSF4ooRexx for MacOSX, that the installation does not work "all of a sudden"! Exploring this problem a little bit, it turned out that students having MacOSX prior to "El