Re: [Oorexx-devel] Conventions
Hi Gil, As Rick has already mentioned it is only the filenames and the top-level directory name in the source package that is being proposed to be all lowercase. The reason for following this convention is that on platforms like Debian and HomeBrew (one of the the package managers on MacOS), the filename of the source package or the top-level directory name is used as the package name and version when building a binary package for the respective platforms. For ooRexx to be accepted in official platform repositories these conventions need to be followed otherwise ooRexx is likely to be rejected from inclusion. And as you know, getting ooRexx into official repositories is one of the goals of RexxLA. Cheers, Mark On 14/4/23 22:32, Gilbert Barmwater wrote: I think this needs more discussion before making, what seems on the surface to be, a "trivial" change. When RexxLA received the source for Object Rexx from IBM, there was quite a bit of discussion on what the project should be called with the eventual decision being "ooRexx". I'm sure the archives have the pro's and con's but there were reasons for the choice. It was definitely NOT arbitrary. I understand the need for all lower case for *nix systems but isn't the "build" that one downloads from the "Files" section of Source Forge just a "container"? Couldn't the "contents" have all lower case names and wouldn't that meet the *nix requirements? I realize I'm showing my ignorance here so please help me understand if this is a "must" or just a "preference". Gil On 4/14/2023 7:27 AM, Rony G. Flatscher wrote: On 14.04.2023 09:44, P.O. Jonsson wrote: While working on creating a source package for #1854 I realized that all our artifacts starts off with ooRexx-, in CamelFont. It comes from this line in CMakeLists.txt set(CPACK_PACKAGE_NAME "ooRexx") Since we have a requirement in the build to keep all other parts in lowercase (example -DOS_DIST=centos9 etc) this is a bit odd. I would like to change this to set(CPACK_PACKAGE_NAME "oorexx") Any objections? Not at all, it seems that all lowercase is the norm on Unix systems and necessary for distributions. Please go for it! ---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 -- * 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] Source package for download
Hi Rony, I have updated bug #1854 with an explanation of the requirements of the source package(s) and some suggested fixes. Cheers, Mark On 7/4/23 21:26, Rony G. Flatscher wrote: Hi Mark, On 05.04.2023 10:58, Mark Hessling wrote: I'm planning on building a HomeBrew formula for ooRexx, so that I can release my external function packages for macos via HomeBrew for both Regina and ooRexx. Super! HomeBrew formula require a link to an official source package; usually a tar.gz that can be downloaded as part of the installation phase. The hurdle I've come across is that there does not appear to be an official source package that can be downloaded, at least from SourceForge where the official binary packages are available. Is there a location where a source package file can be downloaded? AFAIK there is no such location as of yet. Would it be sufficient to create a tar.gz from a checked out the whole ooRexx svn tree? Something like: svn checkout --username=orexx svn+ssh://or...@svn.code.sf.net/p/oorexx/code-0/main/trunk oorexx-code-0 or anonymously: svn checkout https://svn.code.sf.net/p/oorexx/code-0/main/trunk oorexx-code-0 Note: the above (Sourceforge supplied) svn checkout commands relate to the trunk of ooRexx itself, not to the docs sources at https://svn.code.sf.net/p/oorexx/code-0/docs/trunk. The latest versions of the ooRexx docs pdf-files can be downloaded from <https://sourceforge.net/projects/oorexx/files/oorexx-docs/5.1.0beta/> (there are the individual pdf-files, but also zip-archives of the pdf-files - e.g. https://sourceforge.net/projects/oorexx/files/oorexx-docs/5.1.0beta/ooRexx-5.1.0beta-pdf.zip/download - and separately of the html-files). --- If I understand you correctly then we should place a tar.gz package of "main/trunk" at a specific download location (maybe on the files-download branch on the project, i.e. <https://sourceforge.net/projects/oorexx/files/>. What name should such a subdirectory have on Sourceforge? How should the pdf-documentation be made available (in the same subdirectory as the source as a zip- or tar.gz-archive of all the docs pdf-files)? Thank you again for your initiative and efforts, Mark! Best regards ---rony ___ 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
[Oorexx-devel] Source package for download
I'm planning on building a HomeBrew formula for ooRexx, so that I can release my external function packages for macos via HomeBrew for both Regina and ooRexx. HomeBrew formula require a link to an official source package; usually a tar.gz that can be downloaded as part of the installation phase. The hurdle I've come across is that there does not appear to be an official source package that can be downloaded, at least from SourceForge where the official binary packages are available. Is there a location where a source package file can be downloaded? Thanks, Mark -- * 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] Apple: cannot build universal orxncurses, linking error, wrong ncurses being picked up, however if ...
opt/local/lib/libncurs* away and then rerunning cmake makes everything work: ___ 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 ___ 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
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 > <mailto:oor...@jonases.se>> 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 <mailto: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 >>> <mailto:Oorexx-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> >> >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> <mailto:Oorexx-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> <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] Rexx LA Mailing List
I would suggest a more generic statement along the lines of: "For more information and resources about Rexx, visit The Rexx Language Association at https://www.rexxla.org.; On 28/3/21 1:45 am, Erich Steinböck wrote: > ooRexx docs say: "The Rexx Language Association maintains a forum at > http://www.rexxla.org/forum.html with its archive located at > http://rexx-language-association-forum.44760.x6.nabble.com.; > > Currently the two links don't seem to show anything useful. > > Is this an issue we can fix, or should this sentence be removed from > the docs? > > > > ___ > 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: http://www.rexxla.org/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] [Oorexx-svn] SF.net SVN: oorexx-code-0:[12051] main/trunk/platform/unix
The only "configuration" is when you want to switch between alternate
Rexx interpreters. Just as you have to run a script to switch between
different versions of ooRexx.
With the relocatable executables that ooRexx has, how do man pages get
swapped?
eg. I have a version of ooRexx installed in say /opt/ooRexx-v5.0.0 which
has a rexx.1 man page with certain contents, and I have another version
of ooRexx installed in /opt/ooRexx-v5.1.0 which has introduced a new
switch to the rexx binary and is documented in the new rexx.1 man page.
When I switch executables, how are the equivalent man pages switched so
I get the correct man page contents for the correct binary?
While the concept of relocatable executables is a great idea for
switching between different versions of ooRexx, how does it work when I
want to switch between ooRexx and Regina?
Cheers, Mark
On 7/4/20 9:27 am, Enrico Sorichetti wrote:
> I just looked at the man pages both for Ubuntu and Fedora, and it
> looks like
> The update alternatives have to be configured
>
> IMO it is much more simple to
> Cd
> Export PATH=`pwd`:$PATH
> Or better use the attached snippets
>
> It works for me on Darwin Fedora, CentOS
> Enrico
>
> Here are two bash snippets to add/remove a directory to/from the PATH
> ( I have also the same for zsh )
>
> Cd somewhere and …
>
> The snippets should be sourced, not executed
>
> source path.here
> . path.here
>
> source path.remove
> . path.remove
>
>
> # path.here
> # remove the current path from the PATH and add it to the front
>
> # add in front of PATH
> prepen_path()
> {
> if ! eval test -z "\"\${$1##*:$2:*}\"" -o -z "\"\${$1%%*:$2}\"" -o
> -z "\"\${$1##$2:*}\"" -o -z "\"\${$1##$2}\"" ; then
> eval "$1=$2:\$$1"
> fi
> }
>
> # remove path
> remove_path()
> {
> # front/middle
> if eval test -z "\"\${$1##$2:*}\"" -o -z "\"\${$1##*:$2:*}\"" ; then
> eval "$1=${!1/$2:/}"
> return
> fi
> # tail
> if eval test -z "\"\${$1%%*:$2}\"" ; then
> eval "$1=${!1/:$2/}"
> return
> fi
> # only
> if eval test -z "\"\${$1##$2}\"" ; then
> eval "$1=${!1/$2/}"
> return
> fi
> }
>
> # the works
> here="$(pwd)"
> if ! test -d "${here}" ; then
> echo "strange ... path not found '${here}'"
> else
> remove_path PATH "${here}"
> export PATH
> prepen_path PATH "${here}"
> export PATH
> fi
>
> # cleanup
> unset prepen_path
> unset remove_path
>
>
>
>
> # path.remove
> # remove the current path from the PATH
>
> # remove path
> remove_path()
> {
> # front/middle
> if eval test -z "\"\${$1##$2:*}\"" -o -z "\"\${$1##*:$2:*}\"" ; then
> eval "$1=${!1/$2:/}"
> return
> fi
> # tail
> if eval test -z "\"\${$1%%*:$2}\"" ; then
> eval "$1=${!1/:$2/}"
> return
> fi
> # only
> if eval test -z "\"\${$1##$2}\"" ; then
> eval "$1=${!1/$2/}"
> return
> fi
> }
>
> #the works
> here="$(pwd)"
> if ! test -d "${here}" ; then
> echo "strange ... path not found '${here}'"
> else
> remove_path PATH "${here}"
> export PATH
> fi
>
> # cleanup
> unset remove_path
>
>
>
>> On 7 Apr 2020, at 01:05, Mark Hessling > <mailto:m...@rexx.org>> wrote:
>>
>> Hi P.O.,
>>
>> I apologise for problems my changes caused you; it was not
>> intentional and if I had known about your problems at the time I
>> would have fixed them.
>>
>
--
* 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: http://www.rexxla.org/
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] [Oorexx-svn] SF.net SVN: oorexx-code-0:[12051] main/trunk/platform/unix
Hi P.O., I apologise for problems my changes caused you; it was not intentional and if I had known about your problems at the time I would have fixed them. My perspective with the changes is from outside; ie maintainer of Regina, where I wanted to have ooRexx and Regina to be able to be installed on the same machine at the same time. The "standard" way for this is using update-alternatives and that is how Linux users expect to switch between different packages that provide the same functionality. See "man update-alternatives" on your Linux machine; particularly Debian based systems. I, like most Linux users outside of the ooRexx development team don't know about ooRexx's relocatable installation package. Sounds like a good idea. Looks like we have both learnt something. Cheers, Mark On 7/4/20 7:47 am, René Jansen wrote: > I am also in favour of the new, relocatable installs, I have ooRexx, > Regina and brexx on most of my machines, and it is great if they don’t > byte each other. > Also, running Java in various versions is just a path switch; I don’t > want to go back to the years before that when each OS had their own > ’sacred places’ to put that it. > > René. > > > >> On 6 Apr 2020, at 23:23, P.O. Jonsson > <mailto:oor...@jonases.se>> wrote: >> >> Hi Mark, >> >> It was not me that asked for this change, I was in the middle of an >> entirely different change for the samples when this change >> intercepted my changes. And I did not say we should /ignore it/, I >> say the better solution is to have a relocatable installation package >> like macOS (which is a *nix btw). >> >> I can have 10 different versions of ooRexx installed in parallel and >> the only thing to do to „switch“ is to change the path to point to >> the one I use. I have had ooRexx installed in ~/Applications and in >> /Applications at the same time and none of them disturbs the other. >> From the package I build for ooRexx it is possible to „install“ >> oorexx anywhere with a simple drag uninstalling is as easy as >> dragging to the bin. >> >> I for myself have suffered a lot from this thing earlier on when >> trying out ooRexx on different Linux platforms. Using make - make >> install I ended up not with rexx but rexx-oorexx as an executable. >> renaming it manually (is there a documentation of the switch? how on >> earth can one know about it?) I ended up with a broken installation >> since I was unaware which other items had been switched. Trying to >> run the testsuite then aborted halfway throug. In the end I had to >> manually remove all traces of the installation by hand following the >> manifest file. Since then I learned how to use a rpm or deb package. >> >> Can you point me to a place where I can read about >> update-alternatives? I had never heard about it before I stumbled on >> it here. And I have never been confronted with it in the 6 Linuxes I >> am using for testing. >> >> Hälsningar/Regards/Grüsse, >> P.O. Jonsson >> oor...@jonases.se <mailto:oor...@jonases.se> >> >> >> >>> Am 06.04.2020 um 22:29 schrieb Mark Hessling >> <mailto:m...@rexx.org>>: >>> >>> I'm not sure I'd agree that the optimal solution would be to ignore >>> update-alternatives. update-alternatives is the correct way to have >>> more than 1 package that provides the same functionality on Linux. >>> >>> As René indicated installations worked fine with >>> update-alternatives, and had been working fine. The only problem I >>> had with the package build was its name, and that was due to CMake >>> issues, where on 1 version of CMake the package built ok but with >>> the wrong name and the newer version of CMake didn't even make the >>> package. The problem is CMake (or how to use it properly), not with >>> update-alternatives. >>> >>> Cheers, Mark >>> >>> On 7/4/20 1:14 am, P.O. Jonsson wrote: >>>> Hi René and thanks for the info. >>>> >>>> I had missed the fact that one needed to manually synch >>>> CMakelists.txt with oorexx.spec.in <http://oorexx.spec.in/> (I did >>>> not even realize there was a link) and broke the installer for >>>> CentOS when adding some samples missing CMakeLists.txt. Enrico >>>> explained the connection and I could correct it. I was in the >>>> middle of checking/sorting these two files for the remaining >>>> missing/superfluous files in /samples when Erichs change came in. I >>>> will go ahead and make the necessary changes later this
Re: [Oorexx-devel] [Oorexx-svn] SF.net SVN: oorexx-code-0:[12051] main/trunk/platform/unix
I'm not sure I'd agree that the optimal solution would be to ignore update-alternatives. update-alternatives is the correct way to have more than 1 package that provides the same functionality on Linux. As René indicated installations worked fine with update-alternatives, and had been working fine. The only problem I had with the package build was its name, and that was due to CMake issues, where on 1 version of CMake the package built ok but with the wrong name and the newer version of CMake didn't even make the package. The problem is CMake (or how to use it properly), not with update-alternatives. Cheers, Mark On 7/4/20 1:14 am, P.O. Jonsson wrote: > Hi René and thanks for the info. > > I had missed the fact that one needed to manually synch CMakelists.txt > with oorexx.spec.in <http://oorexx.spec.in> (I did not even realize > there was a link) and broke the installer for CentOS when adding some > samples missing CMakeLists.txt. Enrico explained the connection and I > could correct it. I was in the middle of checking/sorting these two > files for the remaining missing/superfluous files in /samples when > Erichs change came in. I will go ahead and make the necessary changes > later this week, I did not have time to submit it. > > Regarding the „switch“ I think it is a sub-optimal solution to a > problem of a few causing problems for the many. The optimal solution > would be a relocatable ooRexx installation, as we have it now for macOS. > > Regarding checking Jenkins an automated mail service would be beneficial. > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se <mailto:oor...@jonases.se> > > > >> Am 06.04.2020 um 16:56 schrieb René Jansen > <mailto:rvjan...@xs4all.nl>>: >> >> Just last week I generated a .deb for AARCH64 for someone, and it all >> ran fine - checked it first on a Raspi with Ubuntu on it. It is true >> that Erich conferred with me about rolling it back; the check in was >> done in haste when Mark was busy with firefighting (literally! >> Australia). Its intention was to have update-alternatives working >> correctly for ooRexx. It should go back in when someone gets it to work. >> >> I would politely ask everyone to check Jenkins when a change is made. >> This goes for myself too. P.O. is doing very good work with that. I >> wonder if we need to coordinate more on that, so we can at least >> check our own platforms when significant change is made. >> >> René. >> >>> On 6 Apr 2020, at 16:47, P.O. Jonsson >> <mailto:oor...@jonases.se>> wrote: >>> >>> OK thanks for the info. >>> >>> Does this mean that the „switch“ stuff (rexx-oorexx) is gone? >>> >>> Does this also mean that oorexx.spec.in <http://oorexx.spec.in/> is >>> now generated by CMake (or Cpack)? >>> >>> Are there other files that are affected? >>> >>> Unfortunately there seems to be other problems with the installer on >>> the Unix platform, see my other mail. Not sure if this was the reason? >>> >>> Hälsningar/Regards/Grüsse, >>> P.O. Jonsson >>> oor...@jonases.se <mailto:oor...@jonases.se> >>> >>> >>> >>>> Am 06.04.2020 um 16:35 schrieb Erich Steinböck >>>> mailto:erich.steinbo...@gmail.com>>: >>>> >>>> Hi P.O. >>>> this removes the CMake changes by Mark Hessling which were >>>> committed by René. >>>> They had been causing a bunch of issues, where the code duplication >>>> you've seen with oorexx.spec.in <http://oorexx.spec.in/> is one of >>>> them. >>>> >>>> René confirmed that the best option was to roll them back. >>>> ___ >>>> Oorexx-devel mailing list >>>> Oorexx-devel@lists.sourceforge.net >>>> <mailto:Oorexx-devel@lists.sourceforge.net> >>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >>> ___ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> <mailto:Oorexx-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> <mailto: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: http://www.rexxla.org/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Any ideas how to fix bug 1645 ?
Hi Rony, I had the same issue when I made the changes to the CMake processing to build the RPM. To get the configurability of update-alternatives I had to use a user-supplied spec file rather than the CMake-generated one. This appears to have caused CMake to not understand where the generated RPM file is. I updated my CMake to CMake v3 and didn't get the error, however this version of CMake ignored the name of the RPM file and used its own name. I don't know CMake enough to determine how to fix the build issue. Cheers, Mark On 13/8/19 10:53 pm, Rony G. Flatscher wrote: > > Hi there, > > <https://sourceforge.net/p/oorexx/bugs/1645/> reports a problem when > using CMake to create a rpm package for ooRexx on Linux (used to work) > using the command "cpack ./" after successfully running "cmake > -DBUILD_RPM=1 -DOS_DIST=fedora -DCMAKE_BUILD_TYPE=Release > path-2-oorexx-trunk" followed by "make". > > The reason seems that the "make" step creates the so-files in > > > "../_CPack_Packages/Linux/RPM/ooRexx-5.0.0-11902.fedora.x86_64/usr/*lib*/..." > > > whereas cpack tries to copy from > > > "../_CPack_Packages/Linux/RPM/ooRexx-5.0.0-11902.fedora.x86_64/usr/*lib64*/..." > > > which does not exist causing error messages and the abortion of the > rpm building step. > > Any ideas how to fix this? > > TIA, > > ---rony > > > > ___ > 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: http://www.rexxla.org/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
