From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Installation of i686 SDK on a x86_64 machine?
Date: Tue, 22 Jan 2013 10:08:32 +0200 [thread overview]
Message-ID: <50FE4900.7020804@intel.com> (raw)
In-Reply-To: <20130122071621.9D11520DA8C@gemini.denx.de>
Hi Wolfgang,
On 01/22/2013 09:16 AM, Wolfgang Denk wrote:
> Hi,
>
> in previous releases it ha always been possible to install a SDK
> configured for a i686 machine on both x86 and x86_64 systems.
>
> Since commit c04f5435 "populate_sdk_base.bbclass: use SDK_ARCH instead
> of SDKMACHINE" this does not work any more; instead, installation will
> abort with "Error: Installation machine not supported!"
>
> ++ uname -m
> ++ sed -e 's/i[3-6]86/ix86/' -e 's/x86[-_]64/x86_64/'
> + INST_ARCH=x86_64
> ++ echo i686
> ++ sed -e 's/i[5-6]86/ix86/'
> + SDK_ARCH=ix86
> + '[' x86_64 '!=' ix86 ']'
> + echo 'Error: Installation machine not supported!'
> Error: Installation machine not supported!
> + exit -1
>
>
> Is this intended behaviour (and if so, why?) or rather a bug that
> should be reported and fixed?
This is the intended behavior. Please check:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3269
Also, this thread:
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-November/031519.html
If people really need to install SDK tarballs intended for other hosts
than the SDK was built for (i686 on x86_64 or vice-versa), we could add
a -f flag to force installation and show an error message like this:
"Error: Installation machine not supported! Use -f to force installation."
Thanks,
Laurentiu
>
> Thanks in advance.
>
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2013-01-22 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 7:16 Installation of i686 SDK on a x86_64 machine? Wolfgang Denk
2013-01-22 8:08 ` Laurentiu Palcu [this message]
2013-01-22 9:03 ` Wolfgang Denk
2013-01-22 9:44 ` Laurentiu Palcu
2013-01-22 11:14 ` Wolfgang Denk
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=50FE4900.7020804@intel.com \
--to=laurentiu.palcu@intel.com \
--cc=wd@denx.de \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.