Support: OpenBMC build failed at bmcweb (commit: 029f4aada38f4b041b5a171c2e112a267cee3b7f)

[Patrick Williams]

On Fri, Sep 15, 2023 at 08:09:08AM +0000, Łukasz Przeniosło wrote:
> Hello,
> I am trying to build OpenBMC on an Ubuntu VM:
> 
> lukasz at ce-lp:~/ce/openbmc/build/evb-ast2600$ uname -a
> Linux ce-lp 6.2.0-32-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Mon Aug 14 
> 10:03:50 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
> 
> I have 16 total cores and 20 GB of RAM assigned to this VM. My target is 
> evb-ast2600. My build fails at bmcweb:
> 
> | {standard input}: Assembler messages:
> | {standard input}:8616216: Warning: end of file in string; '"' inserted
> | arm-openbmc-linux-gnueabi-g++: fatal error: Killed signal terminated 
> program cc1plus
> | compilation terminated.
> | ninja: build stopped: subcommand failed.
> | INFO: autodetecting backend as ninja
> | INFO: calculating backend command to run: 
> /home/lukasz/ce/openbmc/build/evb-ast2600/tmp/work/armv7ahf-vfpv4d16-openbmc-linux-gnueabi/bmcweb/1.0+gitAUTOINC+e1bf8bb6a8/recipe-sysroot-native/usr/bin/ninja 
> -j 16 -v
> | WARNING: exit code 1 from a shell command.
> ERROR: Task 
> (/home/lukasz/ce/openbmc/meta-phosphor/recipes-phosphor/interfaces/bmcweb_git.bb:do_compile) 
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 5292 tasks of which 704 didn't need to be 
> rerun and 1 failed.
> 
> Summary: 1 task failed:
>    
> /home/lukasz/ce/openbmc/meta-phosphor/recipes-phosphor/interfaces/bmcweb_git.bb:do_compile
> Summary: There were 2 WARNING messages.
> Summary: There was 1 ERROR message, returning a non-zero exit code.
> 
> Here is the complete output: https://pastebin.com/yGRDT477
> 
> My gcc version:
> 
> lukasz at ce-lp:~/ce/openbmc/build/evb-ast2600$ gcc --version
> gcc (Ubuntu 12.3.0-1ubuntu1~23.04) 12.3.0
> 
> Before building I have installed all necessary packages via:
> 
> sudo apt install git python3-distutils gcc g++ make file wget gawk 
> diffstat bzip2 cpio chrpath zstd lz4 bzip2
> 
> I cannot figure out what I am missing. I would appreciate all help and 
> support, thank you!
> 
> --
> Łukasz Przeniosło

Two thoughts:

1. You should be using GCC-13 for our repositories now.

2. The symptoms of unexpected EOF from the assembler are generally an
   indication that another GCC process failed due to the kernel OOM
   killer.  You said you have 20GB of RAM, which is decent, but the
   ratio of cores to RAM is barely above 1GB.  You might want to use
   `ninja -j6` to limit the number of parallel jobs that Ninja kicks
   off.

(At this point you should probably `ninja clean` before retrying).

-- 
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20230915/261ece22/attachment.sig>