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/loca
Eric Blake wrote:
> 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.
Sure, it's now up on http://mud.stack.nl/~johans/193-
Eric Blake wrote:
> According to Johan van Selst on 3/1/2010 11:02 AM:
> > Sure, it's now up on http://mud.stack.nl/~johans/193-ktrace.txt
> > (output from the test in checks/193.esyscmd)
> Actually, it looks like you posted the trace for 007.command_li
Oops, I was rath
Eric Blake wrote:
> Johan, can you find the portion in config.log that shows whether the
> native posix_spawn was deemed acceptable or buggy?
It looks acceptable:
checking for posix_spawn... yes
checking whether posix_spawn works... yes
checking whether posix_spawn is declared without a macro.
Johan van Selst wrote:
> Eric Blake wrote:
> > 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.
>
Hi Bruno,
Bruno Haible wrote:
> FreeBSD's POSIX_SPAWN_SETSIGMASK is 0x20, FreeBSD's POSIX_SPAWN_SETSCHEDULER
> is 0x08. Whereas the gnulib replacement value for POSIX_SPAWN_SETSIGMASK is
> 0x08. It seems gnulib's replacement value is in use when it should not. I'm
> applying this fix.
Thanks for
