Rony,
thank you, we will make good use of it.
For the shebang issue you mention, I would suggest that we use /usr/bin/env
which is the common solution for portable and not hardcoded shebangs:
#! /usr/bin/env rexx
say date('L',732940,'B')
works great if rexx is on your PATH; also, makes it much easier to test with a
newer-than-installed rexx interpreter. We should probably move the samples for
unix to use that.
best regards,
René.
> On 30 jun. 2016, at 20:14, Rony G. Flatscher <[email protected]> wrote:
>
> René,
> On 30.06.2016 15:19, René Jansen wrote:
> ... cut ...
>
>> After that, I will look into package build and install. We cannot install
>> into /usr/bin after the latest security changes to MacOSX. We should
>> probably choose a new default location, in /Application. Any ideas are
>> welcome.
> As you may know, I have an Apple compliant installation of ooRexx on MacOSX
> which I have been installing together with BSF4ooRexx for quite a few years
> now.
>
> It has been badly bitten by Apple's "ruthless" changes (invalidating BTW all
> scripts that have the hash-bang line together with the "/usr/bin" path) to
> its latest operating system [I was able to fix that (still have to switch to
> a different installer to stop another stupid Apple warning frightening the
> users without a real need).]
>
> To make a long story short, if you look at the BSF4ooRexx sources, you will
> find the Iceberg installer definitions in
> "gui_installers\mac\Iceberg\ooRexx32withBSF4ooRexx.packproj" and
> "ooRexx32withBSF4ooRexx.packproj\ooRexx64withBSF4ooRexx.packproj". There is a
> readme-create-installer.txt in "gui_installers\mac\Iceberg\".
>
> You will see how the Application and Framework directories have been used for
> ooRexx (and BSF4ooRexx).
>
> However, there is still the need to link from the appropriate Application and
> Framework subdirectories into "/usr/local/bin", "/usr/local/lib" and
> "/usr/local/share/man/man1", such that ooRexx and BSF4ooRexx can be executed.
> [The Apple deployment rules would allow for installing different versions of
> ooRexx and/or BSF4ooRexx where the user can switch among those version quite
> easily.]
>
> To see how this is done, just look at the post- and preflight scripts for
> ooRexx, BSF4ooRexx or AOO-support in
> "gui_installers\mac\Iceberg\installation\scripts".
>
> If I can be of further help, please let me know.
>
> HTH,
>
> ---rony
>
>
>>
>>> On 30 jun. 2016, at 14:12, Erich Steinböck <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>
>>> I checked in a fix for macOS - to have it build again.
>>> It needs revisiting but it works for now. See if it stands up to scrutiny.
>>> The thing that is wrong with it is that it is not really nanotime,
>>> I don't think we really need nano resolution, using gettimeofday() should
>>> be fine, this is what we're using in TimeSupport.hpp also.
>>>
>>> I will replace it if I find something better.
>>> I suggest we switch to gettimeofday() for all architectures, not just for
>>> Mac. If there are no objections, I'd commit the following patch:
>
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape_______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
