From: mfumita@electromag.com.au
To: openembedded-core@lists.openembedded.org
Subject: Re: libstdc++ honister -> kirkstone
Date: Tue, 05 Jul 2022 21:01:13 -0700 [thread overview]
Message-ID: <28194.1657080073438546558@lists.openembedded.org> (raw)
In-Reply-To: <fbe2ba5d-f82c-ea57-a00d-4e0ff1b9586f@electromag.com.au>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
Hello there,
It isn't due to EOVERFLOW but make_file_type function in libstdc++-v3\src\filesystem\ops-common.h always returns file_type::unknown.
It's because _GLIBCXX_HAVE_S_ISREG isn't defined.
I found HAVE_S_ISREG at libstdc++-v3/config.h isn't set properly.
It's caused by a configure failure below to tell if S_ISREG exists on the target.
gcc/arm-emit-linux-gnueabi/11.3.0/ld: error: tmp-glibc/work/cortexa9t2hf-neon-emit-linux-gnueabi/gcc-runtime/11.3.0-r0/dummylib/libstdc++.so: file is empty
collect2: error: ld returned 1 exit status
configure:15686: $? = 1
It complains dummylib/libstdc++.so is empty, configure failed then wrongly considered S_ISREG doesn't exist.
This seems related to the following commit.
https://github.com/openembedded/openembedded-core/commit/34b0edb0d3120c32063ff7e3dd52be20d60401d5
Reverting this commit rectifies this issue but not sure what's the proper fix?
Any help appreciated.
Thanks,
Mori
[-- Attachment #2: Type: text/html, Size: 1198 bytes --]
next prev parent reply other threads:[~2022-07-06 4:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 1:14 libstdc++ honister -> kirkstone Phil Reid
2022-07-06 4:01 ` mfumita [this message]
2022-07-08 13:05 ` [OE-core] " Richard Purdie
2022-07-12 5:23 ` Phil Reid
2022-07-13 22:13 ` Richard Purdie
2022-07-14 8:25 ` Phil Reid
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=28194.1657080073438546558@lists.openembedded.org \
--to=mfumita@electromag.com.au \
--cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.