From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-core] build for 32bit architecture
Date: Wed, 18 Apr 2012 08:10:05 -0600 [thread overview]
Message-ID: <4F8ECB3D.7040200@mlbassoc.com> (raw)
In-Reply-To: <CAOHjBZu=T6TrSomYSOW+Sp5afFwHTu5f4zGKx-3T361gdrJdmg@mail.gmail.com>
On 2012-04-18 07:48, Giuseppe Condorelli wrote:
> Hi All,
>
> I need to build the native packages for a 32bit architecture, although I'm
> working on a 64bit machine.
> So I need to pass the -m32 option to the compiler and my question is about
> the right place where to put it
> to be inherited by all native packages.
Why would you need 32bit native packages when your build host is 64bit?
The native packages are only used to provide functionality during the
build and hence (it makes sense to me at least) they should match the
build host native environment.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-04-18 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 13:48 [oe-core] build for 32bit architecture Giuseppe Condorelli
2012-04-18 14:10 ` Gary Thomas [this message]
2012-04-18 14:17 ` Giuseppe Condorelli
2012-04-18 17:50 ` Denys Dmytriyenko
2012-04-18 16:44 ` McClintock Matthew-B29882
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=4F8ECB3D.7040200@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@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 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.