From: "Andreas Bießmann" <biessmann@corscience.de>
To: ptxdist@pengutronix.de
Cc: "Andreas Bießmann" <andreas@biessmann.de>, Klaus.Hachmeister@l-3com.com
Subject: Re: [ptxdist] Detect if x86 target is 32 or 64bit?
Date: Wed, 15 Feb 2012 10:08:13 +0100 [thread overview]
Message-ID: <4F3B75FD.20508@corscience.de> (raw)
In-Reply-To: <1846417.Lzzx8S0Ecs@ws-stein>
Hi Alexander,
On 15.02.2012 08:30, Alexander Stein wrote:
> Hello Andreas,
>
> Am Mittwoch, 15. Februar 2012, 07:47:04 schrieb Andreas Bießmann:
>> is there any conclusion to this discussion?
>> I startet to build a x86_64 rootfs (on top of i586-qemu-bsp) and failed
>> to build sylinux due to some wrong decisions in syslinux.make (another
>> discussion ..).
>> I started defining ARCH_X86_64 as optimization of ARCH_X86. Alexander,
>> are you building x86_64 stuff too ore did you only ask cause of the
>> ability to build gnu-efi for ia32, x86_32 and ia64?
>
> I didn't work on this topic again. But yes, I asked only for gnu-efi stuff. Until now we are only building 32bit.
Ok.
>>> Another problem prio to this is a 64bit toolchain in ptxdist. Up to now there is no OSELAStoolchain for x86_64.
>>
>> Can you please test my OSELAS.Toolchain x86_64 patches?
>
> IIRC from other mails, do you need a x86_64 host to use a x86_64 toolchain? Well, I'm running a x86_64 host, so this wouldn't be a problem.
No, that is a misunderstanding here.
You can build the x86_64-unknown-linux-gnu OSELAS.Toolchain on any host
you want (even Mac OS X as I did).
If you have a host that has the same GNU triplet as the target (and that
may be the fact for some users with x86 build host and x86 target
toolchain but not only he x86_64 toolchain) the autotools mechanism will
end up in deciding for native build which means e.g. gcc without
prefixed arch triplet. Therefore one of my patches adds explicit
'--build=' switch to cross-tools configure to fool the autotools
guessing mechanism by providing a non-guessable arch triplet (e.g.
x86_64-host-linux-gnu -> see GNU_HOST in <ptxdist>/rules/pre/Rules.make).
This let the autoconf logic think it has a x86_64-host-linux-gnu build
system building a x86_64-unknown-linux-gnu target toolchain running on a
x86_64-unknown-linux-gnu host system which would be 'cross compiling'.
The resulting tools have the arch triplet prefixed and everything should
be fine.
I hope this is clear now. Feel free to test the OSELAS.Toolchain
patches, would be great to get some feedback.
best regards
Andreas Bießmann
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-02-15 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 14:27 Alexander Stein
2012-01-04 16:59 ` Michael Olbrich
2012-01-31 8:21 ` Alexander Stein
2012-01-31 14:12 ` Michael Olbrich
2012-02-01 12:49 ` Alexander Stein
2012-02-06 20:08 ` Michael Olbrich
2012-02-15 6:47 ` Andreas Bießmann
2012-02-15 7:30 ` Alexander Stein
2012-02-15 9:08 ` Andreas Bießmann [this message]
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=4F3B75FD.20508@corscience.de \
--to=biessmann@corscience.de \
--cc=Klaus.Hachmeister@l-3com.com \
--cc=andreas@biessmann.de \
--cc=ptxdist@pengutronix.de \
/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