Re: [Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[Mark Hessling]

Yes oorexx-config is used by any package that wants to use ooRexx as
part of the package's configuration stage, prior to building the
package's binary files. All of my external function packages use it. 
The alternative is to use pkg-config, but that requires more setup on
the developer's machine.

Cheers, Mark

On 17/7/21 3:04 am, CV Bruce wrote:
> I believe oorexx-config is a Linux-ism that you can include in a make
> file to populate variables with information about where various parts
> of oorexx can be found.
> Bruce
>
> Sent by Magic!
>
>> On Jul 16, 2021, at 9:02 AM, Rick McGuire  wrote:
>>
>> 
>>
>>
>> On Fri, Jul 16, 2021 at 11:41 AM P.O. Jonsson > > wrote:
>>
>> Dear Rony, just some thoughts.
>>
>> I did not run the script (yet) but is the intention to create
>> symlinks to /usr/local so as to avoid the need to modify the path?
>>
>> If the 2nd part is creating the steps necessary to „unlink" why
>> do you not create a shell script of those lines? After all the
>> user will not realize at the time of installation (linking) that
>> he might need them (much) later during an uninstall? (unlinking).
>> It would appear possible to create a static unlink script for the
>> default (/Applications/ooRexx5/bin,lib <-> /usr/local/bin,lib
>>
>> Can we hear from the developers what the skipped files (
>> callrexx1, callrexx2, libwpipe1.dylib, libwpipe2.dylib,
>> libwpipe3.dylib and oorexx-config.) are for? Can they be safely
>> removed from the installation on macOS? How does one go about it?
>>
>>
>> I'm not sure what oorexx-config is, but the others are the compiled
>> sample files. 
>>
>> Rick 
>>
>>
>> It is possible to delete these files from the (auto-generated)
>> script building the dmg in a post-process but that would be the
>> ugly way. IMO we should locate the places in CMakelists.txt where
>> those files are copied and fix the problem there.
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>>
>>
>>
>>> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher
>>> mailto:rony.flatsc...@wu.ac.at>>:
>>>
>>> Those who use ooRexx5 from Sourceforge on a Mac and who have
>>> followed the instructions will have
>>> ooRexx in "/Applications/ooRexx5".
>>>
>>> The enclosed Rexx script will create the link and remove
>>> commands that will make ooRexx5 available
>>> systemwide. Run it and copy & paste the output to create the
>>> links or remove them.
>>>
>>> If you have ooRexx5 installed somewhere else, adjust the script
>>> accordingly.
>>>
>>> ---rony
>>>
>>>
>>> ___
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net
>>> 
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>> 
>>
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> 
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> 
>>
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

-- 

* Mark Hessling, m...@rexx.org http://www.rexx.org/
* Author of THE, a Free XEDIT/KEDIT editor and, Rexx/SQL, Rexx/CURL, etc.
* Maintainer of Regina Rexx interpreter
* Use Rexx? join the Rexx Language Association: https://www.rexxla.org/ 


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[P.O. Jonsson]

> Am 16.07.2021 um 18:04 schrieb Rick McGuire :
> 
> btw, if you were properly using the information from CMake.txt to build the 
> .dmg, you would not be having this problem, since all of the install() 
> statements identify which elements of the build should go where. That 
> information is used by all of the other installer types (including the 
> Windows one, which is done without CMake builtin CPack support). 

I only use what make install produces (I merely pack the installation) so it is 
not me that is using the information in the wrong way, ANY installation of 
ooRexx for macOS will have these defects.

Let´s hunt them down (in cmakelists.txt) and fix them there.___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[CV Bruce]

I believe oorexx-config is a Linux-ism that you can include in a make file to 
populate variables with information about where various parts of oorexx can be 
found.
Bruce

Sent by Magic!

> On Jul 16, 2021, at 9:02 AM, Rick McGuire  wrote:
> 
> 
> 
> 
>> On Fri, Jul 16, 2021 at 11:41 AM P.O. Jonsson  wrote:
>> Dear Rony, just some thoughts.
>> 
>> I did not run the script (yet) but is the intention to create symlinks to 
>> /usr/local so as to avoid the need to modify the path?
>> 
>> If the 2nd part is creating the steps necessary to „unlink" why do you not 
>> create a shell script of those lines? After all the user will not realize at 
>> the time of installation (linking) that he might need them (much) later 
>> during an uninstall? (unlinking). It would appear possible to create a 
>> static unlink script for the default (/Applications/ooRexx5/bin,lib <-> 
>> /usr/local/bin,lib
>> 
>> Can we hear from the developers what the skipped files ( callrexx1, 
>> callrexx2, libwpipe1.dylib, libwpipe2.dylib, libwpipe3.dylib and 
>> oorexx-config.) are for? Can they be safely removed from the installation on 
>> macOS? How does one go about it?
> 
> I'm not sure what oorexx-config is, but the others are the compiled sample 
> files. 
> 
> Rick 
>> 
>> It is possible to delete these files from the (auto-generated) script 
>> building the dmg in a post-process but that would be the ugly way. IMO we 
>> should locate the places in CMakelists.txt where those files are copied and 
>> fix the problem there.
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>> 
>> 
>> 
>>> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher :
>>> 
>>> Those who use ooRexx5 from Sourceforge on a Mac and who have followed the 
>>> instructions will have
>>> ooRexx in "/Applications/ooRexx5".
>>> 
>>> The enclosed Rexx script will create the link and remove commands that will 
>>> make ooRexx5 available
>>> systemwide. Run it and copy & paste the output to create the links or 
>>> remove them.
>>> 
>>> If you have ooRexx5 installed somewhere else, adjust the script accordingly.
>>> 
>>> ---rony
>>> 
>>> 
>>> ___
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> 
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[Rony G. Flatscher]

Dear P.O.,

it is just intended to help those who wish to make ooRexx globally available to 
learn the ln- and
rm-commands to do so. It will not be done automatically, one would need to copy 
the commands and
then paste them to execute them.  :)

Even if someone would forget deleting the symbolic links, they would not do any 
harm. To remove all
broken symbolic links, one could use one of the suggestions from 
,
 like:

sudo find /usr/local -type l -exec test ! -e {} \; -delete


On 16.07.2021 17:40, P.O. Jonsson wrote:
> I did not run the script (yet) but is the intention to create symlinks to 
> /usr/local so as to
> avoid the need to modify the path?

The script only creates the commands it does not run them. In order to execute 
them you would need
to copy the output in the Terminal to the clipboard and paste the commands from 
the clipboard to
have them execute.

> If the 2nd part is creating the steps necessary to „unlink" why do you not 
> create a shell script
> of those lines? After all the user will not realize at the time of 
> installation (linking) that he
> might need them (much) later during an uninstall? (unlinking). It would 
> appear possible to create
> a static unlink script for the default (/Applications/ooRexx5/bin,lib <-> 
> /usr/local/bin,lib
>
> Can we hear from the developers what the skipped files ( callrexx1, 
> callrexx2, libwpipe1.dylib,
> libwpipe2.dylib, libwpipe3.dylib and oorexx-config.) are for? Can they be 
> safely removed from the
> installation on macOS? How does one go about it?

Rexx comes with samples that demonstrate how to use C to interact with Rexx, on 
Windows you would
find them in "ooRexx\samples\api". So they can be safely left out for the bare 
bone interpreter.

---rony

>
>> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher > >:
>>
>> Those who use ooRexx5 from Sourceforge on a Mac and who have followed the 
>> instructions will have
>> ooRexx in "/Applications/ooRexx5".
>>
>> The enclosed Rexx script will create the link and remove commands that will 
>> make ooRexx5 available
>> systemwide. Run it and copy & paste the output to create the links or remove 
>> them.
>>
>> If you have ooRexx5 installed somewhere else, adjust the script accordingly.
>>
>> ---rony

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[Rick McGuire]

btw, if you were properly using the information from CMake.txt to build the
.dmg, you would not be having this problem, since all of the install()
statements identify which elements of the build should go where. That
information is used by all of the other installer types (including the
Windows one, which is done without CMake builtin CPack support).

Rick

On Fri, Jul 16, 2021 at 11:41 AM P.O. Jonsson  wrote:

> Dear Rony, just some thoughts.
>
> I did not run the script (yet) but is the intention to create symlinks to
> /usr/local so as to avoid the need to modify the path?
>
> If the 2nd part is creating the steps necessary to „unlink" why do you not
> create a shell script of those lines? After all the user will not realize
> at the time of installation (linking) that he might need them (much) later
> during an uninstall? (unlinking). It would appear possible to create a
> static unlink script for the default (/Applications/ooRexx5/bin,lib <->
> /usr/local/bin,lib
>
> Can we hear from the developers what the skipped files ( callrexx1,
> callrexx2, libwpipe1.dylib, libwpipe2.dylib, libwpipe3.dylib and
> oorexx-config.) are for? Can they be safely removed from the installation
> on macOS? How does one go about it?
>
> It is possible to delete these files from the (auto-generated) script
> building the dmg in a post-process but that would be the ugly way. IMO we
> should locate the places in CMakelists.txt where those files are copied and
> fix the problem there.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher  >:
>
> Those who use ooRexx5 from Sourceforge on a Mac and who have followed the
> instructions will have
> ooRexx in "/Applications/ooRexx5".
>
> The enclosed Rexx script will create the link and remove commands that
> will make ooRexx5 available
> systemwide. Run it and copy & paste the output to create the links or
> remove them.
>
> If you have ooRexx5 installed somewhere else, adjust the script
> accordingly.
>
> ---rony
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[Rick McGuire]

On Fri, Jul 16, 2021 at 11:41 AM P.O. Jonsson  wrote:

> Dear Rony, just some thoughts.
>
> I did not run the script (yet) but is the intention to create symlinks to
> /usr/local so as to avoid the need to modify the path?
>
> If the 2nd part is creating the steps necessary to „unlink" why do you not
> create a shell script of those lines? After all the user will not realize
> at the time of installation (linking) that he might need them (much) later
> during an uninstall? (unlinking). It would appear possible to create a
> static unlink script for the default (/Applications/ooRexx5/bin,lib <->
> /usr/local/bin,lib
>
> Can we hear from the developers what the skipped files ( callrexx1,
> callrexx2, libwpipe1.dylib, libwpipe2.dylib, libwpipe3.dylib and
> oorexx-config.) are for? Can they be safely removed from the installation
> on macOS? How does one go about it?
>

I'm not sure what oorexx-config is, but the others are the compiled sample
files.

Rick

>
> It is possible to delete these files from the (auto-generated) script
> building the dmg in a post-process but that would be the ugly way. IMO we
> should locate the places in CMakelists.txt where those files are copied and
> fix the problem there.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher  >:
>
> Those who use ooRexx5 from Sourceforge on a Mac and who have followed the
> instructions will have
> ooRexx in "/Applications/ooRexx5".
>
> The enclosed Rexx script will create the link and remove commands that
> will make ooRexx5 available
> systemwide. Run it and copy & paste the output to create the links or
> remove them.
>
> If you have ooRexx5 installed somewhere else, adjust the script
> accordingly.
>
> ---rony
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[P.O. Jonsson]

Dear Rony, just some thoughts.

I did not run the script (yet) but is the intention to create symlinks to 
/usr/local so as to avoid the need to modify the path?

If the 2nd part is creating the steps necessary to „unlink" why do you not 
create a shell script of those lines? After all the user will not realize at 
the time of installation (linking) that he might need them (much) later during 
an uninstall? (unlinking). It would appear possible to create a static unlink 
script for the default (/Applications/ooRexx5/bin,lib <-> /usr/local/bin,lib

Can we hear from the developers what the skipped files ( callrexx1, callrexx2, 
libwpipe1.dylib, libwpipe2.dylib, libwpipe3.dylib and oorexx-config.) are for? 
Can they be safely removed from the installation on macOS? How does one go 
about it?

It is possible to delete these files from the (auto-generated) script building 
the dmg in a post-process but that would be the ugly way. IMO we should locate 
the places in CMakelists.txt where those files are copied and fix the problem 
there.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher :
> 
> Those who use ooRexx5 from Sourceforge on a Mac and who have followed the 
> instructions will have
> ooRexx in "/Applications/ooRexx5".
> 
> The enclosed Rexx script will create the link and remove commands that will 
> make ooRexx5 available
> systemwide. Run it and copy & paste the output to create the links or remove 
> them.
> 
> If you have ooRexx5 installed somewhere else, adjust the script accordingly.
> 
> ---rony
> 
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[Rony G. Flatscher]

Those who use ooRexx5 from Sourceforge on a Mac and who have followed the 
instructions will have
ooRexx in "/Applications/ooRexx5".

The enclosed Rexx script will create the link and remove commands that will 
make ooRexx5 available
systemwide. Run it and copy & paste the output to create the links or remove 
them.

If you have ooRexx5 installed somewhere else, adjust the script accordingly.

---rony


#!/usr/bin/env rexx
-- rgf, 2021-07-15: link/remove '/Applications/ooRexx5' to/from /usr/local/{bin|lib}
ooRexxDir="/Applications/ooRexx5/"
targetDir   ="/usr/local/"

say "# remove quarantine attribute from directory and its content, if necessary:"
say "sudo xattr -r -d com.apple.quarantine /Applications/ooRexx5"
say

do dir over "bin", "lib"
   srcDir=ooRexxDir || dir
   tgtDir=targetDir || dir
   say "# linking files from:" srcDir "to:" tgtDir
   call sysFileTree srcDir"/*", "files.", "FO"
   w=0 -- determine longest string
   do i=1 to files.0
   w=max(w,length(files.i))
   end
   do i=1 to files.0
  fn=filespec("name",files.i)
  if fn~startsWith("callrexx") | fn~startsWith("libwpipe") then iterate
  say "sudo ln -sfv" (files.i)~left(w) tgtDir"/"fn
   end
   say
end

say
say "# remove files"
do dir over "bin", "lib"
   srcDir=ooRexxDir || dir
   tgtDir=targetDir || dir
   say "# remove files from:" tgtDir
   call sysFileTree srcDir"/*", "files.", "FO"
   w=0 -- determine longest string
   do i=1 to files.0
   w=max(w,length(files.i))
   end
   do i=1 to files.0
  fn=filespec("name",files.i)
  if fn~startsWith("callrexx") | fn~startsWith("libwpipe") then iterate
  say "sudo rm -f" tgtDir"/"fn
   end
   say
end






___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] BSF4ooRexx now works as well and now behaves like a good citizen on MacOSX ; ) (Re: ooRexx and Apple's "security police" on MacOS

[Rony G. Flatscher]

Just tested the new version of the BSF4ooRexx command line installer and it 
works with the official
ooRexx 5 installation. To test:

  * download

"https://sourceforge.net/projects/bsf4oorexx/files/beta/20200928/BSF4ooRexx_install_v641-20210715-beta.zip;

  * run "xattrs -d com.apple.quarantine 
BSF4ooRexx_install_v641-20210715-beta.zip"
  * unzip
  * change into "bsf4oorexx/install/macosx", issue "sh install.sh"
  o BSF4ooRexx gets copied to "/opt/BSF4ooRexx"
  o to uninstall use "sh /opt/BSF4ooRexx/install/macosx/uninstall.sh"

---rony

P.S.: The alternative would be to use the GUI-package for MacOSX which includes 
ooRexx 5:

  * download

"https://sourceforge.net/projects/bsf4oorexx/files/beta/20200928/b4r_641_500_64Bit_macosx-universal-20210627-r12266.zip;
  * run "xattrs -d com.apple.quarantine 
b4r_641_500_64Bit_macosx-universal-20210627-r12266.zip"
  * unzip and open the package for installation
  * to uninstall: use the menu by opening "/Applications/ooRexx.app", choose 
"Installation -> Uninstall"


On 16.07.2021 15:41, Rony G. Flatscher wrote:
>
> While testing a little bit, here is maybe another helpful insight: after 
> downloading the ooRexx
> installation package it is possible without super-user power to remove the 
> quarantine attribute
> using Renés example:
>
> xattr -d com.apple.quarantine ooRexx-5.0.0-12280.macOS.x86_64.dmg
>
> Then installing ooRexx by opening the dmg-file and following the installation 
> directions yields a
> working installation in /Applications/ooRexx5!
>
> ---rony
>
>
> On 16.07.2021 14:27, René Jansen wrote:
>> Running 
>>
>> sudo xattr -r -d com.apple.quarantine $YOUR_DIRECTORY 
>>
>> mostly helps.
>>
>> René
>>
>>> On 16 Jul 2021, at 14:10, P.O. Jonsson >> > wrote:
>>>
>>> What version of MacOS are we talking about? In the past extracting the .dmg 
>>> caused a warning
>>> that could be overwritten but I never experienced that rexx would not 
>>> launch? Is this a M1 thing
>>> only? Or „Fat Binary“ problem? Does it help to install to ~/Applications (a 
>>> local install)
>>> rather than to /Applications (Install for all users)? 
>>>
>>> I run High Sierra (10.13) and the build machine runs Mojave (10.14). In 
>>> view of the age of the
>>> build machine (~ late 2014) I would not go beyond Catalina (10.15) and I 
>>> see no gain in
>>> changing, just risk of running into problems with outdated hardware.
>>>
>>> We do not have at our disposal any machine with macOS Big Sur (11.1) that 
>>> can run on either
>>> Intel or M1 hardware.
>>>
>>> What I can try to do is to see if I can get some Virtual Machines set up 
>>> with Catalina/Big Sur.
>>> But it will not be on M1 hardware.
>>>
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se 
>>>
>>>
>>>
 Am 16.07.2021 um 13:47 schrieb Rony G. Flatscher >>> >:

 Downloaded the latest MacOS version of ooRexx 5.0 from the ooRexx project 
 page at sourceforge.

 It turns out that Apple inhibits using anything from that dmg as it was 
 downloaded from the
 Internet and not from Apple's store! :(

 This is due to Apple's "security policy" that they put in effect, which 
 simply deprive the
 owners of those Apple computers.

 Here are two use cases, each demonstrated with an attached screenshot:

   * Scenario 1: installing ooRexx according to the readme will create 
 "/Application/ooRexx5"
 with the "bin", "lib" etc directories. Trying to run 
 "/Application/ooRexx5/bin/rexx -v"
 causes "Screenshot 2021-07-16 at 12.46.04.png" to pop up. Apple 
 suggests to move the
 program to the bin! :-(

   * Scenario 2: using Finder to "open" (run) 
 "/Application/ooRexx5/bin/rexx" yields at first a
 pop up that seems to indicate, that further opening would allow the 
 program to run from now
 on, cf. "Screenshot 2021-07-16 at 12.53.17.png". However when "rexx" 
 loads the
 "librexx.4.dylib" the "Move to Bin" popup as above gets displayed!

 Probably turning off SIP
 ()
 will allow this to work again, however, asking users to turn off SIP may 
 be too much.

 The alternative would be to get and use the keys from Apple and use them 
 to sign the ooRexx
 executables.

 The question then is, who should apply/buy this: RexxLA or some individual 
 developer in this
 group who signs the releases? Who is going to pursue this?

 ---rony

 P.S.: @Enrico: this may be also the reason why on M1 with a stricter 
 "security policy" in place
 would not pick the amd64 binaries from the fat distribution! If you look 
 at the first screen
 shot you can read "Reason: no suitable image 

Re: [Oorexx-devel] ooRexx and Apple's "security police" on MacOS

[Rony G. Flatscher]

While testing a little bit, here is maybe another helpful insight: after 
downloading the ooRexx
installation package it is possible without super-user power to remove the 
quarantine attribute
using Renés example:

xattr -d com.apple.quarantine ooRexx-5.0.0-12280.macOS.x86_64.dmg

Then installing ooRexx by opening the dmg-file and following the installation 
directions yields a
working installation in /Applications/ooRexx5!

---rony


On 16.07.2021 14:27, René Jansen wrote:
> Running 
>
> sudo xattr -r -d com.apple.quarantine $YOUR_DIRECTORY 
>
> mostly helps.
>
> René
>
>> On 16 Jul 2021, at 14:10, P.O. Jonsson > > wrote:
>>
>> What version of MacOS are we talking about? In the past extracting the .dmg 
>> caused a warning that
>> could be overwritten but I never experienced that rexx would not launch? Is 
>> this a M1 thing only?
>> Or „Fat Binary“ problem? Does it help to install to ~/Applications (a local 
>> install) rather than
>> to /Applications (Install for all users)? 
>>
>> I run High Sierra (10.13) and the build machine runs Mojave (10.14). In view 
>> of the age of the
>> build machine (~ late 2014) I would not go beyond Catalina (10.15) and I see 
>> no gain in changing,
>> just risk of running into problems with outdated hardware.
>>
>> We do not have at our disposal any machine with macOS Big Sur (11.1) that 
>> can run on either Intel
>> or M1 hardware.
>>
>> What I can try to do is to see if I can get some Virtual Machines set up 
>> with Catalina/Big Sur.
>> But it will not be on M1 hardware.
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>>
>>
>>
>>> Am 16.07.2021 um 13:47 schrieb Rony G. Flatscher >> >:
>>>
>>> Downloaded the latest MacOS version of ooRexx 5.0 from the ooRexx project 
>>> page at sourceforge.
>>>
>>> It turns out that Apple inhibits using anything from that dmg as it was 
>>> downloaded from the
>>> Internet and not from Apple's store! :(
>>>
>>> This is due to Apple's "security policy" that they put in effect, which 
>>> simply deprive the
>>> owners of those Apple computers.
>>>
>>> Here are two use cases, each demonstrated with an attached screenshot:
>>>
>>>   * Scenario 1: installing ooRexx according to the readme will create 
>>> "/Application/ooRexx5"
>>> with the "bin", "lib" etc directories. Trying to run 
>>> "/Application/ooRexx5/bin/rexx -v"
>>> causes "Screenshot 2021-07-16 at 12.46.04.png" to pop up. Apple 
>>> suggests to move the program
>>> to the bin! :-(
>>>
>>>   * Scenario 2: using Finder to "open" (run) 
>>> "/Application/ooRexx5/bin/rexx" yields at first a
>>> pop up that seems to indicate, that further opening would allow the 
>>> program to run from now
>>> on, cf. "Screenshot 2021-07-16 at 12.53.17.png". However when "rexx" 
>>> loads the
>>> "librexx.4.dylib" the "Move to Bin" popup as above gets displayed!
>>>
>>> Probably turning off SIP
>>> ()
>>> will allow this to work again, however, asking users to turn off SIP may be 
>>> too much.
>>>
>>> The alternative would be to get and use the keys from Apple and use them to 
>>> sign the ooRexx
>>> executables.
>>>
>>> The question then is, who should apply/buy this: RexxLA or some individual 
>>> developer in this
>>> group who signs the releases? Who is going to pursue this?
>>>
>>> ---rony
>>>
>>> P.S.: @Enrico: this may be also the reason why on M1 with a stricter 
>>> "security policy" in place
>>> would not pick the amd64 binaries from the fat distribution! If you look at 
>>> the first screen
>>> shot you can read "Reason: no suitable image found.", the same error 
>>> message as on M1, but here
>>> there is additional information pointing ad "Library Validation: ..." that 
>>> fails.
>>>
>>> This behavior might not be present if you create ooRexx on the M1 and run 
>>> it from there, as then
>>> the binaries did not come from "insecure locations" according to Apple 
>>> (which is the Internet
>>> and locations that are not under the control of Apple software).
>>>

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx on MacOSX: superfluous files in ooRexx5/bin

[Rony G. Flatscher]

On 16.07.2021 15:30, P.O. Jonsson wrote:
>> Oops, just noticed that I was working in" ~/Applications/ooRexx5" and not in
>> "/Applications/ooRexx5", sorry!
>
> This IS a bit confusing: The official build install to ~/Applications (i.e.
> /Users/Jenkins/Applications) but since the build is universally relocatable I 
> add a link to
> /Applications for the user Drop You can put the installation anywhere 
> you want but most
> people will look for „Apps“ in the /Applications folder -> rule of least 
> surprise
>
>> There is an empty "/Applications/ooRexx5/Icon?" file there though.
>>
> This is an effect of moving the installation from one machine to another, 
> Originally the icon is
> the ooRexx icon for the DMG itself. For some reason it gets erased during the 
> move. You can see
> this in many „Apps“ you install on macOS.
>
> If you look at the Jenkins ooRexx build machine you can see this for 
> yourself. Any help in fixing
> the problem is most wellcome. Or I can delete the icon for the DMG (it is 
> added during the DMG
> build process)

Unfortunately, I am of no help here, not knowing anything about the inner 
workings of DMG, maybe
Enrico has an idea what happens here?

---rony



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx on MacOSX: superfluous files in ooRexx5/bin

[P.O. Jonsson]

> Oops, just noticed that I was working in" ~/Applications/ooRexx5" and not in 
> "/Applications/ooRexx5", sorry!

This IS a bit confusing: The official build install to ~/Applications (i.e. 
/Users/Jenkins/Applications) but since the build is universally relocatable I 
add a link to /Applications for the user Drop You can put the 
installation anywhere you want but most people will look for „Apps“ in the 
/Applications folder -> rule of least surprise

> There is an empty "/Applications/ooRexx5/Icon?" file there though.
> 

This is an effect of moving the installation from one machine to another, 
Originally the icon is the ooRexx icon for the DMG itself. For some reason it 
gets erased during the move. You can see this in many „Apps“ you install on 
macOS.

If you look at the Jenkins ooRexx build machine you can see this for yourself. 
Any help in fixing the problem is most wellcome. Or I can delete the icon for 
the DMG (it is added during the DMG build process)
> ---rony
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx on MacOSX: superfluous files in ooRexx5/bin

[Rony G. Flatscher]

The empty icon's filename is (when using completion):

/Applications/ooRexx5/Icon$'\r'

---rony


On 16.07.2021 15:18, Rony G. Flatscher wrote:
> On 16.07.2021 15:14, P.O. Jonsson wrote:
>>
>>> Am 16.07.2021 um 15:01 schrieb Rony G. Flatscher >> >:
>>>
>>> Just noticed that the following files (not core of ooRexx) are contained in 
>>> "ooRexx5/bin" and should
>>> probably not be copied to the ooRexx bin directory: callrexx1, callrexx2, 
>>> libwpipe1.dylib,
>>> libwpipe2.dylib, libwpipe3.dylib and oorexx-config.
>>>
>>
>> This will need to be adressed in CMakelists.txt, the installer is merely 
>> providing a 1:1 copy of
>> the ooRexx installation following a „make install“
>>
>>> Also there is a superfluous "ooRexx5/info.txt" file present (output of 
>>> "rexx -v“).
>>
>> I cannot see that in my case, are you sure you did not put it there?
>
> Oops, just noticed that I was working in" ~/Applications/ooRexx5" and not in
> "/Applications/ooRexx5", sorry!
>
> There is an empty "/Applications/ooRexx5/Icon?" file there though.
>
> ---rony
>

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx on MacOSX: superfluous files in ooRexx5/bin

[Rony G. Flatscher]

On 16.07.2021 15:14, P.O. Jonsson wrote:
>
>> Am 16.07.2021 um 15:01 schrieb Rony G. Flatscher > >:
>>
>> Just noticed that the following files (not core of ooRexx) are contained in 
>> "ooRexx5/bin" and should
>> probably not be copied to the ooRexx bin directory: callrexx1, callrexx2, 
>> libwpipe1.dylib,
>> libwpipe2.dylib, libwpipe3.dylib and oorexx-config.
>>
>
> This will need to be adressed in CMakelists.txt, the installer is merely 
> providing a 1:1 copy of
> the ooRexx installation following a „make install“
>
>> Also there is a superfluous "ooRexx5/info.txt" file present (output of "rexx 
>> -v“).
>
> I cannot see that in my case, are you sure you did not put it there?

Oops, just noticed that I was working in" ~/Applications/ooRexx5" and not in
"/Applications/ooRexx5", sorry!

There is an empty "/Applications/ooRexx5/Icon?" file there though.

---rony

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx and Apple's "security police" on MacOS

[Rony G. Flatscher]

On 16.07.2021 15:03, P.O. Jonsson wrote:
... cut ...

> A question on the „fat Binaries“: I cannot see any trace of different 
> versions of the files in the
> installer, can you please elaborate? I do not have any M1 hardware to test it 
> on.

This was a remark for Enrico, who kindly submitted changes to CMake to allow 
the creation of a
universal version of ooRexx which includes both architectures.  In parallel I 
created a fat version
of BSF4ooRexx to create an installation package that included both, the Intel 
and the M1 version.
Unfortunately, the arm64 binaries from BSF4ooRexx and ooRexx would not get 
loaded on M1 with a
rather meaningless error message ("... not found ..."). My take now is that it 
might have to do with
this "security policy" issue of which I am not sure whether it can be solved 
with Renés xattr
command there. Have asked a student who has a M1 and has been really, really 
eager to get BSF4ooRexx
installed and available on it as well. [Unfortunately, I do not have a M1 to 
test, so am dependent
on others and their ree time.]

The original idea was, that once this works, it should be incorporated into the 
official ooRexx
project (via a patch) as Enrico is good with doing so (I would declare this 
with the patch, such
that the origin and the license of the patch is put out of question). But have 
not heard from Enrico
in a while, maybe this findings can get everything going again.

---rony




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx and Apple's "security police" on MacOS

[P.O. Jonsson]

> Am 16.07.2021 um 14:51 schrieb Rony G. Flatscher :
> 
> On 16.07.2021 14:47, P.O. Jonsson wrote:
>>> No, what has helped was René's suggestion: 
>>> sudo xattr -r -d com.apple.quarantine $YOUR_DIRECTORY 
>>> Ran it against /Applications/ooRexx5 and voilà now rexx -v works! (Still 
>>> tests to do, will symbollically create links in /usr/local/bin and 
>>> /usr/local/lib and if problems arise, will report back.)
>> 
>> We should thus have a post install script running this command then (or 
>> instructing the user to do so). But it will then not be „sudo free“ any more.
>> 
>> In any case the user need to add the /bin of the installation 
>> (/Applications/ooRexx5/bin normally) to the path. This is described in the 
>> installer.
> Yes, I followed those instructions. 
> In the next step I will link the ooRexx files to /usr/local for testing a new 
> version of the BSF4ooRexx command line installer with it (that version will 
> install to /opt/BSF4ooRexx and will have no entry in /Application). Have been 
> working on this now that the ooRexx project has official ooRexx distributions 
> for MacOS (the latest GUI-installer of BSF4ooRexx which contains ooRexx5 will 
> abort, if it finds /usr/local/bin/rexx to exist, otherwise it installs its 
> included ooRexx making that version system wide available).
> 
> —rony
> 

OK, I had not been installing ooRexx from the official build since some time so 
I did it as well. On High Sierra I get no warning and do not need to run the 
command above. I need to document this and put it in the installer.

A question on the „fat Binaries“: I cannot see any trace of different versions 
of the files in the installer, can you please elaborate? I do not have any M1 
hardware to test it on.

> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] ooRexx on MacOSX: superfluous files in ooRexx5/bin

[Rony G. Flatscher]

Just noticed that the following files (not core of ooRexx) are contained in 
"ooRexx5/bin" and should
probably not be copied to the ooRexx bin directory: callrexx1, callrexx2, 
libwpipe1.dylib,
libwpipe2.dylib, libwpipe3.dylib and oorexx-config.

Also there is a superfluous "ooRexx5/info.txt" file present (output of "rexx 
-v").

---rony




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx and Apple's "security police" on MacOS

[Rony G. Flatscher]

On 16.07.2021 14:47, P.O. Jonsson wrote:
>>
>> No, what has helped was René's suggestion:
>>
>> sudo xattr -r -d com.apple.quarantine $YOUR_DIRECTORY
>>
>> Ran it against /Applications/ooRexx5 and voilà now rexx -v works! (Still 
>> tests to do, will
>> symbollically create links in /usr/local/bin and /usr/local/lib and if 
>> problems arise, will
>> report back.)
>>
>
> We should thus have a post install script running this command then (or 
> instructing the user to do
> so). But it will then not be „sudo free“ any more.
>
> In any case the user need to add the /bin of the installation 
> (/Applications/ooRexx5/bin normally)
> to the path. This is described in the installer.

Yes, I followed those instructions.

In the next step I will link the ooRexx files to /usr/local for testing a new 
version of the
BSF4ooRexx command line installer with it (that version will install to 
/opt/BSF4ooRexx and will
have no entry in /Application). Have been working on this now that the ooRexx 
project has official
ooRexx distributions for MacOS (the latest GUI-installer of BSF4ooRexx which 
contains ooRexx5 will
abort, if it finds /usr/local/bin/rexx to exist, otherwise it installs its 
included ooRexx making
that version system wide available).

---rony


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx and Apple's "security police" on MacOS

[P.O. Jonsson]

> No, what has helped was René's suggestion: 
> sudo xattr -r -d com.apple.quarantine $YOUR_DIRECTORY 
> Ran it against /Applications/ooRexx5 and voilà now rexx -v works! (Still 
> tests to do, will symbollically create links in /usr/local/bin and 
> /usr/local/lib and if problems arise, will report back.)

We should thus have a post install script running this command then (or 
instructing the user to do so). But it will then not be „sudo free“ any more.

In any case the user need to add the /bin of the installation 
(/Applications/ooRexx5/bin normally) to the path. This is described in the 
installer.

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx and Apple's "security police" on MacOS

[Rony G. Flatscher]

On 16.07.2021 14:27, René Jansen wrote:
> sudo xattr -r -d com.apple.quarantine $YOUR_DIRECTORY

Super, this has worked in this case, thank you very much for sharing!

---rony

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx and Apple's "security police" on MacOS

[Rony G. Flatscher]

On 16.07.2021 14:10, P.O. Jonsson wrote:
> What version of MacOS are we talking about? 

11.4 BigSur on Intel.

ooRexx from SourceForge (r12280, Jul 12 2021).

> In the past extracting the .dmg caused a warning that could be overwritten 
> but I never experienced
> that rexx would not launch? Is this a M1 thing only? Or „Fat Binary“ problem? 
> Does it help to
> install to ~/Applications (a local install) rather than to /Applications 
> (Install for all users)?

No, what has helped was René's suggestion:

sudo xattr -r -d com.apple.quarantine $YOUR_DIRECTORY

Ran it against /Applications/ooRexx5 and voilà now rexx -v works! (Still tests 
to do, will
symbollically create links in /usr/local/bin and /usr/local/lib and if problems 
arise, will report
back.)

---rony

>
>
>> Am 16.07.2021 um 13:47 schrieb Rony G. Flatscher > >:
>>
>> Downloaded the latest MacOS version of ooRexx 5.0 from the ooRexx project 
>> page at sourceforge.
>>
>> It turns out that Apple inhibits using anything from that dmg as it was 
>> downloaded from the
>> Internet and not from Apple's store! :(
>>
>> This is due to Apple's "security policy" that they put in effect, which 
>> simply deprive the owners
>> of those Apple computers.
>>
>> Here are two use cases, each demonstrated with an attached screenshot:
>>
>>   * Scenario 1: installing ooRexx according to the readme will create 
>> "/Application/ooRexx5" with
>> the "bin", "lib" etc directories. Trying to run 
>> "/Application/ooRexx5/bin/rexx -v" causes
>> "Screenshot 2021-07-16 at 12.46.04.png" to pop up. Apple suggests to 
>> move the program to the
>> bin! :-(
>>
>>   * Scenario 2: using Finder to "open" (run) "/Application/ooRexx5/bin/rexx" 
>> yields at first a
>> pop up that seems to indicate, that further opening would allow the 
>> program to run from now
>> on, cf. "Screenshot 2021-07-16 at 12.53.17.png". However when "rexx" 
>> loads the
>> "librexx.4.dylib" the "Move to Bin" popup as above gets displayed!
>>
>> Probably turning off SIP
>> ()
>> will allow this to work again, however, asking users to turn off SIP may be 
>> too much.
>>
>> The alternative would be to get and use the keys from Apple and use them to 
>> sign the ooRexx
>> executables.
>>
>> The question then is, who should apply/buy this: RexxLA or some individual 
>> developer in this
>> group who signs the releases? Who is going to pursue this?
>>
>> ---rony
>>
>> P.S.: @Enrico: this may be also the reason why on M1 with a stricter 
>> "security policy" in place
>> would not pick the amd64 binaries from the fat distribution! If you look at 
>> the first screen shot
>> you can read "Reason: no suitable image found.", the same error message as 
>> on M1, but here there
>> is additional information pointing ad "Library Validation: ..." that fails.
>>
>> This behavior might not be present if you create ooRexx on the M1 and run it 
>> from there, as then
>> the binaries did not come from "insecure locations" according to Apple 
>> (which is the Internet and
>> locations that are not under the control of Apple software).
>>
>>
>> > 12.53.17.png>___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net 
>> 
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

-- 
--
__

Prof. Dr. Rony G. Flatscher
Department Wirtschaftsinformatik und Operations Management
Institut für Wirtschaftsinformatik und Gesellschaft
D2c 2.086
WU Wien
Welthandelsplatz 1
A-1020  Wien/Vienna, Austria/Europe

http://www.wu.ac.at
__





___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx and Apple's "security police" on MacOS

[René Jansen]

Running 

sudo xattr -r -d com.apple.quarantine $YOUR_DIRECTORY 

mostly helps.

René

> On 16 Jul 2021, at 14:10, P.O. Jonsson  wrote:
> 
> What version of MacOS are we talking about? In the past extracting the .dmg 
> caused a warning that could be overwritten but I never experienced that rexx 
> would not launch? Is this a M1 thing only? Or „Fat Binary“ problem? Does it 
> help to install to ~/Applications (a local install) rather than to 
> /Applications (Install for all users)? 
> 
> I run High Sierra (10.13) and the build machine runs Mojave (10.14). In view 
> of the age of the build machine (~ late 2014) I would not go beyond Catalina 
> (10.15) and I see no gain in changing, just risk of running into problems 
> with outdated hardware.
> 
> We do not have at our disposal any machine with macOS Big Sur (11.1) that can 
> run on either Intel or M1 hardware.
> 
> What I can try to do is to see if I can get some Virtual Machines set up with 
> Catalina/Big Sur. But it will not be on M1 hardware.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
>> Am 16.07.2021 um 13:47 schrieb Rony G. Flatscher > >:
>> 
>> Downloaded the latest MacOS version of ooRexx 5.0 from the ooRexx project 
>> page at sourceforge. 
>> 
>> It turns out that Apple inhibits using anything from that dmg as it was 
>> downloaded from the Internet and not from Apple's store! :(
>> 
>> This is due to Apple's "security policy" that they put in effect, which 
>> simply deprive the owners of those Apple computers. 
>> 
>> Here are two use cases, each demonstrated with an attached screenshot:
>> 
>> Scenario 1: installing ooRexx according to the readme will create 
>> "/Application/ooRexx5" with the "bin", "lib" etc directories. Trying to run 
>> "/Application/ooRexx5/bin/rexx -v" causes "Screenshot 2021-07-16 at 
>> 12.46.04.png" to pop up. Apple suggests to move the program to the bin! :-(
>> 
>> Scenario 2: using Finder to "open" (run) "/Application/ooRexx5/bin/rexx" 
>> yields at first a pop up that seems to indicate, that further opening would 
>> allow the program to run from now on, cf. "Screenshot 2021-07-16 at 
>> 12.53.17.png". However when "rexx" loads the "librexx.4.dylib" the "Move to 
>> Bin" popup as above gets displayed!
>> Probably turning off SIP 
>> (
>>  
>> )
>>  will allow this to work again, however, asking users to turn off SIP may be 
>> too much.
>> 
>> The alternative would be to get and use the keys from Apple and use them to 
>> sign the ooRexx executables. 
>> 
>> The question then is, who should apply/buy this: RexxLA or some individual 
>> developer in this group who signs the releases? Who is going to pursue this?
>> 
>> ---rony
>> 
>> P.S.: @Enrico: this may be also the reason why on M1 with a stricter 
>> "security policy" in place would not pick the amd64 binaries from the fat 
>> distribution! If you look at the first screen shot you can read "Reason: no 
>> suitable image found.", the same error message as on M1, but here there is 
>> additional information pointing ad "Library Validation: ..." that fails.
>> 
>> This behavior might not be present if you create ooRexx on the M1 and run it 
>> from there, as then the binaries did not come from "insecure locations" 
>> according to Apple (which is the Internet and locations that are not under 
>> the control of Apple software). 
>> 
>> 
>> 
>> > 12.53.17.png>___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net 
>> 
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx and Apple's "security police" on MacOS

[P.O. Jonsson]

What version of MacOS are we talking about? In the past extracting the .dmg 
caused a warning that could be overwritten but I never experienced that rexx 
would not launch? Is this a M1 thing only? Or „Fat Binary“ problem? Does it 
help to install to ~/Applications (a local install) rather than to 
/Applications (Install for all users)? 

I run High Sierra (10.13) and the build machine runs Mojave (10.14). In view of 
the age of the build machine (~ late 2014) I would not go beyond Catalina 
(10.15) and I see no gain in changing, just risk of running into problems with 
outdated hardware.

We do not have at our disposal any machine with macOS Big Sur (11.1) that can 
run on either Intel or M1 hardware.

What I can try to do is to see if I can get some Virtual Machines set up with 
Catalina/Big Sur. But it will not be on M1 hardware.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 16.07.2021 um 13:47 schrieb Rony G. Flatscher :
> 
> Downloaded the latest MacOS version of ooRexx 5.0 from the ooRexx project 
> page at sourceforge. 
> It turns out that Apple inhibits using anything from that dmg as it was 
> downloaded from the Internet and not from Apple's store! :(
> 
> This is due to Apple's "security policy" that they put in effect, which 
> simply deprive the owners of those Apple computers. 
> Here are two use cases, each demonstrated with an attached screenshot:
> 
> Scenario 1: installing ooRexx according to the readme will create 
> "/Application/ooRexx5" with the "bin", "lib" etc directories. Trying to run 
> "/Application/ooRexx5/bin/rexx -v" causes "Screenshot 2021-07-16 at 
> 12.46.04.png" to pop up. Apple suggests to move the program to the bin! :-(
> 
> Scenario 2: using Finder to "open" (run) "/Application/ooRexx5/bin/rexx" 
> yields at first a pop up that seems to indicate, that further opening would 
> allow the program to run from now on, cf. "Screenshot 2021-07-16 at 
> 12.53.17.png". However when "rexx" loads the "librexx.4.dylib" the "Move to 
> Bin" popup as above gets displayed!
> Probably turning off SIP 
> (
>  
> )
>  will allow this to work again, however, asking users to turn off SIP may be 
> too much.
> 
> The alternative would be to get and use the keys from Apple and use them to 
> sign the ooRexx executables. 
> The question then is, who should apply/buy this: RexxLA or some individual 
> developer in this group who signs the releases? Who is going to pursue this?
> 
> ---rony
> 
> P.S.: @Enrico: this may be also the reason why on M1 with a stricter 
> "security policy" in place would not pick the amd64 binaries from the fat 
> distribution! If you look at the first screen shot you can read "Reason: no 
> suitable image found.", the same error message as on M1, but here there is 
> additional information pointing ad "Library Validation: ..." that fails.
> 
> This behavior might not be present if you create ooRexx on the M1 and run it 
> from there, as then the binaries did not come from "insecure locations" 
> according to Apple (which is the Internet and locations that are not under 
> the control of Apple software). 
> 
>  12.53.17.png>___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel