Gentoo Archives: gentoo-dev

From: "Webmaster Refstart.NL" <webmaster@××××××××.nl>
To: gentoo-dev@g.o
Subject: Re: [gentoo-dev] default-1.0-gcc3 success
Date: Wed, 29 May 2002 02:38:24
Message-Id: 20020529093619.48730391.webmaster@refstart.nl
In Reply to: Re: [gentoo-dev] default-1.0-gcc3 success by Lars Pechan
1 Hi Lars and others,
2
3 Thanks a lot for your help, the glibc problem is solved now! :) The problem was that I had emerged GCC 3.1 before I started bootstrapping the system, that's why glibc won't compile. Now I've removed the whole Gentoo partition and started over installing. I've linked /etc/make.profile to /usr/portage/profiles/default-1.0-gcc3 and edited the packages file so that binutils 2.12 is choosen instead of 2.11. The bootstrap process is now ready and I have edited the compile flags in /etc/make.conf to match my CPU. I'll try to emerge the system now :)
4
5 Thanks again for your help,
6
7 Niek.
8
9 On Wed, 29 May 2002 18:17:06 +1200
10 Lars Pechan <lars.pechan@××××××××××××.nz> wrote:
11
12 > Sorry for not getting back on this yesterday.
13 >
14 > As you may have seen wading through the archives I've been through the same
15 > problems as you but it only happened when I tried to bootstrap using gcc-3.1.
16 > I used two different methods to build the gcc to bootstrap with: either
17 > bootstrapping twice or emerging gcc-3.1 as the very first thing after having
18 > installed the tarball iff the Gentoo CD.
19 >
20 > In both cases I got to the same stage as you, i.e. glibc would not build due
21 > to the error you've seen.
22 >
23 > Spider then reported he'd successfully boostrapped straight from the tarball
24 > and I and I believe others have done that as well without any problems at all
25 > (at that stage anyway). Doing it this way means glibc doesn't get built with
26 > various optimizations but it's probably not a very good idea to do so anyway.
27 >
28 > I've built xfree86-4.2.0r9 since without any problems. Maybe different use
29 > flags is causing this to fail for some and succeed for others?
30 >
31 > My use flags are:
32 >
33 > USE="alsa directfb dvd 3dnow lm_sensors -gnome spell imap xml doc"
34 >
35 > I'm having problems with the nvidia driver but s/w open-gl seems ok. I haven't
36 > researched this fully but I believe the nvidia issue may well be due to the
37 > difference in abi between gcc-3.1 compiled system libraries and nvidia's
38 > binaries (that have been compiled with something else - 2.95 most likely).
39 > I'm hoping I'm wrong though cause otherwise we have to wait for nvidia to
40 > release gcc3 compiled drivers. Anyone having had more luck?
41 >
42 > kdebase and kdelibs have built fine but I had to do something very ugly to get
43 > fam-oss to compile (I'm in contact with the maintainer about this one).
44 > Anyone else having had any problems with this? I can't get as far as kdevelop
45 > since lynx won't compile but I have a theory that's because of the
46 > ncurses-issues.
47 >
48 > What else... ah, just tried emerge kde which tries to compile xanim (probably
49 > due to my use-flags, I think) which fails miserably. Might look into it later
50 > if I get a chance.
51 >
52 > Would be good if other early adopters could post their experiences too.
53 >
54 > Finally, I changed my compiler flags to
55 >
56 > C[XX]FLAGS=-march=athlon-xp -O3 -mmmx -m3dnow -pipe
57 >
58 > immediately after the bootstrap was done so the emerge system was done with
59 > them rather than the std -march=i686 -O3 -pipe.
60 >
61 > HTH,
62 >
63 > /Lasse
64 >
65 > On Wed, 29 May 2002 17:43, Webmaster Refstart.NL wrote:
66 > > This is very cool, are you using binutils 2.12 (combreloc tweak) or the
67 > > default 2.11? I'm trying to bootstrap my system with GCC 3.1 and binutils
68 > > 2.12, but I get this error while compiling glibc:
69 > >
70 > > gawk: scripts/versions.awk:68: (FILENAME=- FNR=3) fatal: printf to "sort -n
71 > > > /v ar/tmp/portage/glibc-2.2.5-r2/work/glibc-2.2.5/buildhere/Versions.tmp"
72 > > failed (B roken pipe)
73 > > sed: couldn't write 69 items to {standard output}: Broken pipe
74 > > stdout: Broken pipe
75 > > make[1]: ***
76 > > [/var/tmp/portage/glibc-2.2.5-r2/work/glibc-2.2.5/buildhere/sysd-ve rsions]
77 > > Error 2
78 > > make[1]: Leaving directory
79 > > '/var/tmp/portage/glibc-2.2.5-r2/work/glibc-2.2.5' make: *** [all] Error 2
80 > >
81 > > !!! ERROR: The ebuild did not complete succesfully.
82 > > !!! Function src_compile, Line 14, Exitcode 2
83 > > !!! (no error message)
84 > >
85 > > !!! emerge aborting on /usr/portage/sys-libs/glibc/glibc-2.2.5-r2.ebuild .
86 > >
87 > > How can I solve this? Should I bootstrap my system with GCC 2.95 and then
88 > > install GCC 3.1?
89 > >
90 > > Bye, Niek.
91 > >
92 > >
93 > > On Wed, 29 May 2002 14:24:18 +0000
94 > >
95 > > Jack Morgan <yojack@××××××××××××.jp> wrote:
96 > > > I did a fresh install after borking an upgrade atempt. I was able to
97 > > > get gcc3.1 to bootstrap. I installed from cdrom, BTW. Here is a short
98 > > > summary:
99 > > >
100 > > > 1) Bootstrap phase
101 > > > Perl wouldn't compile. I had to unmask it, eg comment it out, in
102 > > > package.mask. Then it compiled. Version perl5.6.1-r4, I think.
103 > > > My USE variables were set to the default or USE="" and my compiler
104 > > > was set to -march=i686 -O6
105 > > >
106 > > > 2) Emerge system
107 > > > Everything compiled fine here. Once the system was installed, I added
108 > > > many USE variables and changed my compiler to -march=athlon -O6. All
109 > > > packages installed after this worked fine using athlon optimization.
110 > > > At this point, I wanted to do, emrege -e world but was afraid ;-)
111 > > >
112 > > > 3) Xfree-4.2.0-r9
113 > > > Wouldn't compile. I unmasked this in package.mask and I'm currently
114 > > > compiling xfree-4.2.0-r11. I'll let you know how it goes.
115 > > >
116 > > > Anyway, thanks to all devlopers working on getting gcc-3.1 working.
117 > > >
118 > > > --
119 > > > jack_morgan
120 > > >
121 > > > _______________________________________________
122 > > > gentoo-dev mailing list
123 > > > gentoo-dev@g.o
124 > > > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
125 > >
126 > > _______________________________________________
127 > > gentoo-dev mailing list
128 > > gentoo-dev@g.o
129 > > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
130 >
131 > _______________________________________________
132 > gentoo-dev mailing list
133 > gentoo-dev@g.o
134 > http://lists.gentoo.org/mailman/listinfo/gentoo-dev