This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/52513] gcc-4.7.0-RC-20120302 fails to build for i686-pc-cygwin
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 07 Mar 2012 09:44:34 +0000
- Subject: [Bug bootstrap/52513] gcc-4.7.0-RC-20120302 fails to build for i686-pc-cygwin
- Auto-submitted: auto-generated
- References: <bug-52513-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52513
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |i686-pc-cygwin
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2012-03-07
CC| |davek at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org,
| |rth at gcc dot gnu.org
Host| |i686-pc-cygwin
Ever Confirmed|0 |1
Build| |i686-pc-cygwin
--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-07 09:44:34 UTC ---
Probably caused by
2010-11-04 Richard Henderson <rth@redhat.com>
* configure.ac (AC_CHECK_HEADERS): Add process.h.
(checkfuncs): Add dup3, spawnve, spawnvpe; sort the list.
(AC_CHECK_FUNCS): Add dup3, spawnve, spawnvpe.
* configure, config.in: Rebuild.
* pex-unix.c [HAVE_SPAWNVE] (pex_unix_exec_child): New function.
[HAVE_SPAWNVE] (save_and_install_fd, restore_fd): New functions.
thus 4.6 should be broken as well for you?
Can you check why configure thinks spawnve is available in process.h
(contrary to the warning we see in your snippet)?
What Windows version are you using?