From: Joshua Lock <josh@openedhand.com>
To: poky@yoctoproject.org
Subject: Re: Out of date warning?
Date: Fri, 25 Feb 2011 13:57:27 +0000 [thread overview]
Message-ID: <1298642247.2684.6.camel@scimitar> (raw)
In-Reply-To: <4D67B298.9030107@mlbassoc.com>
On Fri, 2011-02-25 at 06:46 -0700, Gary Thomas wrote:
> Poky just presented me with this warning (on a new machine), when building for
> an ARM (OMAP/3530) platform:
>
> ===================================================================================
> $ bitbake omap-installer-image
> Pseudo is not present but is required, building this first before the main build
> ERROR: Poky's config sanity checker detected a potential misconfiguration.
> Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
> Following is the list of potential problems / advisories:
>
> /proc/sys/vm/mmap_min_addr is not 0. This will cause problems with qemu so please fix the value (as root).
>
> To fix this in later reboots, set vm.mmap_min_addr = 0 in /etc/sysctl.conf.
> ===================================================================================
>
> I know this warning was in place because Qemu was used to run some
> tasks, e.g. locale generation. My impression is that this is no longer
> the case, so do we still need this warning?
>
We have a bug tracking the issue:
http://bugzilla.pokylinux.org/show_bug.cgi?id=543
Most recent update indicates that there are still edge cases which
require this check to be in place, though possibly only when running
qemu for arm images?
Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-02-25 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 13:46 Out of date warning? Gary Thomas
2011-02-25 13:57 ` Joshua Lock [this message]
2011-02-28 6:22 ` Zhai, Edwin
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=1298642247.2684.6.camel@scimitar \
--to=josh@openedhand.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox