Re: m4 1.4.14 esyscmd problems on FreeBSD

2010-03-02 Thread Johan van Selst
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

Re: m4 1.4.14 esyscmd problems on FreeBSD

2010-03-02 Thread Johan van Selst
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. >

Re: m4 1.4.14 esyscmd problems on FreeBSD

2010-03-01 Thread Johan van Selst
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.