This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/52513] gcc-4.7.0-RC-20120302 fails to build for i686-pc-cygwin


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52513

--- Comment #2 from Ryan Johnson <scovich at gmail dot com> 2012-03-07 13:02:50 UTC ---
(In reply to comment #1)
> 4.6 should be broken as well for you?
Oops. I reported wrong in my OP. I've actually been using a home-built 4.6.2
for some time now... and it is the host compiler for this build:

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/home/Ryan/apps/gcc-4.6.2/libexec/gcc/i686-pc-cygwin/4.6.2/lto-wrapper.exe
Target: i686-pc-cygwin
Configured with: ../gcc-4.6.2-src/configure --prefix=/home/Ryan/apps/gcc-4.6.2
Thread model: single
gcc version 4.6.2 (GCC)


> 
> Can you check why configure thinks spawnve is available in process.h
> (contrary to the warning we see in your snippet)?
Sorry, I may not have been clear on this. Google reported that spawnve lives in
process.h. A quick search on my filesystem shows that spawnve actually lives in
<cygwin/process.h>, not <process.h> as expected by pex-unix.c. Configure
probably only tested linker status for the function and therefore wouldn't have
noticed. 

Perhaps the file moved recently (since 1.7.9 or 10)? I've sent mail to the
cygwin list to see if anybody there knows. Meanwhile, soft-linking process.h to
where gcc expects it lets the compile continue. I'll report back if any further
issues arise.

> What Windows version are you using?
W7-x64


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]