From: Segher Boessenkool <segher@kernel.crashing.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@linux-foundation.org, linux-arch@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
masahiroy@kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] isystem: delete global -isystem compile option
Date: Sun, 1 Aug 2021 16:32:47 -0500 [thread overview]
Message-ID: <20210801213247.GM1583@gate.crashing.org> (raw)
In-Reply-To: <20210801201336.2224111-3-adobriyan@gmail.com>
On Sun, Aug 01, 2021 at 11:13:36PM +0300, Alexey Dobriyan wrote:
> In theory, it enables "leakage" of userspace headers into kernel which
> may present licensing problem.
> -NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)
> +NOSTDINC_FLAGS += -nostdinc
This is removing the compiler's own include files. These are required
for all kinds of basic features, and required to be compliant to the C
standard at all. These are not "userspace headers", that is what
-nostdinc takes care of already.
In the case of GCC all these headers are GPL-with-runtime-exception, so
claiming this can cause licensing problems is fearmongering.
I strongly advise against doing this.
Segher
next prev parent reply other threads:[~2021-08-01 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 20:13 [PATCH 1/3] isystem: trim/fixup stdarg.h and other headers Alexey Dobriyan
2021-08-01 20:13 ` [PATCH 2/3] isystem: ship and use stdarg.h Alexey Dobriyan
2021-08-03 7:14 ` Ard Biesheuvel
2021-08-17 1:30 ` Masahiro Yamada
2021-08-06 13:00 ` Rafael J. Wysocki
2021-08-01 20:13 ` [PATCH 3/3] isystem: delete global -isystem compile option Alexey Dobriyan
2021-08-01 21:32 ` Segher Boessenkool [this message]
2021-08-02 6:42 ` Alexey Dobriyan
2021-08-02 16:47 ` Segher Boessenkool
2021-08-02 20:30 ` Alexey Dobriyan
2021-08-02 21:42 ` Segher Boessenkool
2021-08-02 1:30 ` kernel test robot
2021-08-02 18:18 ` Nathan Chancellor
2021-08-02 20:32 ` Alexey Dobriyan
2021-08-02 20:38 ` Nathan Chancellor
2021-08-02 0:21 ` [PATCH 1/3] isystem: trim/fixup stdarg.h and other headers kernel test robot
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=20210801213247.GM1583@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=paulus@samba.org \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).