From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Jim Davis <jim.epost@gmail.com>
Cc: linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation
Date: Thu, 20 Oct 2016 08:33:00 +0200 [thread overview]
Message-ID: <2ff4dbf5-f9e5-9aa1-a93a-2e2bd81b43f7@users.sourceforge.net> (raw)
In-Reply-To: <CA+r1Zhiat4d8FqFcD1BBCxe5jyWOtSDZp99_CLV0qE1D3REquw@mail.gmail.com>
> make defconfig; make EXTRA_CFLAGS="-g" drivers/md/; objdump -S drivers/md/whatever.o
Such a command looks promising.
* I find it safer when double ampersand will be used as control operator
instead of semicolon there.
* I get the impression from an other command like "find . -name '?akefile' -exec ack --with-filename EXTRA_CFLAGS '{}' \;"
that the suggested parameter "EXTRA_CFLAGS" will not achieve an effect
at places where I am interested in at the moment.
It seems that further fine-tuning can become interesting and challenging
for involved make variables.
Regards,
Markus
prev parent reply other threads:[~2016-10-20 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 13:54 Difficulties around "fixdep" for the usage of a kernel build output directory SF Markus Elfring
2016-10-18 15:12 ` Jim Davis
2016-10-18 16:38 ` SF Markus Elfring
2016-10-18 16:50 ` Jim Davis
2016-10-18 17:25 ` SF Markus Elfring
2016-10-18 20:44 ` Jim Davis
2016-10-19 7:25 ` Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation SF Markus Elfring
2016-10-19 19:51 ` Jim Davis
2016-10-19 22:03 ` Segher Boessenkool
2016-10-20 7:37 ` SF Markus Elfring
2016-10-20 6:33 ` SF Markus Elfring [this message]
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=2ff4dbf5-f9e5-9aa1-a93a-2e2bd81b43f7@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=jim.epost@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.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