Actions
Forum Thread Details
  • Replies 1 reply
  • Subscribers 275 subscribers
  • Views 1625 views
  • Users 0 members are here
Related

Petalinux 2020.1 build error

jorikdima

Hi

 

I am trying to build an image using petalinux scripts for UZ7EV board (make_uz7ev_evcc.sh script) and have some issues (I use CentOS7 + Vitis/Vivado 2020.1 if that is important). Some piece of build log looks like:

NOTE: recipe btrfs-tools-5.2.2-r0: task do_rm_work: Started

NOTE: recipe socat-1.7.3.3-r0: task do_rm_work: Started

NOTE: Running task 3523 of 4991 (/projects/BCM4777_ext/work/dmitry/saturnas/avnet/repos/petalinux/projects/uz7ev_evcc_2020_1/components/yocto/layers/core/meta/recipes-graphics/cantarell-fonts/cantarell-fonts_git.bb:do_rm_work)

NOTE: recipe grep-3.3-r0: task do_rm_work: Started

ERROR: libvcu-xlnx-1.0.0-xilinx-v2020.1+gitAUTOINC+8ad2b1323b-r0 do_compile: oe_runmake failed

ERROR: libvcu-xlnx-1.0.0-xilinx-v2020.1+gitAUTOINC+8ad2b1323b-r0 do_compile: Execution of '/tmp/uz7ev_evcc_2020_1-2020.11.01-15.58.12-rkv/work/zynqmp-xilinx-linux/libvcu-xlnx/1.0.0-xilinx-v2020.1+gitAUTOINC+8ad2b1323b-r0/temp/run.do_compile.334068' failed with exit code 1:

LD bin/liballegro_encode.so

sorry - this program has been built without plugin support

sorry - this program has been built without plugin support

make: *** [base.mk:48: bin/liballegro_encode.a] Error 1

make: *** Waiting for unfinished jobs....

make: *** [base.mk:48: bin/liballegro_decode.a] Error 1

LD bin/liballegro_decode.so

WARNING: /tmp/uz7ev_evcc_2020_1-2020.11.01-15.58.12-rkv/work/zynqmp-xilinx-linux/libvcu-xlnx/1.0.0-xilinx-v2020.1+gitAUTOINC+8ad2b1323b-r0/temp/run.do_compile.334068:1 exit 1 from 'exit 1'

 

 

ERROR: Logfile of failure stored in: /tmp/uz7ev_evcc_2020_1-2020.11.01-15.58.12-rkv/work/zynqmp-xilinx-linux/libvcu-xlnx/1.0.0-xilinx-v2020.1+gitAUTOINC+8ad2b1323b-r0/temp/log.do_compile.334068

NOTE: recipe libvcu-xlnx-1.0.0-xilinx-v2020.1+gitAUTOINC+8ad2b1323b-r0: task do_compile: Failed

NOTE: recipe which-2.21-r3: task do_rm_work: Started

NOTE: Running task 3537 of 4991 (/projects/BCM4777_ext/work/dmitry/saturnas/avnet/repos/petalinux/projects/uz7ev_evcc_2020_1/components/yocto/layers/meta-xilinx/meta-xilinx-bsp/recipes-multimedia/vcu/vcu-firmware.bb:do_rm_work)

ERROR: Task (/projects/BCM4777_ext/work/dmitry/saturnas/avnet/repos/petalinux/projects/uz7ev_evcc_2020_1/components/yocto/layers/meta-xilinx/meta-xilinx-bsp/recipes-multimedia/vcu/libvcu-xlnx.bb:do_compile) failed with exit code '1'

NOTE: recipe bc-1.07.1-r0: task do_rm_work: Started

NOTE: recipe glib-2.0-1_2.60.7-r0: task do_rm_work: Started

NOTE: recipe shared-mime-info-1.10-r0: task do_rm_work: Started

 

And then later:

 

ERROR: busybox-1.31.0-r0 do_configure: oe_runmake failed

ERROR: busybox-1.31.0-r0 do_configure: Execution of '/tmp/uz7ev_evcc_2020_1-2020.11.01-15.58.12-rkv/work/aarch64-xilinx-linux/busybox/1.31.0-r0/temp/run.do_configure.292287' failed with exit code 1:

 

