Re:Re: OpenBMC compile failed issue（urgency）

[Roy Zhang]

Hello Patrick,


1.below is my build machine infor ：
bmc at docker:/home/openbmc/build/mtjade/conf$ uname -r 
5.4.196-1.el7.elrepo.x86_64
bmc at docker:/home/openbmc/build/mtjade/conf$ uname -a
Linux docker 5.4.196-1.el7.elrepo.x86_64 #1 SMP Tue May 24 12:49:20 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux
bmc at docker:/home/openbmc/build/mtjade/conf$ 


2. I just follow the opebmc build steps to build the image “https://github.com/openbmc/openbmc”.




Roy

发件人：Patrick Williams <patrick at stwcx.xyz>
发送日期：2022-08-11 02:27:11
收件人：Roy Zhang <roy.zhang at hj-micro.com>
抄送人：openbmc at lists.ozlabs.org
主题：Re: OpenBMC compile failed issue（urgency）>On Tue, Aug 09, 2022 at 04:59:30PM +0800, Roy Zhang wrote:
>> Hello，
>> 
>> 
>> when i compile the  openbmc image for "evb-ast2600", it compiled failed as below error :
>
>> Detail compile log as below:
>> bmc at docker:/home/openbmc/build/evb-ast2600$ cat /home/openbmc/build/evb-ast2600/tmp/work/armv7ahf-vfpv4d16-openbmc-linux-gnueabi/glib-2.0/1_2.72.3-r0/build/meson-logs/meson-log.txt
>...
>> ../glib-2.72.3/meson.build:1:0: ERROR: Executables created by c compiler arm-openbmc-linux-gnueabi-gcc -march=armv7-a -mfpu=vfpv4-d16 -mfloat-abi=hard -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/openbmc/build/evb-ast2600/tmp/work/armv7ahf-vfpv4d16-openbmc-linux-gnueabi/glib-2.0/1_2.72.3-r0/recipe-sysroot are not runnable.
>
>> | NOTE: Executing meson -Dgtk_doc=false -Ddtrace=false -Dfam=false -Dsystemtap=false -Db_lto=true -Dlibmount=enabled -Dman=false -Dselinux=disabled -Dinstalled_tests=false --cross-file=/home/openbmc/meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common-linux --cross-file=/home/openbmc/meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common-glibc --cross-file=/home/openbmc/meta/recipes-core/glib-2.0/glib-2.0/meson.cross.d/common...
>> | qemu-arm: Unable to reserve 0xffff0000 bytes of virtual address space at 0x1000 (Success) for use as guest address space (check your virtual memory ulimit setting, min_mmap_addr or reserve less using -R option)
>
>We certainly regularly build systemd in CI.  I think there'd be a pretty
>big uproar if master were completely broken, so I highly suspect this is
>something with your environment.
>
>It looks like you're building inside Docker on an x86_64 machine, but
>somehow qemu-arm is being invoked?  Do you have any idea where this
>qemu-arm is coming from?
>
>Can you fully describe the environment you've set up for doing this
>build?  If you're running inside a virtual machine or container
>it might be that you've not allocated enough memory to the container,
>which can cause it to report non-obvious compile failures.
>
>-- 
>Patrick Williams




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20220811/7d7911eb/attachment.htm>