ugger.
>
> --
> Gil Barmwater
>
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ___
&
t; https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
--
*Erico Mendonca*
Solution Architect
*SUSE*
[image: https://www.suse.com/susecon/] <https://www.suse.com/susecon/>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Not entirely related, but if you guys want to automate some builds,
consider using Open Build Service (just call the API, even from Jenkins).
Here's an example:
https://api.opensuse.org/apidocs/#/Sources%20-%20Packages/post_source__project_name___package_name__cmd_runservice
In this case it's trig
nt code?
On Sat, Dec 23, 2023 at 6:36 PM Erico Mendonca
wrote:
>
>
> Em sáb., 23 de dez. de 2023 10:27, Rony G. Flatscher <
> rony.flatsc...@wu.ac.at> escreveu:
>
>> Great!
>>
>> Clicking on the "RPM Lint" tab for 15.5 gives the following hin
Em sáb., 23 de dez. de 2023 10:27, Rony G. Flatscher <
rony.flatsc...@wu.ac.at> escreveu:
> Great!
>
> Clicking on the "RPM Lint" tab for 15.5 gives the following hint/advice:
>
> liboorexx4.ppc64le: I: binary-or-shlib-calls-gethostbyname
> /usr/lib64/librxsock.so.4
> The binary calls gethostbynam
/mzm8ObKlXNBXaPhhexqLFs68pOeBx+PXo7V1yiW/Lzy+6h4OY3WV/4Cv+et0n3eLa+RGosUP9nkU2jvyXAqE8ltqZPs1/4L4BVAABca3QMue/DRmH6Mv+ffbx+ltOXd8f2P8diiAAiiAAiiAAiiAAiiAAiiAAiiAAiiAAiiAAtUk8A/5wXY+a4HbHwBJRU5ErkJggg==
*
*Erico Mendonca*
Premium Services
SUSE
___
Oorexx-devel
() and the end of
line encoding should be patchable.
Could anyone cross-check my SPEC to see if I missed anything?
[cid:55200c42-42fa-4a33-a297-b18618e6a887]
Erico Mendonca
Premium Services
SUSE
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourcefor
There are also the SUSE builds in Open Build Service:
https://build.opensuse.org/package/show/devel:languages:misc/ooRexx
ooRexx 4.2.0 has been distributed in SUSE distros this way since openSUSE 13.2.
OBS runs in a similar fashion as Jenkins, but instead of slaves, it
instantiates a temporary
Hi René,
Actually we didn’t need to disable optimizations before. We did see this
problem with ooRexx 4.2.0 recently as well, and our colleague Marguerite
disable the optimizations. This appears to be a GCC bug.
I’ll check tomorrow if there is an open bug and see what we can do about it.
--
—
Em 07/07/16 05:01, "Erich Steinböck" escreveu:
> Erico, these are the tests which fail if rxapi isn't running
Ah ok, I’ll start rxapi before running them.
> I don't know why it's initially been put to /usr/bin. The code currently
> first tries to open rexx.cat through NLSPATH, and, if that fa
Hello all,
Another set of proposed patches...
See the contents here (click on each file name in the file list to see the
contents): https://build.opensuse.org/package/show/home:emendonca/oorexx5
- call_setgroups_before_setuid.patch: this is a security precaution against
chroot traversing.
- de
De: Moritz Hoffmann
I think a clean solution would be to use UNIX sockets on Linux and similar
systems. I don't know about Mac or Windows but I'm sure there exists something
equivalent. Then, each user would have its own instance of the api daemon that
is accessible using a socket stored in th
Hello Michael,
>
>Is GCC 6.x even out yet?
>
Officially yes (it’s on 6.1.x already). But none of the release-grade distros
are using it yet AFAIK.
So far openSUSE Tumbleweed/Factory, Fedora 24, Ubuntu 16.10 and Debian Stretch
have it. All are due to be released in the next few months.
>Ubunt
Hi René,
>
>2a) the current code just looks whether it?s there or not, and does not read
>the process id. We could do without it. First, I tried to read ooRexx.pid to
>kill the process, but most of the time the file was there, but the process was
>gone allready. So now I do:
>
>sudo kill -9 $(
>>
>> I have not quite figured out how to schedule a sudo command in jenkins
>> I'm doing a "sudo install make" in Jenkins project
>> "ooRexx-test-Raspbian-Jessie" to install rexx for the later execution of
>> testOOrexx. I do this, as I wasn't happy with executing directly from the
>> build/b
>
> Erico, when building all those distributions, might you be able to run
> ooRexx regression tests (see
> https://sourceforge.net/p/oorexx/code-0/HEAD/tree/test/trunk/) as a
> post-build step for any successful build?
>
Hi Erich,
Yeah I guess so. I'll work on it as soon as get to a computer.
-
>Do you have a pointer to the description of the new restrictions? This
>essentially makes macros useless for a lot of purposes. Also, I suspect
>there might be something else going on here, because RexxMethod1 and
>wholenumber_t should most definitely be defined by that point.
>
These are the off
>>
>> I haven?t added the proper packaging logic to my SPEC yet
>>
>
>Erico, will you (later on) provide a patch for the SPEC file, too?
>
Erich,
It’s there already . Check the SPEC file I’m using (and constantly modifying)
is the one available at
https://build.opensuse.org/package/view_file/h
>
>Never mind, I missed that the initialization was moved to the CPP file.
>
For a moment there I had a mini-heart attack ☺
--
— Erico Mendonça
Dedicated Support Engineer
SUSE
--
Attend Shape: An AT&T Tech Expo July 1
>
>Is the problem with the token OPTIONAL_RexxStringObject? The fix could be a
>simple as adding some additional defines for all of the OPTIONAL_* types at
>the top of oorexxapi.h.
>
Not only that. In this call, for example:
RexxMethod1(wholenumber_t, rexx_queue_queue,
OPTIONAL_RexxStringObj
>
>Wait, the changes to the memory constants are losing all of the initialized
>values. This will completely break memory management.
>
Hi Rick,
Ouch. Sorry for that. You certainly have a lot more intimacy with the code than
I do. Could you fix it?
--
— Erico Mendonça
Dedicated Support Engin
>Erico, I've committed all patches to trunk.
>There's one exception, systemd-fixes.patch, for which we will need the
>"50-rxapid.preset" file also included in the diff.
>
>Also, does the name, "50-rxapid.preset" make sense? Will a new preset file
>be created for each successive ooRexx version/rele
>Erico, would adding -std=gnu++98 avoid the issue when compiling with gcc 6?
>
>GCC will now require every identifier to be valid beforehand
>>
>Do you have a link which details this change?
>Do you have a short example of ooRexx preprocessor code which now fails
>with gcc 6?
>
>I can look into the
Hello all,
I’d like to request help from someone more experienced with the ooRexx code to
rewrite the code/macros used for generating extension sources.
Unfortunately after GCC 6.x officially adopted C11, some things are
fundamentally different. This is a one-way decision, and all Linux distr
I worked on a few patches today, so now this is what I have building on all
distros:
fix_desktop_version.patch: this fixes the XDG desktop file to make it compliant.
fix_icon_path.patch: this relocates the icon to the proper XDG-approved path
fix_samples_permissions.patch: this fixes the permissi
Hi Erich,
>> - failing builds on i586: I removed a “/*” in CMakeLists.txt. See the
>> fix_arch_detection.patch for details.
>>
> I've applied the patch to trunk
Thanks!
>> - systemd: I removed the requirement for syslog, as some distros use a
>> different logging system, like syslog-ng. I also
Hello all,
I worked on solving some of the problems mentioned here earlier:
- failing builds on i586: I removed a “/*” in CMakeLists.txt. See the
fix_arch_detection.patch for details.
- undefined symbols in CentOS 6 and SLE 11 SP4: this is a weird one. GCC 4.3.4
behaves differently about where t
--
— Erico Mendonça
Dedicated Support Engineer
SUSE
Em 21/06/16 18:30, "oorexx-devel-requ...@lists.sourceforge.net"
escreveu:
>Hi Erico,
>
>
>I have a funny problem on OpenSUSE Tumbleweed X86_64:
>
>[ 85%] Building CXX object
>CMakeFiles/orxncurses.dir/extensions/orxncurses/orxncurses.cpp.
>
>Hi Erico,
>
>2) is very probably a broken gcc - I recognize the errors, and generally at
>least 4.8 is needed to successfully compile and link.
>
>Great progress!
>
Hi René,
I found a reference that could apply to the case:
http://stackoverflow.com/questions/11336477/gcc-will-not-properly-in
>
>Erico, this is for sure a great start!!!
>
>
>| I have suggestions that worked for us while packaging ooRexx 4.2.0 that
>could be adopted upstream
>
>I believe we should adopt as much as possible
>
Hi Erich,
Great! I’ll make sure to present them here first so everybody can check them.
>
>| 7
Hello all,
I placed ooRexx 5.0 (from the code-0 branch) up into SUSE's Open Build Service,
and the report is back.
Please bear with me, as there are quite a few errors/warnings. I don't have
solutions for them all, and sure would like to hear from all of you. I have
suggestions that worked fo
--
— Erico Mendonça
Dedicated Support Engineer
SUSE
>Hi Erico,
>
Hi Rene, sorry for the delay.
>at the moment 5.00 is at svn://svn.code.sf.net/p/oorexx/code-0/main/trunk
> but we will soon branch for
>release, after test have been run for the different platforms.
>If you need commit access
>
>Dear fellow-developer,
>
>I would like to start a concentrated effort to release ooRexx 5.00. Your help
>is needed. Some time ago - how quickly time goes by - we spoke about this.
>
>We need to have an inventory of the things to test and to fix before we do.
>Last time, we made a division of O
> >
> > Some time ago I inquired if I might assist with set up of Ubuntu versions
> > on the ooRexx build machine.
> >
> > Ubuntu has
Send Oorexx-devel mailing list submissions to
oorexx-devel@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https:/
>Date: Tue, 15 Mar 2016 13:26:04 +0100
>From: "Rony G. Flatscher"
>Subject: Re: [Oorexx-devel] Question ad MacOSX El Capitan and creating
>>
>> Our patch can be seen here:
>> https://build.opensuse.org/package/show/devel:languages:misc/ooRexx
>
>thank you very much for this valuable hint!
Sure.
>Date: Sun, 13 Mar 2016 12:31:46 -0700
>From: CVBruce
>
>Are you able to get around the rexx.cat by coding an NLSPATH in the
>environment? So we would need PATH, LD_LIBRARY_PATH, and NLSPATH.
>
>As to opening a bug, seems like the right thing to do.
>
>>On Mar 13, 2016, at 11:13 AM, Rony G. Fla
Date: Thu, 11 Feb 2016 20:43:03 -0600
From: "J. Leslie Turriff"
> It's been quite a while since I attempted to access a device using
> ttyUSBx;
>at least on my distro, I gave up when I found that the x was hardcoded in the
>driver and the author didn't want to bother changing it because
>From: "Bill Turner, WB4ALM"
>Subject: Re: [Oorexx-devel] Need help reading/writing to a "com"
> port...
>
>I would like to thank everybody that has provided ideas on serial port
>communications using ooRexx.
>
>I do not have a final solution yet, but with your help I have had
>partial su
> From: "Mike Cowlishaw"
> Subject: Re: [Oorexx-devel] Need help reading/writing to a "com"
> port...
>
>
> Under Windows or OS/2 the MODE command is used to set baud rates etc. (try
> mode /? for details).
>
I believe Mike's program should work fine under Linux. You just need to
exchan
encies (e.g. on a minimum ooRexx version) and if
not installed have an
automated installation of the prerequisite(s)?
Again, thank you very much for your information!
Cheers
---rony
On 24.06.2015 06:22, Erico Mendonca wrote:
> Hello Rony,
> Sure, I can give you some pointers on RPM pa
above. If you have any questions,
just mail me.
>>> "Rony G. Flatscher" 23/06/15 12:13 >>>
Hi Erico,
On 23.06.2015 16:21, Erico Mendonca wrote:
> Don't forget:
> https://build.opensuse.org/package/show/home:PerryWerneck:pw3270/ooRexx
>
> and
&
Don't forget:
https://build.opensuse.org/package/show/home:PerryWerneck:pw3270/ooRexx
and
https://build.opensuse.org/package/show/devel:languages:misc/ooRexx
Don't think it could be easily integrated with Jenkins, though.
>>> René Jansen 21/06/15 7:48 >>>
Hi Erich,
you bring up a good poin
Hello all,
Again, me and Perry Werneck have been building ooRexx for SUSE and other
distros on SUSE's Build Service for a while now. It's available from SUSE's
official repositories.
This is the devel project, for SUSE-based distros and RHEL:
https://build.opensuse.org/package/show/devel:langua
Hello Jon,
Well, I can humbly offer our page at the SUSE build service. We've been
cranking out fixed/enhanced packages for all SUSE-based distros for a while
now, after talking to David at the time about it. It started out as a necessity
(a couple of customers needed it badly), but now there ar
Hello Michael,
I think you may want to take a look at our (unnofficial) builds on SUSE's Build
Service:
https://build.opensuse.org/package/show/devel:languages:misc/ooRexx
These started out of necessity to re-package ooRexx for SUSE and include it
into the official repositories for the distro (
Hello everybody,I wish to invite you to check out the ooRexx packages I made available for all flavors of SUSE, automatically built via the SUSE Build Service:https://build.opensuse.org/package/show?package=ooRexx&project=home%3AemendoncaCurrently there are packages built for the following platform
I see. I don't mean to duplicate your efforts. Could I venture into maintaining an ooRexx package at OBS based on your stable builds then? It could be a step towards including ooRexx in the distro by default. All packages that go into openSUSE/SLE are generated automatically from the OBS.Erico Mend
Hello,I'd like to start building ooRexx on SUSE's public Build Service (build.opensuse.org). Any special considerations or stuff I should avoid so as not to break any specific builds for other non-linux platforms? It's a huge effort and may take a while to get everything right. But once it's full
>>> On 2/24/2011 at 05:44 PM, in message
, Mark Miesfeld
wrote:
> On Thu, Feb 24, 2011 at 12:05 PM, Erico Mendonca
> wrote:
>
> > Does ooRexx for Windows have an unattended/silent installation option?
>
> Yes it does.
>
> The uninstaller take
Does ooRexx for Windows have an unattended/silent installation option?
I need to install it on a few hundred machines...
--
-- Erico Mendonça
Novell Designated Support Engineer
+55-61-9115-3256
--
Free Software Down
>>> On 2/7/2011 at 08:55 PM, in message
, Mark Miesfeld
wrote:
> Excellent Jean-Louis. I forgot to methion DESTDIR.
>
> If you can build on a Mac and have copious free time, maybe you'd like
> to tackle building an installable package?
>
It appears the only "official" method for creating
Hi all,
I just found the hard way that the ooRexx 4.1 RPM for SLES (and possibly
SLED/OpenSUSE as well) does not have the proper requirements to allow it to be
installed through AutoYaST. AutoYaST is the unattended installation engine by
SUSE.
Since it resolves dependencies at installation ti
>>> On 10/19/2010 at 01:31 PM, in message
, Mark Miesfeld
wrote:
>> No, they do not. In the postinstall section of the RPM spec file we run
>> ldconfig after all the files have been installed. ldconfig is smart enough
> to
>> look in all the subdirs of /usr/lib and put them in the library s
>>> On 9/24/2010 at 10:53 AM, in message <4c9cad70.3080...@gmail.com>, David
Ashley
wrote:
> I took your spec file as a starting point, but I did make a some changes I
> thought enhance and clarify things a bit more. The good news is that spec
> file
> is much cleaner, the bad news is th
>>> On 9/23/2010 at 05:53 PM, in message <4c9bbe54.4070...@gmail.com>, David
>>> Ashley
wrote:
> All -
>
> Although not yet commited, I am playing around with the RPM spec file for
> ooRexx. I have added some new macros to the file that create additional
> information in the name of the
>>> On 9/17/2010 at 02:36 PM, in message
, Mark Miesfeld
wrote:
> This bug report gives details on the problem I think David is referring to:
>
> https://sourceforge.net/tracker/?func=detail&aid=2991134&group_id=119701&atid=6
>
> 84730
>
> 4.0.1 rev. 5804, 5766 don't build with gcc 4.5-5.2
>>> On 9/17/2010 at 10:52 AM, in message <4c93728e.8040...@gmail.com>, David
Ashley
wrote:
> On zLinux the error happens during the creation of rexximage on SLES 11. We
> could not get past that error and the error messages were no help at all.
> That
> is why we reverted to SLES 10. The
>>> On 9/16/2010 at 04:16 PM, in message <4c926d19.3050...@gmail.com>, David
>>> Ashley
wrote:
> BTW, this machine is running Suse 10. We first tried Suse 11 but found that
> the
> gcc compiler on that version has a problem with our source code.
> Subsequently we
> found that ALL Suse 11
>>> On 9/16/2010 at 12:59 PM, in message <4c923ec9.7060...@gmail.com>, David
>>> Ashley
wrote:
> All -
>
> I have been looking at making some changes to the RPM spec file and I am now
> having second/third thought about one issue in the current spec file.
>
I've had to have those thought
>>> On 8/21/2010 at 07:19 PM, in message <4c7050fc.3060...@wu-wien.ac.at>,
>>> "Rony G.
Flatscher" wrote:
> P.S.: On 64-Bit-Ubuntu there is an issue with 64-bit-Java loading the
> 64-bit-so; have to look into it. Using 64-bit-Java from 64-bit ooRexx is o.k.
>
> and one can even successfull
>>> On 8/20/2010 at 01:26 PM, in message <4c6eaca2.7070...@wu-wien.ac.at>,
>>> "Rony G.
Flatscher" wrote:
> Am still trying to finalize the installation/uninstallation scripts with
> desktop integration, to achieve a single double-click install and an
> uninstall via menus (just learned all
>>> On 8/20/2010 at 12:01 PM, in message <4c6e98b0.6090...@gmail.com>, David
Ashley
wrote:
> I am not really sure you can at install time. This version information is
> maintained by hand. I modify them as necessary manually in the old rpm spec
> file
> (about lines 59-65). I am probably
>>> On 8/19/2010 at 05:24 PM, in message <4c6d92f1.6090...@wu-wien.ac.at>,
>>> "Rony G.
Flatscher" wrote:
> Thank you all very much for your kind help!
>
> Just stumbled over "xdg-open" which is available on the newer Linux
> systems (part of the xdg-utils).
>
> ---rony
>
By the way,
>>> On 8/11/2010 at 04:12 PM, in message
>>> <4c62a1a6022400055...@novprvlin0050.provo.novell.com>, "Erico Mendonca"
>>> wrote:
BUT, I'm getting error on TEST_006 on SLES 11SP1 if I try to use the same build
as SLES 11:
Okay, apparentl
>>> Mark Miesfeld 11/08/10 10:41 >>>
On Wed, Aug 11, 2010 at 6:02 AM, Erico Mendonca wrote:
> To get the 4.0.1 release test suit:
All right, my builds appear to be fine (executed with "./testOORexx.rex -X
native_API" as per README file).
This is
>>> Mark Miesfeld 11/08/10 10:41 >>>
On Wed, Aug 11, 2010 at 6:02 AM, Erico Mendonca wrote:
> To get the 4.0.1 release test suit:
> svn co https://oorexx.svn.sourceforge.net/svnroot/oorexx/test/branches/4.0.1
Thanks!
> Where should we check it out?
Argh sorr
>>> David Ashley 11/08/10 10:31 >>>
We need to test it on a Red Hat/Fedora system before we replace the
existing spec file.
BTW, there is a problem with the current spec file in that it putsall
the shared object files (*.so) in the wrong place when thesystem is ru
Hi there...
I wrote a new, more simplified SPEC file for RPM-based linuxes. It uses some
more RPM best practices, and fixes a few problems I was having with it's
installation under SLES/SLED.
As to why I made it, I found a few inconsistencies with the official package,
namely:
- the rxapid scr
68 matches
Mail list logo
