anyone who wants to give it a try can
do so without affecting the official builds.
As someone pointed out this seems to be a substantial effort and we should keep
it in the SVN repository.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 16. Jul 2022, at 17:11, Rony G. Flatscher wr
My initial mail bounced so I send it to the developers list
This change made one test fail in the SYMBOL testgroup (all platforms I think)
failure] 20220720 02:10:59.042803
Test: TEST_SYMBOL
Class: SYMBOL.testGroup
File: .../ooRexx/base/bif/SYMBOL.testGroup
Line: 144
Failed
sufficient I think?
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
One of the recent commits make the build process break on many platforms,
please have a look, it is breaking at different points for different platforms
it seems
Updating https://svn.code.sf.net/p/oorexx/code-0/main/trunk
<https://svn.code.sf.net/p/oorexx/code-0/main/trunk> at revision
failing. I have reset Virtualbox to default values now. What *DID* help on the
other hand was to deprive the VMs of resources. Changing from 2 cores/4 GB
memory to 1 core/ 2 GB memory made all *nixes pass all tests, so it looks like
the problem were related to Virtualbox rather than to ooRexx
I also found this info, I would be happy if someone worked through this
Read Me
When changing the version number of ooRexx you will need to change the
following files:
oorexx.ver
configure.ac
CHANGES
ReleaseNotes
api/oorexxapi.h (REXX_INTERPRETER_5_x_x)
extensions/rxftp
commits are processed but they may be
> going to the wrong place. Please fill in the new places below. I will add
> this to the todo list once it is complete
>
>
> Build Repository URL
>
> https://svn.code.sf.net/p/oorexx/code-0/main/trunk
> <https://svn.code.sf.net/p/
. Surprisingly this caused some errors in the testing that we did
not see in the past. The building works flawlessly so I assume there is
something wrong with the setting for the testing. I will report the outcome.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
I have great news from down-under
Mark Hessling just confirmed that he could build and test the latest ooRexx
flawlessly on M1 Mac. Here the result
Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 19 Dec 2022
OS Name:DARWIN
SysVersion: Darwin 21.6.0
Tests ran
Regarding the documentation I have merged 5.0.0html and 5.0.0beta into
5.0.0beta and then copied all into 5.0.0_Release_Candidate. Everything amended
from this point on should arrive in 5.0.0_Release_Candidate only.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 18. Dec 2022, at
> On 19. Dec 2022, at 11:23, Rony G. Flatscher wrote:
>
> Dear P.O.,
>
> On 18.12.2022 22:42, ooRexx wrote:
>> Regarding the documentation I have merged 5.0.0html and 5.0.0beta into
>> 5.0.0beta and then copied all into 5.0.0_Release_Candidate. Everything
>>
Dear Rony,
I am a bit busy with personal matters but will have a look tomorrow, at a
glance I did not see a difference to the existing pdf.xsl (5 lines after the
needle)
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 20. Dec 2022, at 16:44, Rony G. Flatscher wrote:
>
some time ago.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 20. Dec 2022, at 20:05, Rony G. Flatscher wrote:
>
> All intended changes to docs/branches/5.0.0 are done with the exception of
> replacing "pdf.xsl" in "docs/branches/5.0.0/tools/bldoc_orx&q
:-)
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 20. Dec 2022, at 14:28, Rony G. Flatscher wrote:
>
> While updating the documentation ent files for trunk I also changed the date
> related information.
>
> The ent (entity files) contain the following bo
ld be solvable. Thanks for noticing.
_______
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
I just tried on Ubuntu and it worked just fine there.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 21. Dec 2022, at 16:21, ooRexx wrote:
>
>
>> On 21. Dec 2022, at 15:57, Gilbert Barmwater > <mailto:gi...@bellsouth.net>> wrote:
>>
>> H
default Win zipper?
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 21. Dec 2022, at 16:27, Gilbert Barmwater wrote:
>
> +1
>
> Thanks for investigating!
>
> On 12/21/2022 10:21 AM, ooRexx wrote:
>>
>>> On 21. Dec 2022, at 15:57, Gilbert Barm
7zip) in
the HowTo for the DocBuild or should such changes be added to the
release-steps.txt? They are not per see related to the new release.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 21. Dec 2022, at 15:57, Gilbert Barmwater wrote:
>
> Hi P.O.,
>
> I saw new
I went through my HowTo and amended a couple of
things. fop is now 2.8 on macOS for instance, it used to be 2.4 when I used it
first time. Will commit it today but will check the Linux version first.___
Oorexx-devel mailing list
Oorexx-devel@lists.source
Bin there - done that… that link was about large files, these files are small
in comparison, but if you can’t join them beat them, right? 7zip works it seems
to I will go with that.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 22. Dec 2022, at 12:22, Rony G. Flatscher wr
We are currently making all changes to
/oorexx/code-0/docs/branches/5.0.0/
/oorexx/code-0/main/branches/5.0.0/
But the document where to document the changes release-steps.txt is in the
trunk
/oorexx/code-0/main/trunk/
Are we supposed to keep two separat SVN trees active while this is going
Dear Gil,
If you look closely there ARE changes to the html version, all good ones as
proposed by Rony.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 22. Dec 2022, at 14:07, Gilbert Barmwater wrote:
>
> As I suspected, this fixed the problem! Good work!
>
> One
e to a document within
that folder. We use svn log to find that out.
What you are proposing - does that require a change in the documentation
building script?
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 22. Dec 2022, at 14:27, Rony G. Flatscher wrote:
>
> Sleep
SVN revision change. Hence my
question too Rony.
per aspera ad Astra…
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 22. Dec 2022, at 14:58, Gilbert Barmwater wrote:
>
> Back in July (seems like years ago), I modified the ooRexx version of the
> document build tools.
with the build&test system.
_______
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
chimney to clean...
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 22. Dec 2022, at 19:20, Rony G. Flatscher wrote:
>
> On 22.12.2022 19:10, Gilbert Barmwater wrote:
>>
>> If this is the final step, I think we should have P.O. build a new set of
>> d
installation (and Apple blocking the
installation on macOS) is something that should be given high priority once
ooRexx 5 is officially released IMO. On the ToDo list.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 22. Dec 2022, at 19:26, Sahananda Sahananda wrote:
>
> H
Agree.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 22. Dec 2022, at 20:00, René Jansen wrote:
>
> +1
>
>> On 22 Dec 2022, at 14:10, Rony G. Flatscher wrote:
>>
>> Assuming that the rebuilds of the release version of the documentation and
>&
Good point Gil, this is the same for macOS so we need to stop amending the
documentation and then someone could do the final commit, maybe tomorrow?
I have done all I could think of, there are a few bugs reported by me that
should probably be “won’t Fix”.
Hälsningar/Regards/Grüsse,
ooRexx
oor
Since the documentation was not built it was outdated when Windows was built,
I will fix this, will take one hour.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 23. Dec 2022, at 15:13, Rony G. Flatscher wrote:
>
> Just downloaded the new 64-bit windows build that
corrected. I will take care of
a last rebuild with the correct documentation manually
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 23. Dec 2022, at 16:52, Rony G. Flatscher wrote:
>
> On 23.12.2022 15:38, Rony G. Flatscher wrote:
>> On 23.12.2022 15:16, ooRexx wrote
Due to this unnecessary commit Windows and macOS are now getting another
revision than the rest. Should we accept that or should I try to manually go
back one version? This is causing a LOT of stress one day before Christmas.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> Be
> On 23. Dec 2022, at 17:33, Rony G. Flatscher wrote:
>
> On 23.12.2022 17:29, ooRexx wrote:
>> Due to this unnecessary commit Windows and macOS are now getting another
>> revision than the rest. Should we accept that or should I try to manually go
>> back one versio
There is the possibility to revert a skunky commit, along the lines of svn
merge -c 12584 Can you do that?
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/lis
,
ooRexx
oor...@jonases.se
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
played me a trick and erased the entire oorexx-docs
when I ordered it to delete oorexx-docs/5.0.0beta :-(
I recreated oorexx-docs and uploaded 5.0.0 again and I have asked on
Sourceforge to get the other folders back from a backup but I guess they are
not so active over Christmas
If anyone have
ow to accomplish this?
_______
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
yout so to speak.
I hope there is a backup on Sourceforge, I have not yet heard from the support
there.
I am upgrading the Jenkins system today and will start it later tonight.
Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se
> On 26. Dec 2022, at 02:04, Gilbert Barmwater wrote:
>
>
d by 12588 that you recently
> committed. However there is a problem with the naming of the builds. Here is
> an example: /oorexx/5.1.0beta/ooRexx-5.0.0-12558.linuxmint20.x86_64.deb
> Note the 5.0.0 in the file name. Hopefully this is easy to fix.
>
> Gil
>
> On 12/27/2022 8:19 AM
.,
>
> I noticed this morning a bunch of new files "released" on SF, both documents
> and builds. I assume these were triggered by 12588 that you recently
> committed. However there is a problem with the naming of the builds. Here is
> an example: /oorexx/5.1.0beta/ooR
ed that I have a copy of the 4.1.3 PDFs. I'll send you a copy.
>
> Rick
>
> On Sun, Dec 25, 2022 at 6:04 PM ooRexx <mailto:oor...@jonases.se>> wrote:
> I have some god news and some bad news
>
> The good news:
>
> FreeBSD is now revision 12583, I rebui
For 5.1.0beta from trunk I have now set Windows and macOS to build only after
(5.1.0beta) documentation has been built. If there are no changes to
documentation the delay will be in the order of seconds.
I have also set Docbuild project from trunk to go to oorexx-docs/5.1.0beta,
currently all
1 Mac
running Ventura (macOS 13)
- (almost) all test passes, some things todo for 5.1.0 (more about that next
year)
I found something interesting in the 4.1.3 documentation:
ooRexx-4.1.3-all.zip
ooRexx-4.1.3-html.zip
ooRexx-4.1.3-pdf.zip
Would it make sense to make the same for 5.0.0 (at least the
xextensions.pdf
> What do you think?
>
> ---rony
> _______
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______
m doing anything to the build machine & it’s scripts, I will
let you know when I have something working.
> ---
>
> Ad release version of ooRexx without revision information: once we can create
> the binaries without revision information we could create new distributions
> of 5.0
Dear Leslie,
We use cURL for building the macOS installer, it is a shell script but an
example of a command line looks like this:
# use cURL to download the latest documentation (this takes some time)
curl -L --insecure
https://sourceforge.net/projects/oorexx/files/oorexx-docs/5.0.0
that we now have an automated way to update also
docs-bildutils
The script is launched from the Project ooRexx-docs-bildutils-check and
hopefully we can provide the necessary input to the script from CMakeLists.txt
in a later stage.
I did only consider files so far, I have a question on the folde
I just committed a script that will monitor
svn.code.sf.net/p/oorexx/code-0/docs/trunk/tools/ and upload any new items to
oorexx-bildutils in the Files section. The script will be running once a day on
Jenkins and make sure the Files/oorexx-bildutils section is up to date to
minimise manual
:
>>>
>>> Thanks for catching this Rony! I will investigate as I have time along
>>> with the problem with setup.rex on Windows using a non-existent FOP mirror.
>>>
>>> Gil
>>>
>>> On 1/3/2023 12:32 PM, Rony G. Flatscher wrote:
The IBMZ Agent (René's IBM LinuxONE Rockhopper with Ubuntu 18.04.5) was
available again temporarily so I took the opportunity to make a retrospekive
build for 5.0.0:
ooRexx-5.0.0-12583.ubuntu1804.s390x.deb
I have also built for the latest 5.1.0 these items:
ooRexx-5.1.0-12625.ubunt
so it needs to be the there or the build fails. Will take some days though.
> ---
>
> Ad failing test: that looks strange. If you repeat the tests, does it
> re-occur?
>
It does occur every time, I tried a number of times and even rebuilt ooRexx to
be sure. Since I did not see th
/tools/RailRoadDiagrams/rr-1.67-java8.zip
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
will continue to run and the Windows platform will be available
for building but almost no *nixes.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net
On Windows (and other platforms) we have the annoying case that the Ticker test
misses a tick or two due to time jitter in the virtual machines, like here:
[failure] 20230406 16:21:37.70
Test: TEST_TICKER_THREE_ARGS_STRING_TRIGGER
Class: Ticker.testGroup
File: ...\ooRexx\base
the native Windows (32 and 64 bit) testing,
I hope you can see what causes the error from this output (the sysdrive error
is probably a glitch)
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter:REXX-ooRexx_5.1.0(MT)_32-bit 6.05 6 Apr 2023
OS Name
As I reported earlier the installers for ooRexx 5.0.0 is broken for Raspberry
P;, the /lib branch (and maybe more) is missing in the installed ooRexx.
Running a simple rexx -v or just rexx will run and look perfectly normal but as
soon as a library is loaded there will be a failure.
Our
ote:
>
> Hi P.O.,
> yes, thanks, rebuild the broken installers.
> _______
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
____
hard-coded features and
other problems that needed changing.
I have done a source package for ooRexx 5.0.0 manually following (basically)
your steps and uploaded it just now, I will ask that Mark have a go at testing
it.
There are no signatures added for now.
FYI the automatic building of a
*
>
> **Status:** accepted
> **Group:** None
> **Created:** Sun May 07, 2023 08:15 PM UTC by Per Olov Jonsson
> **Last Updated:** Sun May 07, 2023 08:15 PM UTC
> **Owner:** Per Olov Jonsson
>
>
> For Windows there is no entry referring to rxSock.cls documentation
> On 10. May 2023, at 11:16, Rick McGuire wrote:
>
>
>
> On Wed, May 10, 2023 at 3:51 AM ooRexx <mailto:oor...@jonases.se>> wrote:
> I added the missing softlink so that Windows users can find rxsock.pdf, Is
> this the right way to do it on sourceforge?
>
Hi Franz,
Nice to hear that you want to try out ooRexx!
Indeed the package for OpenSuse (and all other packages I think) is unsigned so
you would need to ignore the warning when it arrives. The steps would be
(assuming the installer is in Downloads):
noob:~/Downloads> sudo zypper inst
Hi,
Suse is one of the most unproblematic/stable platforms for ooRexx, I have
hardly ever seen a problem in the testing so go ahead and do not hesitate to
report back any problem you find (I bet one bottle of beer that you won’t find
any :-) )
Try to ignore the “Beta” in the name of the
Just one more question and I be gone: re #1895
<https://sourceforge.net/p/oorexx/bugs/1895/> and the fact that 4 (vital) files
are missing on sourceforge in the files/oorexx/5.0.0 section
ReadMe.txt
ReleaseNotes
INSTALL.txt
CHANGES.txt
Since we cannot modify them for 5.0.0 should we (i)
h and the 5.0.1 milestone used.
>>>
Currently we do not have a 5.0.1 branch in SVN, so it is not possible to commit
anything specifically to 5.0.1; all go into trunk which is then uploaded to
5.1.0beta on sourceforge.
Are you saying that we should have branched off a 5.0.1 from 5.0.
> On 10. May 2023, at 20:37, Gilbert Barmwater wrote:
>
> On 5/10/2023 1:27 PM, Rick McGuire wrote:
>>
>>
>> On Wed, May 10, 2023 at 12:22 PM ooRexx > <mailto:oor...@jonases.se>> wrote:
>> I am sorry but I have to come back to this item:
>>
Hi,
I am not sure I understand the question. Once you have installed ooRexx it
should work out of the box, there is nothing to configure on the ooRexx side,
you just call it with rexx myprogram.rex, you can leave out the extension so
rexx myprogram suffices. Similar to how you call a Python
preparing the
next bug fix release. THEN, when there is time for 5.1.0 in the distant future
we copy trunk to main/branches/5.1 and so on.
Looking at the “release rate” for ooRexx 4 the minor bug fix releases have been
3 months to 1.5 year in-between, I interpret this as on a need-to-fix time
a lot for OpenSuse, but I have time.
>> "It's a rainy day, hallelujah ..."
>> 🤗
>>
>> Grüsse aus Österreich
>> Franz
>>
>> Am Fr., 12. Mai 2023 um 14:08 Uhr schrieb ooRexx > <mailto:oor...@jonases.se>>:
>> Hi,
>>
>
,
P.O. Jonsson
oor...@jonases.se
> On 12. May 2023, at 16:03, ooRexx wrote:
>
>
>> On 12. May 2023, at 15:58, CV Bruce > <mailto:cvbr...@gmail.com>> wrote:
>>
>> On Linux and Unix, your Rexx program needs to start with a line like
>> #!/path/to/re
I have tried to close all tickets I was responsible for and moved other forward
to 5.1.0 or 5.0.1 (change to none where I did so in error), there is only a
small number of tickets left can you please have a look and do something about
“your” tickets so that ooRexx can be closed.
1837
egg for Rony I have created ooRexx 5.0.0 portable installers
for most platforms
I have also recompiled most 5.0.0 installers and added the documentation (that
was missing for most Unix/Linux platforms), should I replace the ones from
December last year, or do we wait with that for 5.1.0
ation for every build, and for all
platforms or only a selection. Send me an email off the list if you are
interested indicating Email and what platforms you are interested in.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
___
Oorexx-
of just skipping the test
:-( can someone please change the test to work as it was originally intended?
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter:REXX-ooRexx_5.1.0(MT)_64-bit 6.05 21 Jul 2023
OS Name:LINUX
SysVersion: Linux 5.
CK_PACKAGE_NAME}-${ORX_MAJOR}.${ORX_MINOR}.${ORX_MOD_LVL}-${CPACK_PACKAGE_RELEASE}")
The package looks like this
oorexx-5.1.0-12706
|-- usr
| |-- local
||-- CHANGES
||-- CMake-build-readme.txt
||-- CMakeLists.txt
...
i.e. the default path is included in the compressed s
uot; ::end"
1 *-* reply 1
>L> "1"
>>> "1"
::end
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
> On 22. Jul 2023, at 13:28, Jeremy Nicoll
> wrote:
>
> On Sat, 22 Jul 2023, at 09:53, ooRexx wrote:
>> I changed
Dear Rony,
This did not work (the path inside /Applications/ooRexx is still messed up for
the installation because of my “fix") so I need to remove that line for the
source package and think of something else. I think moving to a temp dir inside
the build path would be more lo
t.
>
> HTH
>
> —-rony
>
> Rony G. Flatscher (mobil/e)
>
>> Am 22.07.2023 um 15:20 schrieb ooRexx :
>>
>> Dear Rony,
>>
>> This did not work (the path inside /Applications/ooRexx is still messed up
>> for the installation because o
> Rony G. Flatscher (mobil/e)
>
>> Am 22.07.2023 um 15:20 schrieb ooRexx :
>>
>> Dear Rony,
>>
>> This did not work (the path inside /Applications/ooRexx is still messed up
>> for the installation because of my “fix") so I need to remove that lin
There is one failing test in the Trace Testgroups for Ubuntu 16, Ubuntu 20 and
22 and all other platforms all pass the same test. Please have a look
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter:REXX-ooRexx_5.1.0(MT)_64-bit 6.05 23 Jul 2023
OS Name
All other platforms seems to pass this test, Windows 7 not. Please have a look.
Executing ...\ooRexx\samples\properties.testGroup
ooTest Framework - Automated Test of the ooRexx Interpreter
Interpreter:REXX-ooRexx_5.1.0(MT)_32-bit 6.05 23 Jul 2023
OS Name:WindowsNT
Now I have this Failure in macOS 10 as well, In the log file I see this
Executing .../ooRexx/base/keyword/TRACE.testGroup
758 *-* trace off
Executing .../ooRexx/base/keyword/USE.testGroup
Which seems to imply that the trace instruction is not captured in the test?
The error message at the end
from the lates build attempt:
Remote file is newer, retrieving.
--2023-08-25 10:38:55--
https://kumisystems.dl.sourceforge.net/project/oorexx/oorexx-docs/5.1.0beta/rexxextensions.pdf
<https://kumisystems.dl.sourceforge.net/project/oorexx/oorexx-docs/5.1.0beta/rexxextensions.pdf>
Connect
will work automatically.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
> Am 27.08.2023 um 12:05 schrieb oorexx :
>
> Dear Gil,
>
> The problem follows from the fact that the downloading of the documentation
> is hardcoded into a script on the Windows build machine.
Dear all,
At the moment the building of the documentation is manually triggered, since
Jenkins cannot find SVN on the build machine (it is there and works, unclear
why Jenkins does not detect it). When making the latest documentation I noticed
the following ooRexx build levels:
12722 for
arliest. And we should agree on a
procedure before that, based on the list that Rick started at 5.0.0.
> ---rony
>
>
@Rony: can you explain what the printed information below actually means?
Should something be changed whenever a commit is made (i.e. before the
documentation is bu
t Jon provided. I've
> tried to commit the change, but I don't have the appropriate access.
> Should I send the change to someone else?
>
> --
> taf
>
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@l
the
documentation. Example todays build of Rexref.pdf
ooRexx Documentation 5.1.0 Open Object Rexx
Reference
Edition 2023.01.01 (last revised on 20221024 with r12526
I guess this is not what it should say.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonase
ran: 23935
Assertions: 398125
Failures: 0
Errors: 2
[Framework exception] 20231027 23:59:53.266639
Type: Trap Severity: Fatal
File: .../ooRexx/base/directives/search_order_cls.testGroup
Line: 2110
Initial call of test container failed
Condition
It seems Fedora and OpenSuse have the same problems so it may be a *nix problem
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
> On 27. Oct 2023, at 16:31, ooRexx wrote:
>
> M1 Mac running macOS 13 Ventura (or higher) is failing two tests. Last
> successful build was
We are getting loads of this warning when building ooRexx at the moment:
CMake Deprecation Warning at CMakeLists.txt:48 (cmake_minimum_required):
Compatibility with CMake < 3.5 will be removed from a future version of
CMake.
It emanates from this piece in CMakeLists.txt:
message(STA
oday, 1.1.2024? It's a nice date to
remember :-)
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
_______
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
t;
> when I try to browse the SVN through the sourceforge SVN web interface
> <https://sourceforge.net/p/oorexx/code-0/> I see this message:
>
> Browsing this repo on the web is unavailable currently. To fix, please try a
> Repository Refresh <https://sourceforge.net/p/o
present packaging and installation of ooRexx can therefore not take
> advantage of universal packages available on macOS (because of rexx.img) such
> that we should start to stop producing the universal macOS version and
> instead have two different macOS packages created, one
I wanted to split the macOS installer and have prepared 2 new jobs. I have
disabled ooRexx-macOS12-build and created ooRexx-macOS12-X86_64-build and
ooRexx-macOS12-ARM64-build.
I have then replaced in those jobs
-DBUILD_OSX_UNIVERSAL_BINARIES=1
With (respectively)
-DBUILD_X86_64_BINARIES=1
t/p/oorexx/bugs/1931/>
I have modified the uploading job to upload the X86-only installer for Intel HW.
We have the option to change the build job on the M1 Mac kindly made available
be Mark to upload either an installer with a “fat” binary or an ARM-only
binary, what do we want?
More inline
It seems we currently have ALL platforms failing this test, can the person
(Rony?) who committed lately check if there was a side-effect of the changes
and/or amend the test to the new behaviour.
Executing .../ooRexx/base/runtime.objects/environmentEntries.testGroup
/tmp
candidate for multiple process
debugging ;-)
If you look at the 32 and 64 bit Windows running on Native Windows they do not
show these problems.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
> On 3. Apr 2024, at 16:45, Rony G. Flatscher wrote:
>
> On 03.04.2024 16:2
se,
P.O. Jonsson
oor...@jonases.se
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
A progress report on my activites today.
The test was partially successful, if you look at Sourceforge you will find two
folders 5.0.0test under /files/oorexx and /files/oorexx-doc. They are staged so
only visible if you are logged on to sourceforge.
For the understanding of how Jenkins works
kRPM: Will use GENERATED spec file:
/home/osboxes/workspace/ooRexx-CentOS9-build/oorexxBuild/_CPack_Packages/Linux/RPM/SPECS/oorexx.spec
CPack: - package:
/home/osboxes/workspace/ooRexx-CentOS9-build/oorexxBuild/oorexx-5.1.0-12831.centos9.x86_64.rpm
generated.
+ pkill rxapi
+ sudo rpm --upgrade
1 - 100 of 452 matches
Mail list logo
