From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "Barbier, Renaud" <renaud.barbier@abaco.com>,
"barebox@lists.infradead.org" <barebox@lists.infradead.org>,
Roland Hieber <rhi@pengutronix.de>
Subject: Re: bareboxenv-target
Date: Tue, 23 Mar 2021 16:47:37 +0100 [thread overview]
Message-ID: <4cc07830-1073-b638-6929-10c677243f05@pengutronix.de> (raw)
In-Reply-To: <MN2PR16MB3135E3998BF7EA4489AE059891649@MN2PR16MB3135.namprd16.prod.outlook.com>
Hello Renaud,
On 23.03.21 15:44, Barbier, Renaud wrote:
>>> Could it it be related to how our toolchain got build?
>>
>> Just ran into the same issue. Cause is as Roland describes the lack of --sysroot
>> as default and that it comes in via $CC, which Kbuild doesn't expect.
>>
>> I guess this would break building kernel host tools too or how do they solve it?
>>>
>>> Not working either:
>>> [renaud@ediowsrv01]$ make tools/leds
>>> DESCEND leds
>>> arm-oe-linux-gnueabi-gcc -Wall -Wextra -g -I../../include/uapi -o uledmon uledmon.c
>>> uledmon.c:14:10: fatal error: fcntl.h: No such file or directory
>>> 14 | #include <fcntl.h>
>>> | ^~~~~~~~~
Thanks for trying it out. Well, this is a general incompatibility of the SDK's environment
setup script with Kbuild then. I am wondering why they decided on not having a default
--sysroot. Raising the issue upstream could shed some light on this and perhaps result
in a fix. I don't think there is anything to fix here at the barebox side.
FTR: we use meta-ptx extensively and AFAIK we haven't run into this issue. It only
popped up when using the SDK build, so bitbake seems to do the right thing in that case.
Cheers,
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-03-23 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 11:09 bareboxenv-target Barbier, Renaud
2020-11-02 13:13 ` bareboxenv-target Roland Hieber
2020-11-04 10:05 ` bareboxenv-target Barbier, Renaud
2020-11-06 9:55 ` bareboxenv-target Barbier, Renaud
2020-11-06 12:25 ` bareboxenv-target Roland Hieber
2020-11-06 13:12 ` bareboxenv-target Barbier, Renaud
2020-11-06 12:06 ` bareboxenv-target Barbier, Renaud
2020-11-06 12:31 ` bareboxenv-target Roland Hieber
2021-03-23 12:33 ` bareboxenv-target Ahmad Fatoum
2021-03-23 14:44 ` bareboxenv-target Barbier, Renaud
2021-03-23 15:47 ` Ahmad Fatoum [this message]
2021-05-31 17:10 ` bareboxenv-target Ahmad Fatoum
-- strict thread matches above, loose matches on Subject: below --
2014-11-14 18:44 bareboxenv-target Balasa, Bogdan
2014-11-15 17:54 ` bareboxenv-target Sascha Hauer
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=4cc07830-1073-b638-6929-10c677243f05@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=renaud.barbier@abaco.com \
--cc=rhi@pengutronix.de \
/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