public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Jon Mason <jdmason@kudzu.us>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "Patches and discussions about the oe-core layer"
	<openembedded-core@lists.openembedded.org>,
	openembedded-devel <openembedded-devel@lists.openembedded.org>,
	"Jon Mason" <jon.mason@arm.com>,
	"Eilís Ní Fhlannagáin" <elizabeth.flanagan@huawei.com>,
	"Naveen Saini" <naveen.kumar.saini@intel.com>
Subject: Re: [meta-zephyr] build broken with current oe-core master
Date: Mon, 18 Jul 2022 14:49:13 -0400	[thread overview]
Message-ID: <YtWrKcR6y1jWSFtC@kudzu.us> (raw)
In-Reply-To: <CAMRc=McXfAzcUrdTLWsHHEo8DyUwU1gUuFTBALwXpJCuA0CoEA@mail.gmail.com>

On Mon, Jul 18, 2022 at 08:31:39PM +0200, Bartosz Golaszewski wrote:
> Hi!
> 
> It seems that the zephyr build is currently broken with master (and
> master-next) for meta-zephyr samples:
> 
> Build Configuration:
> BB_VERSION           = "2.0.1"
> BUILD_SYS            = "x86_64-linux"
> NATIVELSBSTRING      = "universal"
> TARGET_SYS           = "arm-yocto-eabi"
> MACHINE              = "arduino-nano-33-ble"
> DISTRO               = "zephyr"
> DISTRO_VERSION       = "1.0"
> TUNE_FEATURES        = "armv7m cortexm4"
> TARGET_FPU           = "soft"
> meta
> meta-poky            = "HEAD:67b9303d72c14d2aedb3f0313cb7b27dfb1499d3"
> meta-zephyr-core
> meta-zephyr-bsp      = "master:6d184ce6b66349a87dc114c7ab59d0dd3bf92785"
> meta-oe
> meta-python          = "master:cb7d3afba838f159a5df4ef5091dba8e770159a8"
> 
> Initialising tasks: 100%
> |#########################################################################################################|
> Time: 0:00:01
> Sstate summary: Wanted 101 Local 66 Mirrors 0 Missed 35 Current 98
> (65% match, 82% complete)
> NOTE: Executing Tasks
> ERROR: gcc-runtime-12.1.0-r0 do_configure:
> ExecutionError('/home/brgl/workspace/zephyr-yocto/build/tmp-newlib/work/armv7m-yocto-eabi/gcc-runtime/12.1.0-r0/temp/run.do_configure.2702410',
> 1, None, None)
> ERROR: Logfile of failure stored in:
> /home/brgl/workspace/zephyr-yocto/build/tmp-newlib/work/armv7m-yocto-eabi/gcc-runtime/12.1.0-r0/temp/log.do_configure.2702410
> Log data follows:
> | DEBUG: Executing python function extend_recipe_sysroot
> | NOTE: Direct dependencies are
> ['/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-core/newlib/newlib_4.2.0.bb:do_populate_sysroot',
> '/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/binutils/binutils-cross_2.38.bb:do_populate_sysroot',
> '/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/gcc/gcc-cross_12.1.bb:do_populate_sysroot',
> '/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/gcc/libgcc_12.1.bb:do_populate_sysroot',
> '/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/libtool/libtool-native_2.4.7.bb:do_populate_sysroot',
> '/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/quilt/quilt-native_0.67.bb:do_populate_sysroot',
> '/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-extended/texinfo-dummy-native/texinfo-dummy-native.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-core/zlib/zlib_1.2.12.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/autoconf/autoconf_2.71.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/automake/automake_1.16.5.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/flex/flex_2.6.4.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/patch/patch_2.7.6.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-extended/xz/xz_5.2.5.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-extended/zstd/zstd_1.5.2.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-support/gmp/gmp_6.2.1.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-support/libmpc/libmpc_1.2.1.bb:do_populate_sysroot',
> 'virtual:native:/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-support/mpfr/mpfr_4.1.0.bb:do_populate_sysroot']
> | NOTE: Installed into sysroot: []
> | NOTE: Skipping as already exists in sysroot: ['newlib',
> 'binutils-cross-arm', 'gcc-cross-arm', 'libgcc', 'libtool-native',
> 'quilt-native', 'texinfo-dummy-native', 'zlib-native',
> 'autoconf-native', 'automake-native', 'flex-native',
> 'gnu-config-native', 'patch-native', 'pseudo-native', 'xz-native',
> 'zstd-native', 'gmp-native', 'libmpc-native', 'mpfr-native',
> 'attr-native', 'gettext-minimal-native', 'm4-native']
> | DEBUG: Python function extend_recipe_sysroot finished
> | DEBUG: Executing shell function autotools_preconfigure
> | DEBUG: Shell function autotools_preconfigure finished
> | DEBUG: Executing python function autotools_aclocals
> | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
> 'arm-32', 'arm-eabi', 'common']
> | DEBUG: Python function autotools_aclocals finished
> | DEBUG: Executing python function gcc_multilib_setup
> | DEBUG: Python function gcc_multilib_setup finished
> | DEBUG: Executing python function extract_stashed_builddir
> | DEBUG: sed -e
> 's:^[^/]*/:/home/brgl/workspace/zephyr-yocto/build/tmp-newlib/work/armv7m-yocto-eabi/gcc-runtime/12.1.0-r0/gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/:g'
> /home/brgl/workspace/zephyr-yocto/build/tmp-newlib/sysroots-components/x86_64/gcc-stashed-builddir-arm-yocto-eabi/fixmepath
> | xargs sed -i -e
> 's:FIXMESTAGINGDIRTARGET:/home/brgl/workspace/zephyr-yocto/build/tmp-newlib/work/armv7m-yocto-eabi/gcc-runtime/12.1.0-r0/recipe-sysroot:g;
> s:FIXMESTAGINGDIRHOST:/home/brgl/workspace/zephyr-yocto/build/tmp-newlib/work/armv7m-yocto-eabi/gcc-runtime/12.1.0-r0/recipe-sysroot-native:g'
> -e 's:FIXME_PSEUDO_SYSROOT:/home/brgl/workspace/zephyr-yocto/build/tmp-newlib/sysroots-components/x86_64/pseudo-native:g'
> -e 's:FIXME_HOSTTOOLS_DIR:/home/brgl/workspace/zephyr-yocto/build/tmp-newlib/hosttools:g'
> -e 's:FIXME_PKGDATA_DIR:/home/brgl/workspace/zephyr-yocto/build/tmp-newlib/pkgdata/arduino-nano-33-ble:g'
> -e 's:FIXME_PSEUDO_LOCALSTATEDIR:/home/brgl/workspace/zephyr-yocto/build/tmp-newlib/work/armv7m-yocto-eabi/gcc-runtime/12.1.0-r0/pseudo/:g'
> -e 's:FIXME_LOGFIFO:/home/brgl/workspace/zephyr-yocto/build/tmp-newlib/work/armv7m-yocto-eabi/gcc-runtime/12.1.0-r0/temp/fifo.2702410:g'
> | DEBUG: Python function extract_stashed_builddir finished
> | DEBUG: Executing shell function do_configure
> | /home/brgl/workspace/zephyr-yocto/build/tmp-newlib/work/armv7m-yocto-eabi/gcc-runtime/12.1.0-r0/recipe-sysroot-native/usr/bin/arm-yocto-eabi/../../libexec/arm-yocto-eabi/gcc/arm-yocto-eabi/12.1.0/ld:
> cannot find crt0.o: No such file or directory
> | collect2: error: ld returned 1 exit status
> | WARNING: exit code 1 from a shell command.
> ERROR: Task (/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/gcc/gcc-runtime_12.1.bb:do_configure)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 765 tasks of which 746 didn't need to
> be rerun and 1 failed.
> 
> Summary: 1 task failed:
>   /home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/gcc/gcc-runtime_12.1.bb:do_configure
> Summary: There was 1 ERROR message, returning a non-zero exit code.
> 
> I don't have any ideas but it looks like something related to the machine tune?

