From: Etaoin Shrdlu <shrdlu@unlimitedmail.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Going to multilib
Date: Sun, 6 Dec 2009 15:04:47 +0000 [thread overview]
Message-ID: <200912061504.47279.shrdlu@unlimitedmail.org> (raw)
Ok, so I have some apps that require 32 bit libraries, but I'm currently using
a no-multilib profile.
This page
http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml
says:
"Warning: Currently you cannot switch from a no-multilib to a multilib-enabled
profile, so think over your decision twice before you use the no-multilib
profile."
Now, I know that I can install most of the emul-linux-x86-* stuff and that
will probably be enough for me, but I was wondering what the technical
problems iwould be if I just changed my /etc/make.profile to point to a
multilib profile. As far as I can tell, gcc and glibc would be rebuilt with
USE=multilib, and a new set of libraries would be installed into /lib32 and
/usr/lib32 (in addition to those already installed under the corresponding
lib64 locations). So, how would that break the existing applications?
Thanks for any insight.
next reply other threads:[~2009-12-06 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 15:04 Etaoin Shrdlu [this message]
2009-12-06 16:04 ` [gentoo-user] Going to multilib Etaoin Shrdlu
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=200912061504.47279.shrdlu@unlimitedmail.org \
--to=shrdlu@unlimitedmail.org \
--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