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
java.library.path, will have
to check on that. (As it is night over here, I will have to go and analyze this
further ASAP.
---
However, there might be a little problem with ooRexx' code to locate rexx.cat,
it seems ooRexx looks
in "/usr/bin" only, judging from the error message: "97 Cannot open REXX
message catalog rexx.cat.
Not in NLSPATH or /usr/bin".
In the light of Apple's move (non system binaries and libraries need to go into
"/usr/local"
starting with 10.11, "El Capitan"), should I open a bug report for ooRexx for
that particular error
on MacOSX?
---rony
On 13.03.2016 18:38, CVBruce wrote:
> 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, developers
> are encouraged to
> bundle the language runtime and any required components into a
> self-contained binary.”
>
>
> I don’t know that “self-contained binary” is compatible with the architecture
> of ooRexx. On the
> other hand, a bundle (which can be many files in a directory structure) may
> be.
>
> Bruce
>
>> On Mar 13, 2016, at 9:53 AM, Rony G. Flatscher <rony.flatsc...@wu.ac.at
>> <mailto:rony.flatsc...@wu.ac.at>> wrote:
>>
>> 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 Capitan"
>> (MacOSX (10.11)) installed have no problems whatsoever. So the culprit seems
>> to be the latest
>> MacOSX, 10.11.
>>
>> One student reported the same problem using a "pure" ooRexx installation
>> from Sourceforge!
>>
>> Inspecting my Apple having the latest upgrade and path (MacOSX 10.11.3)
>> installed it turns out that
>> the previously installed and functioning BSF4ooRexx was rendered useless in
>> the meantime, the oorexx
>> symbolic links to binaries and libraries (all residing in "/usr/bin",
>> "/usr/lib" and even
>> "/usr/include") have been moved to some
>> "/Library/SystemMigration/History/Migration-some-UUID-value/QuarantineRoot"!
>>
>> ---
>>
>> As spooky as this seems (an operating system update regarding installed,
>> working applications as
>> malware somehow, acting such that rendering it useless) the problem needs to
>> be fixed, if possible
>> at all, ASAP.
>>
>> On either developer list (oorexx and bsf4oorexx) there have been developers
>> showin up who have had
>> experiences developing on the Apple platform.
>>
>> So the question is, does anyone have any ideas what this causes and what a
>> possible remedy would be
>> for it? Possibly anyone who might have been able to re-install ooRexx or
>> BSF4ooRexx on El Capitan,
>> and if so, how?
>>
>> Thankful for any idea, hint and link!
>>
>> ---rony
>>
>> P.S.: Yes, I googled already, but somehow have not been able to get answers
>> that would help. One
>> remark was to the effect to deal with the ElCapitan "No-Tresspassing" tag,
>> without explaining what
>> this was meaning and where to find documentation about it.
>>
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
