Gentoo Archives: gentoo-alpha

From: Marc Giger <gigerstyle@×××.ch>
To: gentoo-alpha@l.g.o
Cc: kloeri@g.o
Subject: Re: [gentoo-alpha] problem upgrading the toolchain
Date: Wed, 07 Dec 2005 18:15:15
Message-Id: 20051207191508.6130edd7@vaio.gigerstyle.ch
In Reply to: Re: [gentoo-alpha] problem upgrading the toolchain by Marc Giger
1 I "straced" emerge, perhaps it helps.
2 That's what I got on the shell:
3
4 witch ~ # strace -fF -s1000 -o emerge-trace.txt emerge -b gcc-config
5 umovestr: Input/output error
6 sh: 10: No such file or directory
7 Calculating dependencies ...done!
8 >>> emerge (1 of 1) sys-devel/gcc-config-1.3.12-r4 to /
9 umovestr: Input/output error
10 PANIC: attached pid 6291 exited
11 umovestr: Input/output error
12 /usr/lib/portage/bin/ebuild.sh: line 56: 11: No such file or directory
13 ptrace: umoven: Input/output error
14 umovestr: Input/output error
15 >>> md5 files ;-) gcc-config-2.0.0_beta2.ebuild
16 >>> md5 files ;-) gcc-config-1.3.12-r4.ebuild
17 >>> md5 files ;-) files/gcc-config-1.3.12
18 >>> md5 files ;-) files/wrapper-1.4.7.c
19 >>> md5 files ;-) files/digest-gcc-config-2.0.0_beta2
20 >>> md5 files ;-) files/digest-gcc-config-1.3.12-r4
21 umovestr: Input/output error
22 PANIC: attached pid 6315 exited
23 umovestr: Input/output error
24 /usr/lib/portage/bin/ebuild.sh: line 56: 11: No such file or directory
25 ptrace: umoven: Input/output error
26 umovestr: Input/output error
27 umovestr: Input/output error
28 umovestr: Input/output error
29 PANIC: attached pid 6338 exited
30 umovestr: Input/output error
31 ptrace: umoven: Input/output error
32 umovestr: Input/output error
33 umovestr: Input/output error
34 [preattached child 73 of 6369 in weird state!]
35 umovestr: Input/output error
36 PANIC: attached pid 6369 exited
37 umovestr: Input/output error
38 ptrace: umoven: Input/output error
39 umovestr: Input/output error
40 alpha-unknown-linux-gnu-gcc: Internal error: Segmentation fault (program
41 as) Please submit a full bug report.
42 See <URL:http://bugs.gentoo.org/> for instructions.
43
44 !!! ERROR: sys-devel/gcc-config-1.3.12-r4 failed.
45 !!! Function src_compile, Line 25, Exitcode 1
46 !!! compile wrapper
47 !!! If you need support, post the topmost build error, NOT this status
48 message.
49
50 The full output of strace is attached.
51
52 Thanks
53
54 Marc
55
56 On Wed, 7 Dec 2005 18:48:02 +0100
57 Marc Giger <gigerstyle@×××.ch> wrote:
58
59 > Bryan
60 >
61 > Thank you for your time. I will provide as much information
62 > as possible to solve these problems.
63 >
64 > witch ~ # cat /proc/cpuinfo
65 > cpu : Alpha
66 > cpu model : EV56
67 > cpu variation : 7
68 > cpu revision : 0
69 > cpu serial number :
70 > system type : EB164
71 > system variation : LX164
72 > system revision : 0
73 > system serial number :
74 > cycle frequency [Hz] : 533172608 est.
75 > timer frequency [Hz] : 1024.00
76 > page size [bytes] : 8192
77 > phys. address bits : 40
78 > max. addr. space # : 127
79 > BogoMIPS : 1059.80
80 > kernel unaligned acc : 190
81 > (pc=fffffffc00313e20,va=fffffc00243c28ce) user unaligned acc : 0
82 > (pc=0,va=0) platform string : Digital AlphaPC 164LX 533 MHz
83 > cpus detected : 1
84 > L1 Icache : 8K, 1-way, 32b line
85 > L1 Dcache : 8K, 1-way, 32b line
86 > L2 cache : 96K, 3-way, 64b line
87 > L3 cache : 2048K, 1-way, 64b line
88 >
89 > witch ~ # emerge --info
90 > Portage 2.0.51.22-r3 (default-linux/alpha/2005.0, gcc-3.4.4,
91 > glibc-2.3.5-r3, 2.6.12.5 alpha)
92 > =================================================================
93 > System uname: 2.6.12.5 alpha EV56 Gentoo Base System version 1.6.13
94 > ccache version 2.3 [enabled]
95 > dev-lang/python: 2.2.3-r5, 2.3.5-r2, 2.4.2
96 > sys-apps/sandbox: 1.2.12
97 > sys-devel/autoconf: 2.13, 2.59-r6
98 > sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
99 > sys-devel/binutils: 2.15.92.0.2-r10
100 > sys-devel/libtool: 1.5.20
101 > virtual/os-headers: 2.6.11-r2
102 > ACCEPT_KEYWORDS="alpha"
103 > AUTOCLEAN="yes"
104 > CBUILD="alpha-unknown-linux-gnu"
105 > CFLAGS="-mcpu=ev56 -O3 -pipe"
106 > CHOST="alpha-unknown-linux-gnu"
107 > CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
108 > /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf
109 > /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=ev56 -O3 -pipe"
110 > DISTDIR="/usr/portage/distfiles"
111 > FEATURES="autoconfig ccache distlocks sandbox sfperms strict"
112 > GENTOO_MIRRORS="ftp://sunsite.cnlab-switch.ch/mirror/gentoo
113 > http://gentoo.oregonstate.edu
114 > http://www.ibiblio.org/pub/Linux/distributions/gentoo"
115 > PKGDIR="/usr/portage/packages"
116 > PORTAGE_TMPDIR="/var/tmp"
117 > PORTDIR="/usr/portage"
118 > SYNC="rsync://rsync.gentoo.org/gentoo-portage"
119 > USE="alpha acl apache apache2 arts berkdb bitmap-fonts bzip2 crypt
120 > cups eds encode ev56 expat font-server foomaticdb fortran gd gdbm gif
121 > gmp gpm gstreamer gtk2 imlib jikes jpeg libg++ libwww mad mhash mikmod
122 > motif mp3 mpeg mysql ncurses nls no-htdocs nptl ogg oggvorbis opengl
123 > oss pam pcre pdflib perl php png postgres python quicktime readline
124 > sdl slang snmp spell ssl tcpd tiff truetype-fonts type1-fonts vorbis
125 > xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS,
126 > CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY
127 >
128 > As you can see I use gcc-3.4.4. This was a test if it would made
129 > any difference. It did also not work with gcc-3.3.x.
130 > Also I rebuilt portage, python etc (with the new glibc) with no
131 > success.
132 >
133 > Please ask if you need more infos. I've set up a chroot-env to
134 > for testing purposes.
135 >
136 > Thanks
137 >
138 > Marc
139 >
140 >
141 > On Wed, 7 Dec 2005 11:20:49 +0100
142 > Bryan Østergaard <kloeri@g.o> wrote:
143 >
144 > > Please don't file a duplicate bug about this problem as we're well
145 > > aware of the existing bug. The big problem is that we don't seem to
146 > > be able to reproduce the bug as everything seems fine in our testing
147 > > using glibc-2.3.5*.
148 > >
149 > > At least 3 Gentoo developers (myself included) have tried to
150 > > reproduce it without any luck which makes it quite hard to fix.
151 > >
152 > > So what I'd like is a bit more information about the machines this
153 > > problem happens on. Model of the box, glibc version, kernel version
154 > > and patchset and output from emerge --info.
155 > >
156 > > Please add all this info to bug 100259 or send it to this list or me
157 > > directly at kloeri@g.o and I'll see if I can find some
158 > > pattern to this. Hopefully this will give me some much needed clue
159 > > about this problem.
160 > >
161 > > Regards,
162 > > Bryan Østergaard
163 > >
164 > > On Tue, Dec 06, 2005 at 07:39:53PM -0800, Jeff Donsbach wrote:
165 > > > Thanks, Marc,
166 > > >
167 > > > I guess it's a good thing I didn't build with
168 > > > USE="-nptlonly" then, huh? ;-)
169 > > >
170 > > > Should I file a duplicate bug in bugzilla (if it would
171 > > > help)?
172 > > >
173 > > > So, is there some kind of catch 22 going on here?
174 > > > Weren't there some reports of problems with
175 > > > linuxthreads in glibc on Alpha?
176 > > >
177 > > > Jeff D
178 > > >
179 > > > --- Marc Giger <gigerstyle@×××.ch> wrote:
180 > > >
181 > > > > Hi,
182 > > > >
183 > > > > I reported the same problem to bugzilla...
184 > > > > http://bugs.gentoo.org/show_bug.cgi?id=100259#c36
185 > > > > (Perhaps it finds more attention here...)
186 > > > >
187 > > > > It seems it has to do with the current state of ntpl
188 > > > > on
189 > > > > alphas.
190 > > > >
191 > > > > If you set LD_ASSUME_KERNEL=2.4.1 and therefore
192 > > > > force
193 > > > > to use linuxthreads, emerge works again.
194 > > > > But I don't know if it really is nptl's fault. I can
195 > > > > manually
196 > > > > compile everything with the same parameters as
197 > > > > portage does. So a portage (sandbox?) fault is also
198 > > > > possible.
199 > > > >
200 > > > > Marc
201 > > > >
202 > > > >
203 > > > > On Tue, 6 Dec 2005 10:45:57 -0800 (PST)
204 > > > > Jeff Donsbach <jeff_donsbach@×××××.com> wrote:
205 > > > >
206 > > > > >
207 > > > > > Good point, Nils. Perhaps "5" is the configure.log
208 > > > > I
209 > > > > > included? I don't know.I'll try that tonight (the
210 > > > > > Miata is at home).
211 > > > > >
212 > > > > > Jeff D
213 > > > > >
214 > > > > > --- "Nils o. Janus" <NoJ@××××××××××××.de> wrote:
215 > > > > >
216 > > > > > > Hi Jeff,
217 > > > > > >
218 > > > > > > > configure:1892: checking whether the C
219 > > > > compiler
220 > > > > > > > (/usr/bin/gcc -mieee -mcpu=ev56 -pipe -O2 )
221 > > > > works
222 > > > > > > > configure:1908: /usr/bin/gcc -o conftest
223 > > > > -mieee
224 > > > > > > > -mcpu=ev56 -pipe -O2 conftest.c 1>&5
225 > > > > > > ^^^^
226 > > > > > > what perplexes me is that stdout is redirecting
227 > > > > to
228 > > > > > > the filedescriptor 5
229 > > > > > > which is not a standardized one.
230 > > > > > > Does that filedescriptor ( /dev/fd/5 ) exist?
231 > > > > > > This may be the reason why compiling without
232 > > > > > > redirecting the output, like
233 > > > > > > you already tried, works fine.
234 > > > > > >
235 > > > > > > Try passing the 1>&5 to the call of gcc too and
236 > > > > > > check wether it segfaults
237 > > > > > > again.
238 > > > > > >
239 > > > > > > On a DS20e, gcc just throws a "Bad file
240 > > > > descriptor"
241 > > > > > > error without
242 > > > > > > segfaulting.
243 > > > > > >
244 > > > > > > HTH,
245 > > > > > >
246 > > > > > > greetings
247 > > > > > > Nils
248 > > > > > > --
249 > > > > > > gentoo-alpha@g.o mailing list
250 > > > > > >
251 > > > > > >
252 > > > > >
253 > > > > >
254 > > > > >
255 > > > > >
256 > > > > > __________________________________________
257 > > > > > Yahoo! DSL – Something to write home about.
258 > > > > > Just $16.99/mo. or less.
259 > > > > > dsl.yahoo.com
260 > > > > >
261 > > > > > --
262 > > > > > gentoo-alpha@g.o mailing list
263 > > > > >
264 > > > >
265 > > > > --
266 > > > > gentoo-alpha@g.o mailing list
267 > > > >
268 > > > >
269 > > >
270 > > >
271 > > > __________________________________________________
272 > > > Do You Yahoo!?
273 > > > Tired of spam? Yahoo! Mail has the best spam protection around
274 > > > http://mail.yahoo.com
275 > > > --
276 > > > gentoo-alpha@g.o mailing list
277 > > >
278 > > >
279 > > --
280 > > gentoo-alpha@g.o mailing list
281 > >
282 >
283 > --
284 > gentoo-alpha@g.o mailing list
285 >

Attachments

File name MIME type
emerge-trace.txt.gzip application/octet-stream

Replies

Subject Author
Re: [gentoo-alpha] problem upgrading the toolchain Marc Giger <gigerstyle@×××.ch>