From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Best plan for cross compiling for i686
Date: Sat, 5 Aug 2006 17:33:32 -0700 [thread overview]
Message-ID: <7573e9640608051733p7ce00bdaq27a482290db5e300@mail.gmail.com> (raw)
In-Reply-To: <eb3amk$f9c$1@sea.gmane.org>
On 8/5/06, Duncan <1i5t5.duncan@cox.net> wrote:
> Have you read the amd64 chroot guide? If not, read it, as that's
Um, er....no.
> one little bit -- the command to change your uname to x86 so those
> packages don't mess up.
Yep, I missed the linux32/setarch trick.
I have a pretty major KDE update compiling now, after which I will
probably do the linux32 thing and start an emerge -ev world in the
chroot to see what breaks.
Thanks Duncan for pointing out that I should have RTFM!!
-Richard
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-06 0:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 21:08 [gentoo-amd64] Best plan for cross compiling for i686 Richard Fish
2006-08-05 21:48 ` Thierry de Coulon
2006-08-05 22:27 ` Richard Fish
2006-08-05 23:33 ` Peter Hoff
2006-08-06 18:05 ` Paul de Vrieze
2006-08-05 23:47 ` [gentoo-amd64] " Duncan
2006-08-06 0:33 ` Richard Fish [this message]
2006-08-06 0:01 ` [gentoo-amd64] " Brian Litzinger
2006-08-06 0:39 ` 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=7573e9640608051733p7ce00bdaq27a482290db5e300@mail.gmail.com \
--to=bigfish@asmallpond.org \
--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