I haven't had time to bottom out on the issue, but I was able to
confirm that the patch in OE core that breaks meta-zephyr is

commit 028ecb0c265fa495071cbcca10587c0ba60cf538
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date:   Wed Jul 13 23:12:06 2022 +0100

    gcc-runtime: Fix build when using gold

    If gold is enabled as the default linker, it errors trying to link
    to our dummy library empty file and this turns off things which should
    be present in libstdc++.

    For example, _GLIBCXX_HAVE_S_ISREG isn't defined and HAVE_S_ISREG in
    libstdc++-v3/config.h isn't set properly.

    Instead of just creating an empty file, create an empty elf binary
    instead which addresses the issue.

    (From OE-Core rev: 2070bcd10aa3a05c96c8501c6a8c1e129fb1d440)

    Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

If you revert that, everything is happy.

Thanks,
Jon


> 
> Bart
> 


  reply	other threads:[~2022-07-18 18:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 18:31 [meta-zephyr] build broken with current oe-core master Bartosz Golaszewski
2022-07-18 18:49 ` Jon Mason [this message]
2022-07-18 20:05   ` [oe] " Khem Raj
2022-07-18 22:09     ` Jon Mason
2022-07-19  7:40       ` Bartosz Golaszewski
2022-07-19 12:54         ` Khem Raj
2022-07-19 14:48           ` Bartosz Golaszewski
2022-07-19 14:57             ` Khem Raj
2022-07-20 15:35               ` Bartosz Golaszewski
2022-07-20 15:58                 ` Khem Raj
2022-07-21  8:22                   ` Bartosz Golaszewski
2022-07-21 13:52                     ` Khem Raj
2022-07-22 10:36                       ` Bartosz Golaszewski
2022-07-22 14:28                         ` Khem Raj
2022-07-22 14:30                           ` Ross Burton
2022-07-22 14:31                             ` Khem Raj
2022-07-22 14:34                               ` Khem Raj
2022-07-22 15:54                                 ` Jon Mason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YtWrKcR6y1jWSFtC@kudzu.us \
    --to=jdmason@kudzu.us \
    --cc=brgl@bgdev.pl \
    --cc=elizabeth.flanagan@huawei.com \
    --cc=jon.mason@arm.com \
    --cc=naveen.kumar.saini@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox