From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: 64-bit or 32-bit?
Date: Tue, 28 Mar 2006 12:53:02 -0700 [thread overview]
Message-ID: <pan.2006.03.28.19.53.01.867666@cox.net> (raw)
In-Reply-To: 43872d370603280717w2b6ccbd9l9dae6e21a9a927d2@mail.gmail.com
Bertrand Jacquin posted
<43872d370603280717w2b6ccbd9l9dae6e21a9a927d2@mail.gmail.com>, excerpted
below, on Tue, 28 Mar 2006 17:17:27 +0200:
> How could you compile mplayer or firefox in your 64 bits environnement
> to generate 32 bits binary ? I have multilib activated and I can't
> build mplayer with CFLAGS="-m32".
>
> It is needing something else ?
>
> I don't want too to have and maintain a 32 bit chroot.
There /are/ the 32-bit precompiled packages for those in the tree,
firefox-bin and mplayer-bin, if you want to merge them. Note that these
use different executable names so you can even have both your regular
64-bit and the 32-bit-binary versions merged side by side.
As for why you can't seem to compile the 32-bit binaries, it's very
possibly because you are missing certain of the libraries and other
dependencies, or more likely, the 32-bit headers for them necessary for
compilation. Naturally, you could track all this stuff manually, but
that's what portage is for -- only it can track only one bitness at a
time. Thus, the idea of a 32-bit chroot, complete with its own instance
of portage, which can track all the 32-bit dependencies necessary to
compile in 32-bit what you really want, firefox and mplayer, in this case.
Sure, it's /possible/ to track all those dependencies manually, but it's
/far/ easier to run a chroot for the purpose and let portage do what
portage does well -- automate all that stuff for you so you don't have to
worry about it.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-28 19:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 15:33 [gentoo-amd64] 64-bit or 32-bit? JimD
2006-03-26 15:45 ` Mike Arthur
2006-03-26 17:09 ` Simon Stelling
2006-03-26 17:50 ` Hemmann, Volker Armin
2006-03-26 18:27 ` Jim
2006-03-26 19:03 ` Hemmann, Volker Armin
2006-03-26 21:20 ` Barry.SCHWARTZ
2006-03-26 23:08 ` Jim
2006-03-27 0:10 ` Barry.SCHWARTZ
2006-03-28 15:17 ` Bertrand Jacquin
2006-03-28 19:53 ` Duncan [this message]
2006-03-28 22:06 ` Barry.SCHWARTZ
2006-03-28 22:20 ` Simon Stelling
2006-03-28 22:27 ` Barry.SCHWARTZ
2006-03-29 10:21 ` Bertrand Jacquin
2006-03-29 15:35 ` Simon Stelling
2006-03-29 17:25 ` Mike Arthur
2006-03-29 17:36 ` Simon Stelling
2006-03-29 17:58 ` Mike Arthur
2006-03-29 18:00 ` [gentoo-amd64] 32-bit Netscape Plugins in Konqueror Mike Arthur
2006-03-29 20:43 ` [gentoo-amd64] 64-bit or 32-bit? Barry.SCHWARTZ
2006-03-28 22:49 ` Marco Matthies
2006-03-29 10:19 ` Bertrand Jacquin
2006-03-29 11:14 ` Marco Matthies
2006-03-29 15:53 ` [gentoo-amd64] " Duncan
2006-03-29 12:58 ` [gentoo-amd64] " Vladimir G. Ivanovic
2006-03-29 15:30 ` Simon Stelling
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 11:27 Anand Buddhdev
2005-07-12 15:37 ` [gentoo-amd64] " Duncan
2005-07-12 17:51 ` Kyle Liddell
2005-07-12 20:19 ` Richard Freeman
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=pan.2006.03.28.19.53.01.867666@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@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