On Sun, Jul 28, 2019 at 5:52 PM Heinrich Schuchardt <[email protected]> wrote: > > On 7/28/19 11:35 AM, Bin Meng wrote: > > On Sun, Jul 28, 2019 at 5:08 PM Heinrich Schuchardt <[email protected]> > > wrote: > >> > >> On 7/28/19 10:56 AM, Bin Meng wrote: > >>> On Sun, Jul 28, 2019 at 4:33 PM Heinrich Schuchardt <[email protected]> > >>> wrote: > >>>> > >>>> On 7/28/19 9:41 AM, Bin Meng wrote: > >>>>> +Stefan > >>>>> > >>>>> Hi Heinrich, > >>>>> > >>>>> On Sun, Jul 28, 2019 at 2:32 PM Heinrich Schuchardt > >>>>> <[email protected]> wrote: > >>>>>> > >>>>>> > >>>>>> Hello Tom, > >>>>>> > >>>>>> origin/master commit bfe28bc70fc8b192878d6e8b7f7db344091643cf fails to > >>>>>> build conga-qeval20-qa3-e3845 on Debian Buster: > >>>>>> > >>>>> > >>>>> I cannot reproduce it. Did you set CONFIG_BUILD_ROM = y? > >>>> > >>>> My expectation is that if I call 'make > >>>> conga-qeval20-qa3-e3845_defconfig' it sets all necessary configuration > >>>> options to build successfully. This defconfig results in > >>>> > >>>> # CONFIG_BUILD_ROM is not set > >>>> > >>> > >>> Sorry I was not clear. CONFIG_BUILD_ROM should not be set. When it is > >>> unset, it does not touch descriptor.bin. I thought you previously had > >>> it enabled hence binman tried to find descriptor.bin. > >>> > >>>> Setting CONFIG_BUILD_ROM=y does not solve the problem. > >>>> > >>>> Did you delete all *.bin files before testing? 'make mrproper' does not > >>>> delete *.bin from the build path. Shouldn't it remove generated *.bin? > >>>> > >>> > >>> *.bin in the board directory is kept there because it's not generated > >>> during U-Boot build. > >>> > >>> I still cannot reproduce this. Not sure what's wrong. > >> > >> In my .bashrc I had export BUILD_ROM=y. In earlier releases > >> qemu-x86_defconfig needed this. If I unset this variable the build works > >> on my local system. Thanks for the hint. > >> > > > > Good to hear. > > > >> This still leaves me with the question what is broken on Gitlab (Travis > >> CI ran fine). > >> > > > > I tried to look at the Gitlab log but when I opened > > https://gitlab.denx.de/u-boot/custodians/u-boot-efi/-/jobs/2155, it > > gave me 404. > > To me was shown only when logged on. >
I have been logged on but still cannot see that. I suspect that's because I am not a member of the u-boot-efi git repo. > I append the log below. > > Best regards > > Heinrich > > > > U-Boot > Custodians > EFI U-Boot Custodian TreeEFI U-Boot Custodian Tree > Jobs > #2155 > > failed Job #2155 triggered 11 hours ago by Heinrich Schuchardt's avatar > Heinrich Schuchardt > > > Running with gitlab-runner 12.0.1 (0e5417a3) > on konsulko-bootbake G37FKVsV > Using Docker executor with image > trini/u-boot-gitlab-ci-runner:xenial-20190720-24Jul2019 ... > Pulling docker image > trini/u-boot-gitlab-ci-runner:xenial-20190720-24Jul2019 ... > Using docker image > sha256:5b1c8d4e86ff4494305883637941b882b324282a91d57d6157d1140e7a67d9d3 > for trini/u-boot-gitlab-ci-runner:xenial-20190720-24Jul2019 ... > Running on runner-G37FKVsV-project-553-concurrent-0 via bootbake... > Fetching changes... > Reinitialized existing Git repository in > /builds/u-boot/custodians/u-boot-efi/.git/ > Checking out 5bab6711 as efi-2019-10... > Removing boards.cfg > Removing tools/binman/cbfs_util.pyc > Removing tools/binman/cmdline.pyc > Removing tools/binman/control.pyc > Removing tools/binman/elf.pyc > Removing tools/binman/entry.pyc > Removing tools/binman/etype/__init__.pyc > Removing tools/binman/etype/blob.pyc > Removing tools/binman/etype/blob_dtb.pyc > Removing tools/binman/etype/fdtmap.pyc > Removing tools/binman/etype/image_header.pyc > Removing tools/binman/etype/powerpc_mpc85xx_bootpg_resetvec.pyc > Removing tools/binman/etype/section.pyc > Removing tools/binman/etype/u_boot_dtb_with_ucode.pyc > Removing tools/binman/etype/u_boot_with_ucode_ptr.pyc > Removing tools/binman/image.pyc > Removing tools/binman/state.pyc > Removing tools/buildman/board.pyc > Removing tools/buildman/bsettings.pyc > Removing tools/buildman/builder.pyc > Removing tools/buildman/builderthread.pyc > Removing tools/buildman/cmdline.pyc > Removing tools/buildman/control.pyc > Removing tools/buildman/kconfiglib.pyc > Removing tools/buildman/toolchain.pyc > Removing tools/concurrencytest/concurrencytest.pyc > Removing tools/dtoc/fdt.pyc > Removing tools/dtoc/fdt_util.pyc > Removing tools/patman/checkpatch.pyc > Removing tools/patman/command.pyc > Removing tools/patman/commit.pyc > Removing tools/patman/cros_subprocess.pyc > Removing tools/patman/get_maintainer.pyc > Removing tools/patman/gitutil.pyc > Removing tools/patman/patchstream.pyc > Removing tools/patman/series.pyc > Removing tools/patman/settings.pyc > Removing tools/patman/terminal.pyc > Removing tools/patman/test_util.pyc > Removing tools/patman/tools.pyc > Removing tools/patman/tout.pyc > > Skipping Git submodules setup > $ ret=0; ./tools/buildman/buildman -P -E -x arm,powerpc || ret=$?; if [[ > $ret -ne 0 && $ret -ne 129 ]]; then ./tools/buildman/buildman -sdeP; > exit $ret; fi; > Building current source for 167 boards (24 threads, 1 job per thread) > > Starting build... > 0 0 0 /167 (starting) > > > 1 0 0 /167 1:06:16 : vct_platinumavc > > x86: + conga-qeval20-qa3-e3845-internal-uart > +Compiler aborting due to parser-detected syntax error(s) > +board/congatec/conga-qeval20-qa3-e3845/dsdt.asl.tmp 731: This is weird. What IASL version did that use? I am using: $ iasl -v Intel ACPI Component Architecture ASL+ Optimizing Compiler version 20160108-64 Copyright (c) 2000 - 2016 Intel Corporation Regards, Bin Regards, Bin _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
