Building GCC 4.3.0 on Cygwin...
Tim Prince
n8tm@aol.com
Sat Mar 24 01:33:00 GMT 2007
brian@dessent.net wrote:
> Angelo Graziosi wrote:
>
>> As I wrote:
>>
>>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31039
>
> Ah, okay. I failed to see that you'd posted the config.log there. (And
> I mentioned gmp/mpfr as I have seen that cause the build to fail in
> exactly the way you described, but it's clearly not the case here.)
>
> The real problem seems to be that the libgcc is broken:
>
> configure:2121: /home/User/cvsroot/gcc-obj/./prev-gcc/xgcc
> -B/home/User/cvsroot/gcc-obj/./prev-gcc/
> -B/usr/local/i686-pc-cygwin/bin/
> conftest.c >&5
> /home/User/cvsroot/gcc-obj/./prev-gcc/libgcc.a(_ctors.o): In function
> `__sgetc_r':
> /usr/include/stdio.h:414: undefined reference to `_ungetc'
> /usr/include/stdio.h:410: undefined reference to `___srget_r'
> /usr/include/stdio.h:407: undefined reference to `___srget_r'
> collect2: ld returned 1 exit status
>
> It looks like a problem with some function being defined as a macro when
> it shouldn't, or vice versa. You'll need to look into how _ctors.o is
> built to see exactly, since I can't find any reference to _sgetc_r or
> ungetc in any of the libgcc2.{c,h} files. You can try the trick of
> going into the libgcc build directory (you may have to "make restage1"
> to back up one stage), "rm _ctors.o" and then "make CFLAGS="-g -O2
> -save-temps"" (or some variant) and then look at the preprocessed source
> to see what's happening.
>
> Brian
>
Just before that, there is a reported failure of the bootstrap compiler,
due to the trailing -V argument supplied in configure. Most of the
configure files in the recent 4.3 snapshots do this. I don't have a
clue what this -V is meant for.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list