public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bob Sanders <rmsand@concentric.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 (AMD64 users please help)
Date: Sun, 24 Jul 2005 11:10:39 -0700	[thread overview]
Message-ID: <20050724111039.77e97834@chi.speakeasy.net> (raw)
In-Reply-To: <42E3AE89.1010506@asmallpond.org>

On Sun, 24 Jul 2005 17:06:49 +0200
Richard Fish <bigfish@asmallpond.org> wrote:


> 
> Argh, I don't get it.  /u/p/p/default-linux/amd64/2005.0/use.mask 
> contains "multilib", but with a comment stating it is forced on when 
> MULTILIB_ABIS is defined, and make.defaults has MULTILIB_ABIS="x86 amd64".
> 
> Can any AMD64 users shed some light on this please?
> 

multilib can be, or it used to be able to, turned off so that only 64-bit versions of the
libs get built.

Normally, it should be turned on and set in the USE string, for most folks on a x86_64
platform.  But, on a system without multilib, turning it on means that, as a minimum an -

		emerge -uDav --newuse system

will need to be performed to rebuild gcc, glibc and all the base system libs so that the following
get created - 

	/lib64
	/lib32
	/usr/lib32
	/usr/lib64

and a few other items.

Bob
-  
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-07-24 18:15 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-23 11:38 [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 Jules Colding
2005-07-23 12:36 ` Patrick Börjesson
2005-07-23 12:50 ` Holly Bostick
2005-07-23 13:14   ` Jules Colding
2005-07-23 15:51   ` Patrick Börjesson
2005-07-23 16:37     ` Richard Fish
2005-07-23 17:08       ` Patrick Börjesson
2005-07-23 18:19         ` Richard Fish
2005-07-23 23:02           ` Patrick Börjesson
2005-07-24 12:43             ` Jules Colding
2005-07-25  2:09         ` Holly Bostick
2005-07-23 18:38   ` neil
2005-07-24 17:23     ` Neil Bothwick
2005-07-23 18:46 ` Bob Sanders
2005-07-23 18:51 ` Zac Medico
2005-07-23 21:26   ` Richard Fish
2005-07-24 12:28     ` Jules Colding
2005-07-24 11:07   ` Jules Colding
2005-07-24 13:20     ` Richard Fish
2005-07-24 13:28       ` Jules Colding
2005-07-24 13:51         ` Richard Fish
2005-07-24 13:57           ` Jules Colding
2005-07-24 13:58           ` Richard Fish
2005-07-24 14:27             ` Jules Colding
2005-07-24 14:43               ` Rumen Yotov
2005-07-24 14:47                 ` Jules Colding
2005-07-24 15:06               ` [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 (AMD64 users please help) Richard Fish
2005-07-24 15:12                 ` Jules Colding
2005-07-24 18:10                 ` Bob Sanders [this message]
2005-07-24 18:59                   ` Jules Colding
2005-07-24 19:14                   ` Richard Fish
2005-07-26  1:37                     ` Bob Sanders
2005-07-24 14:00         ` [gentoo-user] Can't emerge mozilla-firefox-1.0.6-r2 Zac Medico
2005-07-24 15:29     ` neil
2005-07-24 12:22   ` Jules Colding
2005-07-24 12:38     ` Jules Colding
2005-07-24 12:48       ` Richard Fish
2005-07-24 13:10         ` Jules Colding
2005-07-24 13:30           ` Richard Fish
2005-07-24 13:28       ` Rumen Yotov
2005-07-24 13:35         ` Jules Colding

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=20050724111039.77e97834@chi.speakeasy.net \
    --to=rmsand@concentric.net \
    --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