Re: MinGW and "warning: implicit declaration of function _spawnv"

2017-11-14 Thread Bob Friesenhahn
On Tue, 14 Nov 2017, Jeffrey Walton wrote: What does spawnv have to do with _XOPEN_SOURCE? Isn't spawnv a Microsoft Windows-specific function and _XOPEN_SOURCE is a Unix thing? I think spawn is Posix, and its for systems that don't have fork. posix_spawn and _spawn are deprecated on MS platfo

Re: MinGW and "warning: implicit declaration of function _spawnv"

2017-11-14 Thread Jeffrey Walton
On Tue, Nov 14, 2017 at 4:00 PM, Bob Friesenhahn wrote: >>> Or maybe something else? >> >> It looks like the extra files provided by libtool are the problem. It >> looks like the libtool folks need to add _XOPEN_SOURCE=600 to their >> preprocessor definitions. I'm guessing they only test with a C

Re: MinGW and "warning: implicit declaration of function _spawnv"

2017-11-14 Thread Bob Friesenhahn
Or maybe something else? It looks like the extra files provided by libtool are the problem. It looks like the libtool folks need to add _XOPEN_SOURCE=600 to their preprocessor definitions. I'm guessing they only test with a C compiler, and not a C++ compiler and Newlib combination. What does s

Re: MinGW and "warning: implicit declaration of function _spawnv"

2017-11-14 Thread Jeffrey Walton
On Tue, Nov 7, 2017 at 6:10 PM, Jeffrey Walton wrote: > I'm testing on MinGW (). I'm surprised how easily the library built > for MinGW under Autotools. Hat's off for the good job. > > I'm down to one error from what appears to be an Automake source file > (see below). I'm not a MinGW expert and s

MinGW and "warning: implicit declaration of function _spawnv"

2017-11-07 Thread Jeffrey Walton
I'm testing on MinGW (). I'm surprised how easily the library built for MinGW under Autotools. Hat's off for the good job. I'm down to one error from what appears to be an Automake source file (see below). I'm not a MinGW expert and searching is not returning useful results. I test the platform to