From: Justin Patrin <papercrane@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] i386 vs amd64
Date: Sat, 22 Oct 2005 19:34:08 -0700 [thread overview]
Message-ID: <432beae0510221934g452bacdbp46059bdf5652fd46@mail.gmail.com> (raw)
In-Reply-To: <435AA7F4.2090406@comcast.net>
On 10/22/05, Sean <rsh.lists@comcast.net> wrote:
>
>
> All,
>
> Thanks for your responses, I plan to try out the amd64 version.
>
Be very careful if you're doing any cross-compiling. The system
headers in Gentoo AMD64 are hacked to allow compiling for both 64 and
32-bit. If you try compiling for, say, ARM and it picks up the system
headers you get *nothing*....wonderful, eh?
To Gentoo devs:
Might I suggest that the system headers default to 32-bit?
--
Justin Patrin
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-23 2:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 0:07 [gentoo-user] i386 vs amd64 Sean
2005-10-21 0:19 ` Peter Gordon
2005-10-21 4:19 ` Bob Sanders
2005-10-22 20:58 ` Sean
2005-10-23 2:34 ` Justin Patrin [this message]
2005-10-21 12:54 ` Scott Tiret
2005-10-21 15:46 ` Neil Bothwick
2005-10-21 17:02 ` Rob
2005-10-21 19:37 ` Richard Fish
2005-10-21 20:49 ` [gentoo-user] i386 vs amd64/ forget my Python comparisons Rob
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=432beae0510221934g452bacdbp46059bdf5652fd46@mail.gmail.com \
--to=papercrane@gmail.com \
--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