Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Multilib Development Update
Date: Tue, 21 Jun 2011 15:33:03 +0200	[thread overview]
Message-ID: <4E009D8F.10301@eukrea.com> (raw)
In-Reply-To: <1308663032.20015.29.camel@rex>

Hi,

On 21/06/2011 15:30, Richard Purdie wrote:
> On Tue, 2011-06-21 at 15:02 +0200, Frans Meulenbroeks wrote:
>> As I already asked before: what is the benefit having this in embedded
>> systems?
>>
>> If I am doing an embedded system I know the target hardware, and there
>> is no need to have e.g. both 32 and 64 bit libs.
>
> This has been mentioned before but there are embedded use cases where
> the requirement is to have a low overhead OS using 32 bit libs and
> binaries to save memory but the main application (like a database
> server) runs in 64 bit mode with 64 bit libraries so it can take
> advantage of system memory, extra instructions or so forth. This applies
> to mips and powerpc as well as x86.
>
> The implementation is fairly self contained so if you don't want
> multilib, you shouldn't even be aware its there...
>
will that feature allow to build a sdk running on both x86 and amd64 hosts 
whatever is the build host ?

Eric



  reply	other threads:[~2011-06-21 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 12:14 Multilib Development Update Richard Purdie
2011-06-21 12:28 ` Koen Kooi
2011-06-21 13:31   ` Richard Purdie
2011-06-21 13:02 ` Frans Meulenbroeks
2011-06-21 13:30   ` Richard Purdie
2011-06-21 13:33     ` Eric Bénard [this message]
2011-06-21 16:43       ` Khem Raj
2011-06-21 17:00       ` Richard Purdie
2011-06-21 14:35   ` Mark Hatle
2011-06-21 14:32 ` Khem Raj
2011-06-21 14:51   ` Mark Hatle
2011-06-29  9:10 ` [Multilib] a problem of SHLIBSDIR Lu, Lianhao
2011-06-29  9:49   ` Richard Purdie

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=4E009D8F.10301@eukrea.com \
    --to=eric@eukrea.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