And in the end:

 

GEN     networking/Config.in

  GEN     networking/udhcp/Kbuild

  GEN     networking/udhcp/Config.in

  GEN     networking/libiproute/Kbuild

  GEN     scripts/Kbuild

mkdir -p include

make -f scripts/Makefile.build obj=scripts/kconfig oldconfig

make[1]: *** Cannot allocate memory.  Stop.

make: *** [Makefile:445: oldconfig] Error 2

+ die 'oe_runmake failed'

+ bbfatal_log 'oe_runmake failed'

+ '[' -p /tmp/uz7ev_evcc_2020_1-2020.11.01-15.58.12-rkv/work/aarch64-xilinx-linux/busybox/1.31.0-r0/temp/fifo.292287 ']'

+ printf '%b\0' 'bbfatal_log oe_runmake failed'

+ exit 1

+ bb_exit_handler

+ ret=1

+ case $ret in

+ case $BASH_VERSION in

+ echo 'WARNING: /tmp/uz7ev_evcc_2020_1-2020.11.01-15.58.12-rkv/work/aarch64-xilinx-linux/busybox/1.31.0-r0/temp/run.do_configure.292287:1 exit 1 from '\''oe_runmake oldconfig'\'''

WARNING: /tmp/uz7ev_evcc_2020_1-2020.11.01-15.58.12-rkv/work/aarch64-xilinx-linux/busybox/1.31.0-r0/temp/run.do_configure.292287:1 exit 1 from 'oe_runmake oldconfig'

+ exit 1

 

 

ERROR: Logfile of failure stored in: /tmp/uz7ev_evcc_2020_1-2020.11.01-15.58.12-rkv/work/aarch64-xilinx-linux/busybox/1.31.0-r0/temp/log.do_configure.292287

NOTE: recipe busybox-1.31.0-r0: task do_configure: Failed

ERROR: Task (/projects/BCM4777_ext/work/dmitry/saturnas/avnet/repos/petalinux/projects/uz7ev_evcc_2020_1/components/yocto/layers/core/meta/recipes-core/busybox/busybox_1.31.0.bb:do_configure) failed with exit code '1'

NOTE: Tasks Summary: Attempted 3538 tasks of which 3095 didn't need to be rerun and 2 failed.

ERROR: Failed to build avnet-image-minimal

 

 

I use the latest 2020.1 branch from GIT. I know it might be raw yet, but is it a known issue or am I doing something wrong (though I basically just call the script)?

 

Thank you

  • Hi there,

     

    Thank you for posting the OS version.  That was going to be my first question.

    While the tools should support CentOS 7.4. 7.5, 7.6 we only officially test our scripting under Ubuntu 18.04.02 at this time. 18.04.1 LTS, 18.04.2 LTS are officially supported by the Xilinx tools and I think one team member is still on 18.04.01 - but that is not where the tags will be built from.

    https://www.xilinx.com/html_docs/xilinx2020_1/vitis_doc/aqm1532064088764.html

     

    We also only support BASH, which can be seen from our VirtualBox installation documentation.  You can ignore the VM portions and take a look at the OS configuration sections and translate that over to CentOS, or the more painful option since you are setup with CentOS, use Ubuntu.

    Here is a link to that document: http://avnet.me/vm_install

     

    Just off the top of my head, I have seen similar strange things with our build scripting when you use DASH instead of BASH.  I am not sure what the default is for Cent.  Check that and see if that help you.

     

    In Ubuntu, you would type:
    sudo dpkg-reconfigure dash

    Then select "no"

    image

    ** Note that this reconfigure is different than just assigning a new shell using something like chsh and the above command is the one that works under Ubuntu

    This link might also help, there are solutions for switching without using dpkg-reconfigure for OS that are not Ubuntu: https://unix.stackexchange.com/questions/442510/how-to-use-bash-for-sh-in-ubuntu

     

    We are planning Tags for this week and have some final changes.  Overall, the branch should be working, but you are correct that we are not tagged yet and we are still making small and critical changes.

     

    --Dan