From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: poky-image-sato-sdk failed at do_rootfs
Date: Wed, 02 Feb 2011 14:06:29 +0000 [thread overview]
Message-ID: <1296655589.1544.3260.camel@rex> (raw)
In-Reply-To: <4D4962A5.8060406@windriver.com>
On Wed, 2011-02-02 at 07:56 -0600, Mark Hatle wrote:
> On 2/2/11 5:33 AM, Wolfgang Denk wrote:
> > Dear Richard Purdie,
> >
> > In message <1296645484.1544.2556.camel@rex> you wrote:
> >>
> >>>> Did you leave NO32LIBS set in local.conf as per the default?
> >>>
> >>> Good point - sorry, I had forgotten about that. I always comment out
> >>> NO32LIBS because when building the SDK I also need this for 32 bit
> >>> machines.
> >>
> >> This option really just controls psuedo-native, it has no effect on the
> >
> > I see - that was not clear to me from the comment ("Default to not
> > build 32 bit libs on 64 bit systems, comment this out if that is
> > desired").
> >
> > When is this option needed, then? If it was not needed (and is
> > broken), should it eventually be removed?
>
> PSEUDO is similar to fakeroot, it is a LD_PRELOADed library that intercepts
> certain calls, and emulates a root user capable environment.
>
> As such, it MUST be able to intercept both 32-bit and 64-bit function calls,
> when both are available on a host.
>
> So if you have both 32-bit and 64-bit binaries installed on your host, you need
> to disable the NO32LIBS, otherwise you could end up with an incomplete faked
> root environment.
Since poky builds all its own tools out the box, this isn't something
I've ever seen a user get bitten by so far. There are people using say
an external 32 bit toolchain on a 64 bit machine who do need this
functionality though.
Cheers,
Richard
next prev parent reply other threads:[~2011-02-02 14:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 1:33 poky-image-sato-sdk failed at do_rootfs Zhang, Jessica
2011-01-30 2:00 ` Cui, Dexuan
2011-01-30 7:16 ` Zhang, Jessica
2011-01-30 7:46 ` Lu, Lianhao
2011-01-30 7:58 ` Zhang, Jessica
2011-01-30 8:05 ` Cui, Dexuan
2011-01-30 8:16 ` Lu, Lianhao
2011-01-30 8:26 ` Zhang, Jessica
2011-01-30 10:13 ` Richard Purdie
2011-01-30 12:20 ` Tian, Kevin
2011-01-30 14:49 ` Lu, Lianhao
2011-01-31 15:24 ` Lu, Lianhao
2011-01-31 16:40 ` Richard Purdie
2011-02-01 0:58 ` Zhang, Jessica
2011-02-01 11:55 ` Richard Purdie
2011-02-01 13:07 ` Zhang, Jessica
2011-02-01 13:32 ` Richard Purdie
2011-02-01 19:27 ` Wolfgang Denk
2011-02-01 20:00 ` Mark Hatle
2011-02-01 22:08 ` Wolfgang Denk
2011-02-01 23:29 ` Richard Purdie
2011-02-02 7:03 ` Wolfgang Denk
2011-02-02 11:18 ` Richard Purdie
2011-02-02 11:33 ` Wolfgang Denk
2011-02-02 13:56 ` Mark Hatle
2011-02-02 14:05 ` Wolfgang Denk
2011-02-02 14:06 ` Richard Purdie [this message]
2011-02-02 14:56 ` Mark Hatle
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=1296655589.1544.3260.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=mark.hatle@windriver.com \
--cc=poky@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.