From: Ross Burton <Ross.Burton@arm.com>
To: "raj.khem@gmail.com" <raj.khem@gmail.com>
Cc: "Bartosz Golaszewski" <brgl@bgdev.pl>,
"Eilís Ní Fhlannagáin" <elizabeth.flanagan@huawei.com>,
"Jon Mason" <jdmason@kudzu.us>, "Jon Mason" <Jon.Mason@arm.com>,
"Naveen Saini" <naveen.kumar.saini@intel.com>,
"Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>,
openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-zephyr] build broken with current oe-core master
Date: Fri, 22 Jul 2022 14:30:27 +0000 [thread overview]
Message-ID: <CB11164A-DF98-44E2-B0BF-265797DB930A@arm.com> (raw)
In-Reply-To: <CAMKF1srvQZDtjtQnQPTaT2PNYZCaChCY9S9pBNVQV5ybqAjVkw@mail.gmail.com>
On 22 Jul 2022, at 15:28, Khem Raj via lists.openembedded.org <raj.khem=gmail.com@lists.openembedded.org> wrote:
>
> On Fri, Jul 22, 2022 at 6:36 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>>
>> On Thu, Jul 21, 2022 at 3:52 PM Khem Raj <raj.khem@gmail.com> wrote:
>>>
>>> I don’t see config.log for Libstdc++ folder in there
>>> Can you see why that’s missing ?
>>>
>>
>> I was missing because I misunderstood you - you were probably asking
>> for the config.log *with* Jon's patch applied.
>>
>> Here's the log: https://controlc.com/4544edd8
>
> right, so I can see that its checking for fcnt function on system
> where it should not, your toolchain
> is using newlib and I am not sure what Jon's build is using for
> zephyr, I guess it could be pure baremetal
> if so, then perhaps we have a place to look into.
>
> Jon, whats TCLIBC set to in zephyr's case.
Our CI has the following workaround for a problem that we’ve not managed to root-cause so far:
EXTRA_OECONF:append:pn-gcc-runtime = " ac_cv_func_fcntl=no ac_cv_func_getexecname=no”
Ross
next prev parent reply other threads:[~2022-07-22 14:30 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
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 [this message]
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=CB11164A-DF98-44E2-B0BF-265797DB930A@arm.com \
--to=ross.burton@arm.com \
--cc=Jon.Mason@arm.com \
--cc=brgl@bgdev.pl \
--cc=elizabeth.flanagan@huawei.com \
--cc=jdmason@kudzu.us \
--cc=naveen.kumar.saini@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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