From: Darren Grant <dgrant@monstertech.ca>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading from gcc-3.4.5 to gcc-3.4.6-r1
Date: Thu, 29 Jun 2006 17:10:52 -0700 [thread overview]
Message-ID: <44A46C0C.40702@monstertech.ca> (raw)
In-Reply-To: <7573e9640606291119n3c36f3e6xb49ae553a6c056a0@mail.gmail.com>
Richard Fish wrote:
> On 6/28/06, Darren Grant <dgrant@monstertech.ca> wrote:
>> Any chance that's what's causing my gcc problems now?
>
> Hmm, I doubt it. But in comparing what you have posted to my AMD64
> box, I see some things that don't look right. For example, on my
> AMD64 box, I have:
>
> Gentoo Base System version 1.12.0
> Portage 2.1 (default-linux/amd64/2006.0, gcc-4.1.1/amd64-vanilla,
> glibc-2.4-r3, 2.6.16 x86_64)
> =================================================================
> System uname: 2.6.16 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor
> 4400+
>
> Notice my profile is default-linux/amd64/<something>, where you have
> your profile as just default-linux/amd64. I'm not sure that is
> actually supported...and may in fact be the cause of your trouble.
>
> The new profiles (starting with 2005.1) are "multilib" by default, so
> for example merging glibc will try to build both i686 and x86_64
> versions. So it is in fact perfectly reasonble for an emerge of glibc
> to try to build a i686 version, but *only* if you are using a multilib
> profile. Similarly gcc would try to build i686 versions of its
> libraries, but would require an i686 glibc to be available first.
>
> I suspect what you need to do is:
>
> cd /etc
> rm make.profile
> ln -s ../usr/portage/profiles/default-linux/amd64/2005.1/no-multilib
>
> Then try re-merging glibc and gcc.
>
> If you want to switch to the multilib profile, the symlink should be
> to /usr/portage/profiles/default-linux/amd64/2005.1 or 2006.0. But
> you might want to ask on gentoo-amd64 about how to switch from
> no-multilib to a multilib profile...
>
> -Richard
Didn't seem to help... I can emerge certain packages, but still can't
re-merge gcc and glibc.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-30 0:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 18:39 [gentoo-user] Upgrading from gcc-3.4.5 to gcc-3.4.6-r1 Darren Grant
2006-06-27 20:28 ` Benno Schulenberg
2006-06-27 21:26 ` Darren Grant
2006-06-28 2:53 ` Richard Fish
2006-06-28 15:44 ` Darren Grant
2006-06-28 16:00 ` Richard Fish
2006-06-28 16:40 ` Richard Fish
2006-06-28 16:43 ` Richard Fish
2006-06-28 17:17 ` Darren Grant
2006-06-28 17:42 ` Richard Fish
2006-06-28 18:18 ` Benno Schulenberg
2006-06-28 18:53 ` Darren Grant
2006-06-28 19:11 ` Benno Schulenberg
2006-06-28 20:43 ` Darren Grant
2006-06-28 21:30 ` Darren Grant
2006-06-29 10:49 ` Benno Schulenberg
2006-06-29 16:45 ` Darren Grant
2006-06-29 20:37 ` Benno Schulenberg
2006-06-29 18:19 ` Richard Fish
2006-06-30 0:10 ` Darren Grant [this message]
2006-06-30 17:15 ` Richard Fish
2006-06-30 17:44 ` Darren Grant
2006-06-30 18:36 ` Alexander Skwar
2006-06-28 18:44 ` Darren Grant
2006-06-28 2:48 ` Richard Fish
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=44A46C0C.40702@monstertech.ca \
--to=dgrant@monstertech.ca \
--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