public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthew Kennedy <mkennedy@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GCC 3.1/binutils 2.12 and glibc compile problems
Date: 05 Jun 2002 22:07:54 -0500	[thread overview]
Message-ID: <1023332874.7556.19.camel@gentoo.shacknet.nu> (raw)
In-Reply-To: <20020528104638.16e88e26.webmaster@refstart.nl>

On Tue, 2002-05-28 at 03:46, Webmaster Refstart.NL wrote:

> gawk: scripts/versions.awk:68: (FILENAME=- FNR=3) fatal: printf to "sort -n > /v
> ar/tmp/portage/glibc-2.2.5-r2/work/glibc-2.2.5/buildhere/Versions.tmp" failed (B
> roken pipe)
> sed: couldn't write 69 items to {standard output}: Broken pipe
> stdout: Broken pipe
> make[1]: *** [/var/tmp/portage/glibc-2.2.5-r2/work/glibc-2.2.5/buildhere/sysd-ve
> rsions] Error 2
> make[1]: Leaving directory '/var/tmp/portage/glibc-2.2.5-r2/work/glibc-2.2.5'
> make: *** [all] Error 2

That is symptomatic of a portage (ie. sandbox) built with a gcc3.1. See
the m4/autoconf bug. You might try unpacking the rescue portage (which
afaik, is bot built with gcc3.1) to get around this.

Matt

-- 
Matthew Kennedy
Gentoo Linux Developer



  parent reply	other threads:[~2002-06-06  3:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27 19:18 [gentoo-dev] GCC 3.1/binutils 2.12 and glibc compile problems Webmaster Refstart.NL
2002-05-27 21:50 ` Lars Pechan
2002-05-28  8:46   ` Webmaster Refstart.NL
2002-05-28  8:59     ` Spider
2002-05-28 16:23       ` Webmaster Refstart.NL
2002-06-06  3:07     ` Matthew Kennedy [this message]
2002-05-27 22:37 ` Bill Kenworthy
2002-05-27 22:45   ` Lars Pechan

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=1023332874.7556.19.camel@gentoo.shacknet.nu \
    --to=mkennedy@gentoo.org \
    --cc=gentoo-dev@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