Re: [Oorexx-devel] ooRexx AIX
hello, Rick McGuire wrote: > You're not getting the point. It looks that way :-)) > There should be NOTHING added to the > build process with respect to restricting/warning/etc. for AIX and gcc > (or other platform, for that matter). It's ok to document this in the > readme that there are issues, but the buid process itself should not > have any specific code that would otherwise discourage an interested > party in pursuing getting this to work. > > Which gcc/g++ version do you use on Linux ?? OK, then we could add something like this to the unix-like-build.txt. Sample... AIX: --- ... AIX text ... cut for clarity ... WARNING: If you use gcc/g++ on AIX then the resulting binaries are not working as intended. > Rick > > Bye Rainer > On Mon, Jan 26, 2009 at 8:43 AM, Rainer Tammer wrote: > >> Hello, >> >> this is regarding your updates of patch *2491990*: >> >> >> >>> 1.) I applied the part of the patch that changes the Makefile to not >>> install rxapid on AIX because you said it won't work on AIX. There must be >>> some way to have rxapi run as a daemon, or a service, on AIX, isn't >>> >> there? >> >>> Will your AIX package set that up? >>> >> Yes, >> the daemon can be started via /etc/inittab - see unix readme. >> If ooRexx 4.0.0 is out I might add the necessary entry via the AIX LPP >> install package. >> If I find the time I could also provide an AIX version of rxapid. I >> tried to put rxapi under >> the control of the subsystem resource controller (SRC) in AIX but >> unfortunately this >> did not work out >> >>> 2.) I didn't apply the second part of your patch concerning g++. I'm not >>> an expert on the config system, but it looks to me like that part of your >>> patch turns off g++ on AIX >>> >> yes >> >>> in addition to issuing a warning. Rick was >>> opposed to this and after some second thought I am too. If the binaries >>> don't work, then so be it. >>> >>> >> The binaries build but the resulting executables do not work as supposed. >> Basically the build is broken. Neither gcc 3.x not 4.2 do produce working >> executable on AIX. >> >>> I think Rick's feeling was that if someone tries to build with g++ on AIX, >>> they will discover soon enough that the binaries don't work. Maybe they >>> will have the skill to come up with a fix for that and turning off g++ may >>> just discourage their trying to fix it. >>> >> OK, >> so I could change this to a warning message that the binaries do not wok >> and >> just go on with the build ? >> >>> Wouldn't it be better to submit a patch to the unix-like-build.txt file >>> updating the AIX portion wil some text saying that using g++ on AIX does >>> not seem to work and we would appreciate any help in determining why? >>> >>> >> I can do this - no problem. >> >>> Anyhow, I would rather see the update unix-like-build.txt route at this >>> point. If you think I didn't interpret the effect of the patch correctly >>> (which I might not of) please submit a patch with just that change and >>> bring it up for discussion on the devel group. >>> >>> >> OK >> >>> I know Rick monitors all these tracker updates just like I do. But, it is >>> just easier to discuss these types of things through an e-mail interface >>> rather than the tracker interface. I for one need a spell checker. >>> >>> >> OK, >> I switch to that tracker because Rick told me so a while ago :-)) ... >> >>> Thanks again for all your work on AIX. >>> >> No problem. >> >> Bye >> Rainer >> >> -- >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > -- > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx AIX
You're not getting the point. There should be NOTHING added to the build process with respect to restricting/warning/etc. for AIX and gcc (or other platform, for that matter). It's ok to document this in the readme that there are issues, but the buid process itself should not have any specific code that would otherwise discourage an interested party in pursuing getting this to work. Rick On Mon, Jan 26, 2009 at 8:43 AM, Rainer Tammer wrote: > Hello, > > this is regarding your updates of patch *2491990*: > > >> 1.) I applied the part of the patch that changes the Makefile to not >> install rxapid on AIX because you said it won't work on AIX. There must be >> some way to have rxapi run as a daemon, or a service, on AIX, isn't > there? >> Will your AIX package set that up? > > Yes, > the daemon can be started via /etc/inittab - see unix readme. > If ooRexx 4.0.0 is out I might add the necessary entry via the AIX LPP > install package. > If I find the time I could also provide an AIX version of rxapid. I > tried to put rxapi under > the control of the subsystem resource controller (SRC) in AIX but > unfortunately this > did not work out >> 2.) I didn't apply the second part of your patch concerning g++. I'm not >> an expert on the config system, but it looks to me like that part of your >> patch turns off g++ on AIX > yes >> in addition to issuing a warning. Rick was >> opposed to this and after some second thought I am too. If the binaries >> don't work, then so be it. >> > The binaries build but the resulting executables do not work as supposed. > Basically the build is broken. Neither gcc 3.x not 4.2 do produce working > executable on AIX. >> I think Rick's feeling was that if someone tries to build with g++ on AIX, >> they will discover soon enough that the binaries don't work. Maybe they >> will have the skill to come up with a fix for that and turning off g++ may >> just discourage their trying to fix it. > OK, > so I could change this to a warning message that the binaries do not wok > and > just go on with the build ? >> >> Wouldn't it be better to submit a patch to the unix-like-build.txt file >> updating the AIX portion wil some text saying that using g++ on AIX does >> not seem to work and we would appreciate any help in determining why? >> > I can do this - no problem. >> Anyhow, I would rather see the update unix-like-build.txt route at this >> point. If you think I didn't interpret the effect of the patch correctly >> (which I might not of) please submit a patch with just that change and >> bring it up for discussion on the devel group. >> > OK >> I know Rick monitors all these tracker updates just like I do. But, it is >> just easier to discuss these types of things through an e-mail interface >> rather than the tracker interface. I for one need a spell checker. >> > OK, > I switch to that tracker because Rick told me so a while ago :-)) ... >> Thanks again for all your work on AIX. > No problem. > > Bye > Rainer > > -- > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] ooRexx AIX
Hello, this is regarding your updates of patch *2491990*: > 1.) I applied the part of the patch that changes the Makefile to not > install rxapid on AIX because you said it won't work on AIX. There must be > some way to have rxapi run as a daemon, or a service, on AIX, isn't there? > Will your AIX package set that up? Yes, the daemon can be started via /etc/inittab - see unix readme. If ooRexx 4.0.0 is out I might add the necessary entry via the AIX LPP install package. If I find the time I could also provide an AIX version of rxapid. I tried to put rxapi under the control of the subsystem resource controller (SRC) in AIX but unfortunately this did not work out > 2.) I didn't apply the second part of your patch concerning g++. I'm not > an expert on the config system, but it looks to me like that part of your > patch turns off g++ on AIX yes > in addition to issuing a warning. Rick was > opposed to this and after some second thought I am too. If the binaries > don't work, then so be it. > The binaries build but the resulting executables do not work as supposed. Basically the build is broken. Neither gcc 3.x not 4.2 do produce working executable on AIX. > I think Rick's feeling was that if someone tries to build with g++ on AIX, > they will discover soon enough that the binaries don't work. Maybe they > will have the skill to come up with a fix for that and turning off g++ may > just discourage their trying to fix it. OK, so I could change this to a warning message that the binaries do not wok and just go on with the build ? > > Wouldn't it be better to submit a patch to the unix-like-build.txt file > updating the AIX portion wil some text saying that using g++ on AIX does > not seem to work and we would appreciate any help in determining why? > I can do this - no problem. > Anyhow, I would rather see the update unix-like-build.txt route at this > point. If you think I didn't interpret the effect of the patch correctly > (which I might not of) please submit a patch with just that change and > bring it up for discussion on the devel group. > OK > I know Rick monitors all these tracker updates just like I do. But, it is > just easier to discuss these types of things through an e-mail interface > rather than the tracker interface. I for one need a spell checker. > OK, I switch to that tracker because Rick told me so a while ago :-)) ... > Thanks again for all your work on AIX. No problem. Bye Rainer -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Runtime-infos about caller ? (Re: Question about calling an external routine
Hi Robert, rob...@garrettfamily.us wrote: > Thanks for the push in the right direction, I actually have it working > now. Great! > > One more quick question just because I'm being lazy at the moment: in > LOGGER, is there a function/method I can call that will tell me 1) > that it is being invoked from a 'parent' calling routine (as opposed > to being started from a command prompt) and 2) what the name of that > parent routine is? In 3.x this seems to not be possible. Not sure about 4.x which introduces a context object that may allow for that (also not sure whether it would be possible to get at the call stack and the respective context objects). Probably only Rick may be able to answer this. ---rony P.S.: Because of your new question I changed the subject line. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
