Re: [gentoo-alt] Re: Prefix/Cygwin: zlib, GCC, which version?

[Al]

> IIRC, the reason to stick with gcc-4.2 during bootstrap is that it is the
> last one not needing extra dependencies (mpfr, gmp) being merged before,
> to keep bootstrap process as simple as possible.

Thank you Michael. Also 4.2*  needs mpfr and gmp on Cygwin, but I can
use the Cygwin package for this in the initial circle. So 4.2* is not
a must and a can go with a younger version. 4.3* didn't build either.

>
>> To note that gcc-4.2.4-r01.2 also doesn't work.
>>
>> /home/prefix/gentoo/var/tmp/portage/sys-devel/gcc-4.2.4-r01.2/work/gcc-4.2.4/libiberty/strsignal.c:409:
>> error: conflicting types for 'strsignal'
>> /usr/include/string.h:79: error: previous declaration of 'strsignal' was here
>
> Seems like a cygwin specific issue, needing a cygwin specific fix in gcc then.
>

So I searched and found that they did something cygwin specific in
libc/include/string.h.

http://sourceware.org/ml/newlib/2008/msg00342.html

-const char  *_EXFUN(strsignal, (int __signo));
+char  *_EXFUN(strsignal, (int __signo));

However I am surprised that ggc-4.2 breaks from this, while ggc-4.4
builds. From this thread I should expect that gcc-4.4 is the breaking
one:

http://old.nabble.com/GCC-4.4---Cygwin-build-failed-in-%27strsignal%27-td19666377.html

Bottomline from both answers is to try to go with gcc-4.4 I think and
to fokus on the SHAREDLIB issue.

>> Is that right, that it using /usr/include/string.h from Cygwins glibc?
>
> Yes, although gcc may make a copy of system headers to fix known issues
> here and there, but I doubt this is done before building gcc itself.
>

I meanwhile found an old thread on this, that tells nobody managed to
emerge glibc on prefix yet.

Al

-- 
Caution crosser:  Runnig Gentoo/Prefix on Cygwin/Vista.
All stupid questions are related to that context.