From: Laura Abbott <labbott@redhat.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>
Cc: Laura Abbott <labbott@redhat.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: [PATCH 0/3] HOSTCFLAGS and HOSTLDFLAGS from the environment
Date: Wed, 28 Mar 2018 17:48:02 -0700 [thread overview]
Message-ID: <20180329004805.7278-1-labbott@redhat.com> (raw)
Hi,
Someone noted that scripts/tools userspace binaries packaged as part of
the Fedora kernel were not picking up the recommended compiler flags
(https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/master/f/buildflags.md)
This series lets the host ld and C flags be set on the command line
similar to the kernel flags:
make AFLAGS_HOSTCFLAGS="%{build_cflags}" AFLAGS_HOSTLDFLAGS="%{build_ldflags}"
There's one more annoying case I didn't quite figure out with
tools/objtool/fixdep since that's linked with ld directly but this
covers the initial set of reports.
Thanks,
Laura
Laura Abbott (3):
kbuild: Support HOSTLDFLAGS
objtool: Support HOSTCFLAGS and HOSTLDFLAGS
kbuild: Allow passing additional HOSTCFLAGS and HOSTLDFLAGS
Documentation/kbuild/kbuild.txt | 9 +++++++++
Makefile | 3 +++
scripts/Makefile.host | 6 +++---
tools/build/Makefile.build | 2 +-
tools/objtool/Makefile | 5 +++--
5 files changed, 19 insertions(+), 6 deletions(-)
--
2.16.2
next reply other threads:[~2018-03-29 0:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 0:48 Laura Abbott [this message]
2018-03-29 0:48 ` [PATCH 1/3] kbuild: Support HOSTLDFLAGS Laura Abbott
2018-04-05 5:13 ` Masahiro Yamada
2018-03-29 0:48 ` [PATCH 2/3] objtool: Support HOSTCFLAGS and HOSTLDFLAGS Laura Abbott
2018-04-05 4:42 ` Masahiro Yamada
2018-04-05 22:01 ` Laura Abbott
2018-04-06 17:27 ` Josh Poimboeuf
2018-03-29 0:48 ` [PATCH 3/3] kbuild: Allow passing additional " Laura Abbott
2018-04-05 4:59 ` Masahiro Yamada
2018-04-05 21:51 ` Laura Abbott
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=20180329004805.7278-1-labbott@redhat.com \
--to=labbott@redhat.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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.