From: Will Briggs <will@burnieanglican.org.au>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] glibc update problem
Date: Wed, 01 Mar 2006 11:24:56 +1100 [thread overview]
Message-ID: <4404E9D8.5060701@burnieanglican.org.au> (raw)
In-Reply-To: <20060228225750.7564725213F@smtp.nildram.co.uk>
Rupert Young (Restart) wrote:
>
> Hi,
>
> Our server is getting stuck on updating packages. We can not seem to
> get past the upgrade to glibc. Sometimes it fails, with an error, and
> sometimes it actually kills the machine requiring reboot, examples of
> both below. Sorry if this is a known problem, but I’ve been looking
> and struggling with it for a couple of weeks. Any help would be
> appreciated, here’s the info from emerge,
>
> emerge --info
>
<snip>
>
> The bug is not reproducible, so it is likely a hardware or OS problem.
>
> make[2]: ***
> [/var/tmp/portage/glibc-2.3.5-r2/work/build-default-x86_64-pc-linux-gnu-linuxthreads/iconvdata/iso_6937-2.os]
> Error 1
>
> make[2]: *** Waiting for unfinished jobs....
>
> make[2]: Leaving directory
> `/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5/iconvdata'
>
> make[1]: *** [iconvdata/others] Error 2
>
> make[1]: Leaving directory
> `/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5'
>
> make: *** [all] Error 2
>
> !!! ERROR: sys-libs/glibc-2.3.5-r2 failed.
>
> !!! Function toolchain-glibc_src_compile, Line 226, Exitcode 2
>
> !!! (no error message)
>
> !!! If you need support, post the topmost build error, NOT this status
> message.
>
> Any help appreciated.
>
When I experienced this problem it was only during building stuff that
pushed compiler to its limits - glibc, gcc, qt - that sort of stuff.
Fixed by replacing heat compound between CPU and heatsink.
W.
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-01 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 22:57 [gentoo-amd64] glibc update problem Rupert Young (Restart)
2006-02-28 23:17 ` Boyd Stephen Smith Jr.
2006-02-28 23:21 ` Richard Fish
2006-02-28 23:26 ` Jan Riedel
2006-03-01 0:13 ` David Guerizec
2006-03-01 0:24 ` Will Briggs [this message]
2006-03-01 17:45 ` Hemmann, Volker Armin
2006-03-01 18:01 ` Simon Strandman
2006-03-02 0:08 ` [gentoo-amd64] " Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4404E9D8.5060701@burnieanglican.org.au \
--to=will@burnieanglican.org.au \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox