From: Richard Purdie <rpurdie@linux.intel.com>
To: Hector Oron <hector.oron@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Build failures on yocto
Date: Tue, 02 Nov 2010 11:27:04 +0000 [thread overview]
Message-ID: <1288697224.28481.1124.camel@rex> (raw)
In-Reply-To: <AANLkTikf5R=dnMKpEX+V4awP=3Dt5+ttcoCVD0TAP8Kb@mail.gmail.com>
On Tue, 2010-11-02 at 10:03 +0000, Hector Oron wrote:
> > At a guess this is a 64 bit kernel and a 32 bit userspace? What does
> > "uname -a" show?
>
> Yes, it is 64 bit kernel host running a 32 bit userland.
> Linux enorme 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux
>
> > I suspect if you add
> >
> > BUILD_ARCH = "i686"
> >
> > to your local.conf, the build might work better? If you can confirm that
> > we can probably detect this problem and avoid this failure.
>
> Build attempted with
> BUILD_ARCH="i686" BB_NUMBER_THREADS="2" PARALLEL_MAKE="-j 2"
> MACHINE=$(BOARD) bitbake $(YOCTO_IMAGE)
> got same result as above.
Only certainly variables can be passed through the environment. Can you
put the line in local.conf please and retry as otherwise it won't have
any effect.
> > Same as the above failure (64 bit kernel and 32 bit userspace)?
>
> Sure.
>
> >> others|*)
> >> cat <<EOF
> >> - I need to setup "vm.mmap_min_addr = 0" under /etc/sysctl.conf
> >
> > Right, but it detected that?
>
> If it was not set, scripts warn about it, once you set it up, it goes through.
Ok, good.
Cheers,
Richard
next prev parent reply other threads:[~2010-11-02 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 18:23 Build failures on yocto Hector Oron
2010-11-01 20:48 ` Richard Purdie
2010-11-02 10:03 ` Hector Oron
2010-11-02 11:27 ` Richard Purdie [this message]
2010-11-02 9:17 ` Hector Oron
2010-11-02 9:51 ` Richard Purdie
2010-11-02 10:08 ` Hector Oron
2010-11-02 11:29 ` Richard Purdie
2010-11-02 11:39 ` Hector Oron
2010-11-02 12:07 ` 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=1288697224.28481.1124.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=hector.oron@gmail.com \
--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.