I have tried emerging wine-20030408 and wine-20030411 with glibc-2.3.2-r1/gcc-3.2.2-r2 and it fails every time when compiling glu32 stuff, which a huge number of "undefined reference to ..." errors. I know there are currently bugs for problems with glibc-2.3.2 and binutils. I don't think this is related, for the following reasons: 1. These versions of wine are supposed to be compatible with "all 2.3 variants of glibc." 2. I have tried building wine with the following versions of binutils, all with the same results: 2.13.90.0.20-r1 2.13.90.0.20 2.13.90.0.18 Reproducible: Always Steps to Reproduce: 1. On a system with glibc-2.3.2-r1, gcc-3.2.2-r1 and xfree-4.3.0-r1, do 'emerge wine' Actual Results: It fails as described above. Expected Results: Wine should have been successfully compiled.
Created attachment 10601 [details] Stack trace starting with compilation of glu32
Created attachment 10608 [details] config.log for wine configuration during merge.
Forgot to add my USE and CFLAGS.. here they are: USE="X gtk2 xft2 freetype smooth dvd apache2 imap -kde -qt -qtmt -arts -cups" CFLAGS="-march=athlon -O3 -pipe" I am running "~x86" (obviously).
My bad.. sorry. After remerging gcc and xfree, wine now compiles fine. I can't seem to resolve this bug though - is that the intended behaviour? Why can't bug reporters resolve their own bugs?
closing