Skip to contentSkip to conversation

Incorrect startup warning on ARM targets

DISCUSSION Gary Thomas 2 participants 3 messages May 3, 2011

lore
Share & tools
lore
#0 lore raw

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.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 11 lines · Gary Thomas

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.

Quoted 3 lines

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

Quoted 10 lines
Signature · 9 lines
-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Signature · 1 line
-Khem
#2 lore raw
Quoted 12 lines · Khem Raj
Quoted 11 lines · Gary Thomas

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.

Quoted 6 lines
Quoted 3 lines

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.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------