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... yes checking whether posix_spawnp is declared without a macro... yes The full m4 configure output and the generated logfile are online at http://mud.stack.nl/~johans/m4/configure.txt http://mud.stack.nl/~johans/m4/config.log > It may be possible to work around the failure, by priming the configure > cache. For example, if the bug is that your posix_spawnp is broken, but > gnulib is not properly detecting that brokenness, then you could use > './configure ac_cv_func_posix_spawnp=no' to force the gnulib replacement > to be compiled in. I tried this, but it still results in the same errors, ../src/m4: esyscmd subprocess failed: Operation not permitted Thanks for looking in to this, Johan
pgp8Bi4yKk7QO.pgp
Description: PGP signature
