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