From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] populate_sdk_base.bbclass: Allow installation of ix86 SDK on x86_64 host
Date: Thu, 24 Jan 2013 11:23:29 +0200 [thread overview]
Message-ID: <5100FD91.2030508@intel.com> (raw)
In-Reply-To: <50FEBA91.7060804@windriver.com>
On 01/22/2013 06:13 PM, Mark Hatle wrote:
> On 1/22/13 6:18 AM, Wolfgang Denk wrote:
>> > Commit c04f5435 "populate_sdk_base.bbclass: use SDK_ARCH instead
>> > of SDKMACHINE" prevents not only the installation of 64 bit SDK
>> > configurations on 32 bit hosts (which indeed cannot work), but also
>> > the legitimate installation of a 32 bit SDK on a 64 bit host.
>> >
>> > Fix this.
>> >
>> > While there, also make sure we use the same patterns ("i[3-6]86" resp.
>> > "x86[-_]64" to get unified strings for both INST_ARCH and SDK_ARCH.
> As far as I am aware, this is intentional. For various SDK items
> pseudo/libpseudo may be used. On a 32-bit SDK, only a 32-bit pseudo/libpseudo
> is available. This will prevent it from working with any host system binaries
> that are x86_64.
>
> If you don't care, the "workaround" is to use setarch and install it by telling
> the system you are an ix86 target.
>
> --Mark
>
>> >
Hi Mark,
There was a discussion on the yocto mailing list about this:
https://lists.yoctoproject.org/pipermail/yocto/2013-January/013889.html
Also, a bug filed:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3770
It turns out that people would like to be able to install 32-bit SDKs on
64-bit machines. Provided they have the 32-bit libraries in place.
Thanks,
Laurentiu
prev parent reply other threads:[~2013-01-24 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 12:18 [PATCH] populate_sdk_base.bbclass: Allow installation of ix86 SDK on x86_64 host Wolfgang Denk
2013-01-22 16:13 ` Mark Hatle
2013-01-24 9:23 ` Laurentiu Palcu [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=5100FD91.2030508@intel.com \
--to=laurentiu.palcu@intel.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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