[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [lmi] fork failed: no error [464]

From: Boutin, Wendy
Subject: RE: [lmi] fork failed: no error [464]
Date: Fri, 26 May 2006 12:28:36 -0400

Wendy Boutin wrote:
> Greg Chicares wrote:
> > 
> > Using an ancient native msw port of ash for portability testing
> > (it's the closest thing I've found to the original bourne shell),
> > I ran into this problem. It occurs only when invoking 'wx-config'
> > this way:
> >   wx_config_libs     := $(shell $(wx_config_script) --libs)
> > but not this way:
> >   wx_config_libs     := $(shell sh -c "$(wx_config_script) --libs")
> That change causes us to not compile skeleton. 

Now, I think that's only the case if Mikey's ash doesn't exist in 
'c:/bin'. I found an old version of (what I think is) Mikey's ash here:
and put a copy in 'c:/bin/'. After I downloaded skeleton's current
cvs HEAD, I was able to successfully compile it as expected.

I was never able to reproduce Greg's original problem that provoked
workhorse.make revision 1.24, but there should no longer be any 
problems upgrading wx as long as a copy of Mikey's ash exists in 

This e-mail transmission may contain information that is proprietary, 
privileged and/or confidential and is intended exclusively for the person(s) to 
whom it is addressed. Any use, copying, retention or disclosure by any person 
other than the intended recipient or the intended recipient's designees is 
strictly prohibited. If you are not the intended recipient or their designee, 
please notify the sender immediately by return e-mail and delete all copies. 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]