* Incorrect startup warning on ARM targets
@ 2011-05-03 22:07 Gary Thomas
2011-05-03 23:12 ` Khem Raj
0 siblings, 1 reply; 3+ messages in thread
From: Gary Thomas @ 2011-05-03 22:07 UTC (permalink / raw)
To: Poky Project
When building for an ARM target, you may see this error:
/proc/sys/vm/mmap_min_addr is not <= 65536. This will cause problems with qemu so please fix the value (as root)
This is a show-stopper; bitbake refuses to run until it's fixed.
However, I don't believe it is useful or required any longer. From
my understanding, it was there in the past because QEMU for ARM didn't
work correctly unless this system parameter was set as indicated. That
was when QEMU was being used during the build to create localization
data. This is no longer being done and QEMU is not used during the
build process.
Perhaps we could eliminate this warning or make it conditional
somehow? As is, asking the user to make a system-wide setting
as root for something that's not necessary seems wrong.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Incorrect startup warning on ARM targets
2011-05-03 22:07 Incorrect startup warning on ARM targets Gary Thomas
@ 2011-05-03 23:12 ` Khem Raj
2011-05-03 23:20 ` Gary Thomas
0 siblings, 1 reply; 3+ messages in thread
From: Khem Raj @ 2011-05-03 23:12 UTC (permalink / raw)
To: Gary Thomas; +Cc: Poky Project
On (03/05/11 16:07), Gary Thomas wrote:
> When building for an ARM target, you may see this error:
> /proc/sys/vm/mmap_min_addr is not <= 65536. This will cause problems with qemu so please fix the value (as root)
>
> This is a show-stopper; bitbake refuses to run until it's fixed.
> However, I don't believe it is useful or required any longer. From
> my understanding, it was there in the past because QEMU for ARM didn't
> work correctly unless this system parameter was set as indicated. That
> was when QEMU was being used during the build to create localization
> data. This is no longer being done and QEMU is not used during the
> build process.
>
> Perhaps we could eliminate this warning or make it conditional
> somehow? As is, asking the user to make a system-wide setting
> as root for something that's not necessary seems wrong.
This warning is taken care of in qemu-native we build. But I think its
already fixed in upstream oe-core
>
> --
> ------------------------------------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> ------------------------------------------------------------
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
--
-Khem
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Incorrect startup warning on ARM targets
2011-05-03 23:12 ` Khem Raj
@ 2011-05-03 23:20 ` Gary Thomas
0 siblings, 0 replies; 3+ messages in thread
From: Gary Thomas @ 2011-05-03 23:20 UTC (permalink / raw)
To: Poky Project
On 05/03/2011 05:12 PM, Khem Raj wrote:
> On (03/05/11 16:07), Gary Thomas wrote:
>> When building for an ARM target, you may see this error:
>> /proc/sys/vm/mmap_min_addr is not<= 65536. This will cause problems with qemu so please fix the value (as root)
>>
>> This is a show-stopper; bitbake refuses to run until it's fixed.
>> However, I don't believe it is useful or required any longer. From
>> my understanding, it was there in the past because QEMU for ARM didn't
>> work correctly unless this system parameter was set as indicated. That
>> was when QEMU was being used during the build to create localization
>> data. This is no longer being done and QEMU is not used during the
>> build process.
>>
>> Perhaps we could eliminate this warning or make it conditional
>> somehow? As is, asking the user to make a system-wide setting
>> as root for something that's not necessary seems wrong.
>
> This warning is taken care of in qemu-native we build. But I think its
> already fixed in upstream oe-core
It's still in the Poky tree (sanity.bbclass) which is what I'm asking about.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-05-03 23:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-03 22:07 Incorrect startup warning on ARM targets Gary Thomas
2011-05-03 23:12 ` Khem Raj
2011-05-03 23:20 ` Gary Thomas
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.