Re: [meta-zephyr] build broken with current oe-core master


Bartosz Golaszewski
 

On Wed, Jul 20, 2022 at 5:59 PM Khem Raj <raj.khem@...> wrote:



On Wed, Jul 20, 2022 at 11:35 AM Bartosz Golaszewski <brgl@...> wrote:

On Tue, Jul 19, 2022 at 4:58 PM Khem Raj <raj.khem@...> wrote:

On Tue, Jul 19, 2022 at 10:48 AM Bartosz Golaszewski <brgl@...> wrote:

On Tue, Jul 19, 2022 at 2:54 PM Khem Raj <raj.khem@...> wrote:



On Tue, Jul 19, 2022 at 3:40 AM Bartosz Golaszewski <brgl@...> wrote:

On Tue, Jul 19, 2022 at 12:10 AM Jon Mason <jdmason@...> wrote:

On Mon, Jul 18, 2022 at 4:06 PM Khem Raj <raj.khem@...> wrote:

Can you try something like this

diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc
b/meta/recipes-devtools/gcc/gcc-runtime.inc
index 5d74e4494d..61d5bf6058 100644
--- a/meta/recipes-devtools/gcc/gcc-runtime.inc
+++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
@@ -68,8 +68,7 @@ do_configure () {
# libstdc++ isn't built yet so CXX would error not able to find it
which breaks stdc++'s configure
# tests. Create a dummy empty lib for the purposes of configure.
mkdir -p ${WORKDIR}/dummylib
- touch ${WORKDIR}/dummylib/dummylib.c
- ${CC} ${WORKDIR}/dummylib/dummylib.c -shared -o
${WORKDIR}/dummylib/libstdc++.so
+ ${CC} -nostartfiles -shared -x c /dev/null -o
${WORKDIR}/dummylib/libstdc++.so
for d in libgcc ${RUNTIMETARGET}; do
echo "Configuring $d"
rm -rf ${B}/${TARGET_SYS}/$d/


and see if it helps ?
That appears to work for the 2 zephyr machines in meta-arm
This still fails for arduino nano 33 ble:

| checking for dirent.h... no
| checking sys/statvfs.h usability... no
| checking sys/statvfs.h presence... no
| checking for sys/statvfs.h... no
| checking utime.h usability... yes
| checking utime.h presence... yes
| checking for utime.h... yes
| checking whether to build Filesystem TS support... no
| checking for struct dirent.d_type... no
| checking for realpath... no
| checking for utimensat... no
| checking for utime... no
| checking for lstat... no
| checking for struct stat.st_mtim.tv_nsec... yes
| checking for fchmod... yes
| checking for fchmodat... yes
| checking for sendfile that can copy files... no
| checking for link... yes
| checking for readlink... yes
| checking for symlink... yes
| checking for truncate... yes
| checking for fdopendir... no
| checking for dirfd... no
| checking for unlinkat... yes
| checking __sync extensions... yes
| checking link.h usability... no
| checking link.h presence... no
| checking for link.h... no
| checking for fcntl... configure: error: Link tests are not allowed
after GCC_NO_EXECUTABLES.


Can you post config.log from this component
Here you go: https://pastebin.com/6KMD9PhX
this one has succeeded. I guess there are multiple config.log files in
your build tree. Perhaps the one which shows exit 1 at the end is one
I am interested in.


Bart
I don't see any config.h that would fail and I just ran a clean build.

Not config.h but config.log
Sorry, the heatwave is getting to me.

Still with config.log:

When I run this from the gcc-runtime's workdir:

$ find | grep config.log$ | xargs tail -n1
==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/intl/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/arm-yocto-eabi/libgcc/config.log
<==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/libcody/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/fixincludes/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/lto-plugin/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/gcc/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/libbacktrace/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/libcpp/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/build-x86_64-linux/fixincludes/config.log
<==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/build-x86_64-linux/libcpp/config.log
<==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/build-x86_64-linux/libiberty/config.log
<==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/libcc1/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/c++tools/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/libdecnumber/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/config.log <==
configure: exit 0

==> ./gcc-12.1.0/build.arm-yocto-eabi.arm-yocto-eabi/libiberty/config.log <==
configure: exit 0

There's no log indicating a failure.

Bart

Join openembedded-devel@lists.openembedded.org to automatically receive all group messages.