From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Sunil Kumar Dora <sunilkumar.dora@blackfigtech.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [Question] -- Inquiry: GCC's -Wpoison-system-directories in Buildroot
Date: Mon, 09 Jun 2025 20:55:26 +0300 [thread overview]
Message-ID: <87bjqwx0j5.fsf@tarshish> (raw)
In-Reply-To: <MAZPR01MB837141FB4F42F5F5EA84F1F29B6BA@MAZPR01MB8371.INDPRD01.PROD.OUTLOOK.COM> (Sunil Kumar Dora's message of "Mon, 9 Jun 2025 17:35:41 +0000")
Hi Sunil Kumar,
On Mon, Jun 09 2025, Sunil Kumar Dora wrote:
> I noticed that GCC once had a `-Wpoison-system-directories` flag to
> warn about unsafe system include paths, but it seems absent in modern
> GCC. Does Buildroot apply any patches to handle this case (e.g.,
> preventing accidental mixing of system and local headers)? If not, is
> there a recommended alternative for embedded builds?
This is a binutils patch that Buildroot applies to its toolchaind:
https://gitlab.com/buildroot.org/buildroot/-/blob/master/package/binutils/2.44/0002-poison-system-directories.patch
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-06-09 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 17:35 [Buildroot] [Question] -- Inquiry: GCC's -Wpoison-system-directories in Buildroot Sunil Kumar Dora
2025-06-09 17:55 ` Baruch Siach via buildroot [this message]
2025-06-10 2:57 ` [Buildroot] EXTERNAL-Re: " Sunil Kumar Dora
2025-06-16 19:00 ` Arnout Vandecappelle via buildroot
2025-06-17 15:28 ` Sunil Kumar Dora
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=87bjqwx0j5.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=sunilkumar.dora@blackfigtech.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