* [Buildroot] [Question] -- Inquiry: GCC's -Wpoison-system-directories in Buildroot
@ 2025-06-09 17:35 Sunil Kumar Dora
2025-06-09 17:55 ` Baruch Siach via buildroot
0 siblings, 1 reply; 5+ messages in thread
From: Sunil Kumar Dora @ 2025-06-09 17:35 UTC (permalink / raw)
To: buildroot@buildroot.org
[-- Attachment #1.1: Type: text/plain, Size: 382 bytes --]
Hi Buildroot developers,
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?
Thanks,
Sunil Dora
[-- Attachment #1.2: Type: text/html, Size: 2545 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Buildroot] [Question] -- Inquiry: GCC's -Wpoison-system-directories in Buildroot
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
2025-06-10 2:57 ` [Buildroot] EXTERNAL-Re: " Sunil Kumar Dora
0 siblings, 1 reply; 5+ messages in thread
From: Baruch Siach via buildroot @ 2025-06-09 17:55 UTC (permalink / raw)
To: Sunil Kumar Dora; +Cc: buildroot@buildroot.org
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Buildroot] EXTERNAL-Re: [Question] -- Inquiry: GCC's -Wpoison-system-directories in Buildroot
2025-06-09 17:55 ` Baruch Siach via buildroot
@ 2025-06-10 2:57 ` Sunil Kumar Dora
2025-06-16 19:00 ` Arnout Vandecappelle via buildroot
0 siblings, 1 reply; 5+ messages in thread
From: Sunil Kumar Dora @ 2025-06-10 2:57 UTC (permalink / raw)
To: Baruch Siach; +Cc: buildroot@buildroot.org
[-- Attachment #1.1: Type: text/plain, Size: 3850 bytes --]
Thank you, Baruch for the update.
The current poison-system-directories patch in Binutils effectively blocks unsafe library paths (via -L flags), but cross-compilation safety also depends on preventing accidental use of host headers (via -I flags). Since Buildroot doesn’t patch GCC to warn about -I paths to directories like /usr/include, this leaves a potential gap:
Risk: Projects might still pick up host headers during compilation, leading to subtle breaks.
Comparison: Yocto addresses this by patching both GCC (for -I) and Binutils (for -L).
Questions:
Is this intentional (e.g., deemed unnecessary for typical Buildroot use cases)?
Would a GCC patch for -I paths align with Buildroot’s goals?
Am I missing any existing mechanisms (e.g., environment variables, wrapper scripts) that mitigate this?
Thanks,
Sunil Dora
________________________________
From: buildroot <buildroot-bounces@buildroot.org> on behalf of Baruch Siach via buildroot <buildroot@buildroot.org>
Sent: Monday, June 9, 2025 11:25 PM
To: Sunil Kumar Dora <sunilkumar.dora@blackfigtech.com>
Cc: buildroot@buildroot.org <buildroot@buildroot.org>
Subject: EXTERNAL-Re: [Buildroot] [Question] -- Inquiry: GCC's -Wpoison-system-directories in Buildroot
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
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://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2Fbuildroot.org%2Fbuildroot%2F-%2Fblob%2Fmaster%2Fpackage%2Fbinutils%2F2.44%2F0002-poison-system-directories.patch&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7C4c6349104c1543a8fd7608dda77ed77b%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638850885432217898%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=MOYMBxa7Qt7dkj3kf3Rkmfewgv5bBJsOMQnZI2omQxQ%3D&reserved=0<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, https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.tkos.co.il%2F&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7C4c6349104c1543a8fd7608dda77ed77b%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638850885432242858%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PjqW7n6fUT8hn%2FYw3EOAZy4%2F5T66O4HUzW9UQjrjgR4%3D&reserved=0<http://www.tkos.co.il/> -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.buildroot.org%2Fmailman%2Flistinfo%2Fbuildroot&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7C4c6349104c1543a8fd7608dda77ed77b%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638850885432255555%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=VE%2BHwNQgR8%2Ft1hr1t055jmANb6gQ6IlrmPxArfg25BQ%3D&reserved=0<https://lists.buildroot.org/mailman/listinfo/buildroot>
[-- Attachment #1.2: Type: text/html, Size: 7459 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Buildroot] EXTERNAL-Re: [Question] -- Inquiry: GCC's -Wpoison-system-directories in Buildroot
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
0 siblings, 1 reply; 5+ messages in thread
From: Arnout Vandecappelle via buildroot @ 2025-06-16 19:00 UTC (permalink / raw)
To: Sunil Kumar Dora, Baruch Siach; +Cc: buildroot@buildroot.org
On 10/06/2025 04:57, Sunil Kumar Dora wrote:
> Thank you, Baruch for the update.
>
> The current poison-system-directories patch in Binutils effectively blocks
> unsafe library paths (via -L flags), but cross-compilation safety also depends
> on preventing accidental use of host headers (via -I flags). Since Buildroot
> doesn’t patch GCC to warn about -I paths to directories like /usr/include, this
> leaves a potential gap:
The `gcc` that Buildroot puts in $HOST_DIR/bin is not the actual gcc, but a
wrapper (the source of which is in toolchain/toolchain-wrapper.c). We moved the
functionality from a patch of GCC itself to the wrapper.
Just try running output/host/bin/*-gcc -I/usr/include to see the effect.
With this, Buildroot is able to have the poisoning functionality also with
external toolchains (which obviously can't be patched).
ld, when called directly, doesn't use the wrapper, so there we still rely on
the patch. This means that for external toolchains, no checking is done. But ld
is very rarely called directly, I don't think we ever had any package that used
ld directly and added -L/usr/lib.
A few years ago we did consider adding the wrapper for ld as well, but it's
not trivial (because the options accepted by ld are widely different than those
of gcc/g++/etc.) and nobody ever got around to doing it.
Regards,
Arnout
> *Risk*: Projects might still pick up host headers during compilation, leading to
> subtle breaks.
> *Comparison*: Yocto addresses this by patching both GCC (for -I) and Binutils
> (for -L).
>
> Questions:
> Is this intentional (e.g., deemed unnecessary for typical Buildroot use cases)?
> Would a GCC patch for -I paths align with Buildroot’s goals?
> *Am I missing any existing mechanisms* (e.g., environment variables, wrapper
> scripts) that mitigate this?
>
> Thanks,
> Sunil Dora
> --------------------------------------------------------------------------------
> *From:* buildroot <buildroot-bounces@buildroot.org> on behalf of Baruch Siach
> via buildroot <buildroot@buildroot.org>
> *Sent:* Monday, June 9, 2025 11:25 PM
> *To:* Sunil Kumar Dora <sunilkumar.dora@blackfigtech.com>
> *Cc:* buildroot@buildroot.org <buildroot@buildroot.org>
> *Subject:* EXTERNAL-Re: [Buildroot] [Question] -- Inquiry: GCC's -Wpoison-
> system-directories in Buildroot
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the content
> is safe.
>
>
> 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://ind01.safelinks.protection.outlook.com/?
> url=https%3A%2F%2Fgitlab.com%2Fbuildroot.org%2Fbuildroot%2F-
> %2Fblob%2Fmaster%2Fpackage%2Fbinutils%2F2.44%2F0002-poison-system-
> directories.patch&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7C4c6349104c1543a8fd7608dda77ed77b%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638850885432217898%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=MOYMBxa7Qt7dkj3kf3Rkmfewgv5bBJsOMQnZI2omQxQ%3D&reserved=0 <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, https://
> ind01.safelinks.protection.outlook.com/?
> url=http%3A%2F%2Fwww.tkos.co.il%2F&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7C4c6349104c1543a8fd7608dda77ed77b%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638850885432242858%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PjqW7n6fUT8hn%2FYw3EOAZy4%2F5T66O4HUzW9UQjrjgR4%3D&reserved=0 <http://www.tkos.co.il/> -
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://ind01.safelinks.protection.outlook.com/?
> url=https%3A%2F%2Flists.buildroot.org%2Fmailman%2Flistinfo%2Fbuildroot&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7C4c6349104c1543a8fd7608dda77ed77b%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638850885432255555%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=VE%2BHwNQgR8%2Ft1hr1t055jmANb6gQ6IlrmPxArfg25BQ%3D&reserved=0 <https://lists.buildroot.org/mailman/listinfo/buildroot>
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Buildroot] EXTERNAL-Re: [Question] -- Inquiry: GCC's -Wpoison-system-directories in Buildroot
2025-06-16 19:00 ` Arnout Vandecappelle via buildroot
@ 2025-06-17 15:28 ` Sunil Kumar Dora
0 siblings, 0 replies; 5+ messages in thread
From: Sunil Kumar Dora @ 2025-06-17 15:28 UTC (permalink / raw)
To: Arnout Vandecappelle, Baruch Siach; +Cc: buildroot@buildroot.org
[-- Attachment #1.1: Type: text/plain, Size: 7695 bytes --]
Thank you so much for the information.
Kind Regards
Sunil Dora
________________________________
From: Arnout Vandecappelle <arnout@rnout.be>
Sent: Tuesday, June 17, 2025 12:30 AM
To: Sunil Kumar Dora <sunilkumar.dora@blackfigtech.com>; Baruch Siach <baruch@tkos.co.il>
Cc: buildroot@buildroot.org <buildroot@buildroot.org>
Subject: Re: [Buildroot] EXTERNAL-Re: [Question] -- Inquiry: GCC's -Wpoison-system-directories in Buildroot
[You don't often get email from arnout@rnout.be. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
On 10/06/2025 04:57, Sunil Kumar Dora wrote:
> Thank you, Baruch for the update.
>
> The current poison-system-directories patch in Binutils effectively blocks
> unsafe library paths (via -L flags), but cross-compilation safety also depends
> on preventing accidental use of host headers (via -I flags). Since Buildroot
> doesn’t patch GCC to warn about -I paths to directories like /usr/include, this
> leaves a potential gap:
The `gcc` that Buildroot puts in $HOST_DIR/bin is not the actual gcc, but a
wrapper (the source of which is in toolchain/toolchain-wrapper.c). We moved the
functionality from a patch of GCC itself to the wrapper.
Just try running output/host/bin/*-gcc -I/usr/include to see the effect.
With this, Buildroot is able to have the poisoning functionality also with
external toolchains (which obviously can't be patched).
ld, when called directly, doesn't use the wrapper, so there we still rely on
the patch. This means that for external toolchains, no checking is done. But ld
is very rarely called directly, I don't think we ever had any package that used
ld directly and added -L/usr/lib.
A few years ago we did consider adding the wrapper for ld as well, but it's
not trivial (because the options accepted by ld are widely different than those
of gcc/g++/etc.) and nobody ever got around to doing it.
Regards,
Arnout
> *Risk*: Projects might still pick up host headers during compilation, leading to
> subtle breaks.
> *Comparison*: Yocto addresses this by patching both GCC (for -I) and Binutils
> (for -L).
>
> Questions:
> Is this intentional (e.g., deemed unnecessary for typical Buildroot use cases)?
> Would a GCC patch for -I paths align with Buildroot’s goals?
> *Am I missing any existing mechanisms* (e.g., environment variables, wrapper
> scripts) that mitigate this?
>
> Thanks,
> Sunil Dora
> --------------------------------------------------------------------------------
> *From:* buildroot <buildroot-bounces@buildroot.org> on behalf of Baruch Siach
> via buildroot <buildroot@buildroot.org>
> *Sent:* Monday, June 9, 2025 11:25 PM
> *To:* Sunil Kumar Dora <sunilkumar.dora@blackfigtech.com>
> *Cc:* buildroot@buildroot.org <buildroot@buildroot.org>
> *Subject:* EXTERNAL-Re: [Buildroot] [Question] -- Inquiry: GCC's -Wpoison-
> system-directories in Buildroot
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the content
> is safe.
>
>
> 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://ind01.safelinks.protection.outlook.com/?
> url=https%3A%2F%2Fgitlab.com%2Fbuildroot.org%2Fbuildroot%2F-
> %2Fblob%2Fmaster%2Fpackage%2Fbinutils%2F2.44%2F0002-poison-system-
> directories.patch&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7C4c6349104c1543a8fd7608dda77ed77b%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638850885432217898%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=MOYMBxa7Qt7dkj3kf3Rkmfewgv5bBJsOMQnZI2omQxQ%3D&reserved=0 <https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2Fbuildroot.org%2Fbuildroot%2F-%2Fblob%2Fmaster%2Fpackage%2Fbinutils%2F2.44%2F0002-poison-system-directories.patch&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7Ccf5e00dc3e4a40fb403808ddad081e4f%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638856972603584545%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=mFQsf5%2FG12rpq8TFGrEpxIYSOEeO9NHriZeuKR1gm8c%3D&reserved=0<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, https://
> ind01.safelinks.protection.outlook.com/?
> url=http%3A%2F%2Fwww.tkos.co.il%2F&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7C4c6349104c1543a8fd7608dda77ed77b%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638850885432242858%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PjqW7n6fUT8hn%2FYw3EOAZy4%2F5T66O4HUzW9UQjrjgR4%3D&reserved=0 <https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.tkos.co.il%2F&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7Ccf5e00dc3e4a40fb403808ddad081e4f%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638856972603602565%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=y%2FpldJi%2FNSKHwUIq2yC2Syqa4ruPrYBND%2BqheweASXE%3D&reserved=0<http://www.tkos.co.il/>> -
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://ind01.safelinks.protection.outlook.com/?
> url=https%3A%2F%2Flists.buildroot.org%2Fmailman%2Flistinfo%2Fbuildroot&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7C4c6349104c1543a8fd7608dda77ed77b%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638850885432255555%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=VE%2BHwNQgR8%2Ft1hr1t055jmANb6gQ6IlrmPxArfg25BQ%3D&reserved=0 <https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.buildroot.org%2Fmailman%2Flistinfo%2Fbuildroot&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7Ccf5e00dc3e4a40fb403808ddad081e4f%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638856972603621814%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=IJISPWd3ms1ttbT5wroz2WQnDeQF%2F0PMf7B5aIv96D8%3D&reserved=0<https://lists.buildroot.org/mailman/listinfo/buildroot>>
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.buildroot.org%2Fmailman%2Flistinfo%2Fbuildroot&data=05%7C02%7Csunilkumar.dora%40blackfigtech.com%7Ccf5e00dc3e4a40fb403808ddad081e4f%7C75dd016f4b8642d99a4d6df5b9790019%7C0%7C0%7C638856972603635990%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=HxtwXOYluub680YtS7vZusM4si68fGh%2BKQcnFK7qdgs%3D&reserved=0<https://lists.buildroot.org/mailman/listinfo/buildroot>
[-- Attachment #1.2: Type: text/html, Size: 11042 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2025-06-17 15:28 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox