According to Johan van Selst on 2/28/2010 3:12 PM: > Greetings, > > I tested the latest m4 on FreeBSD and found that with this installed, I > cannot compile Apache or PHP programs anymore. The problem seems to be > with esyscmd changes in the latest release (1.4.13 works fine). > The typical error message looks something like this (from Apache 2): > > /usr/local/bin/gm4: esyscmd subprocess failed: Invalid argument > /usr/local/bin/gm4:configure.in:398: cannot run command > `./build/config-stubs .': Invalid argument
Thanks for the report. Can you run the equivalent of strace to see what is being attempted when exec'ing the child process? Or maybe this is the case of a spurious errno value being left over from some earlier syscall. I'll try and get on a FreeBSD machine and see if I can reproduce this. But my initial pre-release testing on BSD did not fail, so I will have to figure out what is different between my environment and yours. > --- m4-tmp.22799/m4-xerr 2010-02-28 23:00:26.000000000 +0100 > +++ m4-tmp.22799/m4-err 2010-02-28 23:00:26.000000000 +0100 > @@ -0,0 +1,2 @@ > +m4: syscmd subprocess failed: Invalid argument > +m4:stdin:5: cannot run command `POSIXLY_CORRECT=1 'm4' -Dbar=hello foo > -Dbar=world foo': Invalid argument -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net
signature.asc
Description: OpenPGP digital signature
