At 10:19 AM 3/29/2004, you wrote: >Larry Hall wrote:
<snip> >> >>>Got a SIGCHLD; 1 unreaped children. >>>Reaping winning child 0x108b3a20 PID 1288 >>>Removing child 0x108b3a20 PID 1288 from chain. >>> Successfully remade target file `some_path/GUI_Module.lib_ar'. >>>Finished prerequisites of target file `some_path/GUI_Module.lib'. >>>Must remake target `some_path/GUI_Module.lib'. >>>/cygdrive/c/tmp/tornado2_1/host/i686-pc-cygwin/bin/arsh -M < >> >> >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> >> Yikes! You're still mixing tool-sets. That ain't gonna work! >> >> >> -- >> Larry Hall http://www.rfk.com >> RFK Partners, Inc. (508) 893-9779 - RFK Office >> 838 Washington Street (508) 893-9889 - FAX >> Holliston, MA 01746 >> >> > >The referenced arsh binary was compiled locally for the currently >installed cygwin (cygwin version at compile time was 1.5.6) from the >windriver-provided sources to work around some problems with the >original tornado-binaries. > >The path to AR is set inside the Makefile like this >AR=/path/to/arsh > >Calling this specific arsh from the bash does work, whatever the cygwin >version, so I see no problem with calling it from within make, or am I >completely wrong here ?? That sounds OK. Assuming that this is the only binary pulled in from the tornado distribution, it's not obvious that this would cause a problem. I'm out of ideas at the moment, beyond the obvious debugging. -- Larry -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
