LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Robin Jarry <robin.jarry@6wind.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] kbuild: fix host progs build with libs in non standard locations
Date: Tue, 27 Feb 2018 21:52:31 +0100 [thread overview]
Message-ID: <20180227205231.t2wmh4e2ky2ganyo@6wind.com> (raw)
In-Reply-To: <20180227174518.qzw6eqmuyggcvjl6@treble>
2018-02-27, Josh Poimboeuf:
> In Documentation/kbuild/kbuild.txt, we have the following environment
> variables:
>
> KCFLAGS
> --------------------------------------------------
> Additional options to the C compiler (for built-in and modules).
>
> CFLAGS_KERNEL
> --------------------------------------------------
> Additional options for $(CC) when used to compile
> code that is compiled as built-in.
>
> CFLAGS_MODULE
> --------------------------------------------------
> Additional module specific options to use for $(CC).
>
> LDFLAGS_MODULE
> --------------------------------------------------
> Additional options used for $(LD) when linking modules.
>
> LDFLAGS_vmlinux
> --------------------------------------------------
> Additional options passed to final link of vmlinux.
>
> So instead of
>
> HOST_CFLAGS
> HOST_LDFLAGS
>
> maybe it would be more consistent to call them
>
> CFLAGS_HOST
> LDFLAGS_HOST
>
> ?
I had missed this file. Indeed {C,LD}FLAGS_HOST are much less confusing!
> Also, the new environment variables should be documented in the above
> file.
Sure, I'll do that. However, I feel like I should also leave the
paragraph in Documentation/admin-guide/README.txt.
What do you think?
--
Robin
next prev parent reply other threads:[~2018-02-27 20:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 14:22 [PATCH 0/2] objtool: fix libelf detection in non-standard locations Robin Jarry
2018-02-23 14:22 ` [PATCH 1/2] kbuild: introduce HOST_EXTRALDFLAGS Robin Jarry
2018-02-23 14:22 ` [PATCH 2/2] objtool: use host flags to detect if libelf is missing Robin Jarry
2018-02-23 15:37 ` Josh Poimboeuf
2018-02-23 16:22 ` Robin Jarry
2018-02-23 16:34 ` Josh Poimboeuf
2018-02-26 18:41 ` [PATCH v2 0/3] kbuild: fix host progs build with libs in non standard locations Robin Jarry
2018-02-26 18:41 ` [PATCH v2 1/3] kbuild: introduce HOST_{C,LD}FLAGS Robin Jarry
2018-02-26 18:41 ` [PATCH v2 2/3] kbuild: use HOSTLDFLAGS for single .c executables Robin Jarry
2018-04-05 14:23 ` Masahiro Yamada
2018-02-26 18:41 ` [PATCH v2 3/3] objtool: use global host flags for compilation Robin Jarry
2018-02-27 17:49 ` Josh Poimboeuf
2018-02-27 20:55 ` Robin Jarry
2018-02-27 21:41 ` Josh Poimboeuf
2018-02-27 17:45 ` [PATCH v2 0/3] kbuild: fix host progs build with libs in non standard locations Josh Poimboeuf
2018-02-27 20:52 ` Robin Jarry [this message]
2018-02-27 21:38 ` Josh Poimboeuf
2018-02-28 0:23 ` Randy Dunlap
2018-02-28 10:22 ` Masahiro Yamada
2018-02-28 17:24 ` Robin Jarry
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=20180227205231.t2wmh4e2ky2ganyo@6wind.com \
--to=robin.jarry@6wind.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.com \
--subject='Re: [PATCH v2 0/3] kbuild: fix host progs build with libs in non standard locations' \
/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
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).