On Mon, Jun 29, 2009 at 9:04 AM, Rick McGuire<object.r...@gmail.com> wrote:
> Hmmm, the inclusion of that really shouldn't be dependent upon rxapi. > Since you've narrowed down the conditions under which this happens, it > should be possible sort out the reasons why. "Should be possible" doesn't seem to apply to me. <grin> I first noticed this quite a long time ago when I was building on an older version of SuSE, 9.3. Since David and you were building on Fedora and never said anything I thought it was specific to my SuSE. The key, I thought,was that when I had problems, I would always see that the xxx/.libs/lt-rexximage process was still running after the build finished. That process is started of course during the build when rexx.img is created. I tried, unsuccessfully, at the time to debug why lt-rexximage didn't exit normally. During that process I discovered that if a rxapi was running that was at the same level as the build I was trying to do, the lt-rexximage always completed normally. So, I used that as a work around on that SuSE system. Then, when I set up some new Fedora and Debian systems, I didn't notice the problem at first. I set up a new SuSE system, and also didn't notice the problem. So, I chalked it up to something in the older SuSE's CRT libraries, or gremlins. However, over time, I did notice that even on my new systems the symptom of lt-rexximage not completing does happen. So, that is as far as I got in sorting out the reasons why. -- Mark Miesfeld ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
