From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Problems compiling gcc 4.2.4 and 4.3.1-r1
Date: Wed, 16 Jul 2008 16:35:39 +0300 [thread overview]
Message-ID: <g5ktfd$but$1@ger.gmane.org> (raw)
In-Reply-To: <18557.38367.217512.342985@ccs.covici.com>
John covici wrote:
> on Tuesday 07/15/2008 Neil Bothwick(neil@digimed.co.uk) wrote
> > On Tue, 15 Jul 2008 03:54:43 -0400, John covici wrote:
> >
> > > > Did you try updating glibc even though it's not a dependency with
> > > > x86?
> > >
> > > Nope, because I was hesitant being this is an unstable version
> >
> > It is not unstable, the ~arch keyword means the ebuild is still in
> > testing. Nowhere in the Gentoo docs does it say that setting ~arch will
> > install unstable software. If software not fit for general use is
> > included in the portage treee, like betas and release candidates, it is
> > generally package-masked so even ~arch systems won't install it without
> > specifically unmasking it.
> >
>
> OK, thanks for the clarification -- and indeed getting the latest
> glibc did enable me to compile gcc-4.3.1-r1.
Please post in http://bugs.gentoo.org/show_bug.cgi?id=191088 about it,
so that the newer glibc will become a dependency also for x86.
--
gentoo-user@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-07-16 13:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 1:36 [gentoo-user] Problems compiling gcc 4.2.4 and 4.3.1-r1 John covici
2008-07-14 1:43 ` [gentoo-user] " Nikos Chantziaras
2008-07-14 1:53 ` John covici
2008-07-14 2:03 ` Nikos Chantziaras
2008-07-14 15:18 ` [gentoo-user] " Joe User
2008-07-14 15:25 ` John covici
2008-07-14 15:34 ` Daniel Pielmeier
2008-07-15 4:36 ` [gentoo-user] " Nikos Chantziaras
2008-07-15 7:29 ` John covici
2008-07-15 7:46 ` Nikos Chantziaras
2008-07-15 7:54 ` John covici
2008-07-15 8:18 ` Nikos Chantziaras
2008-07-15 9:04 ` Neil Bothwick
2008-07-16 6:31 ` John covici
2008-07-16 13:35 ` Nikos Chantziaras [this message]
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='g5ktfd$but$1@ger.gmane.org' \
--to=realnc@arcor.de \
--cc=gentoo-user@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