From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Jim Davis <jim.epost@gmail.com>,
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 09:37:34 +0200 [thread overview]
Message-ID: <80d31faa-b328-b8eb-4d19-d96aef1cc16a@users.sourceforge.net> (raw)
In-Reply-To: <20161019220346.GA20054@gate.crashing.org>
> Don't forget -r when running objdump on an object file.
Thanks for your reminder.
> But, you want to use make drivers/md/whatever.s if you want to see
> the assembler code.
Thanks for your advice!
This is one kind of "generation convenience" I was looking for.
Was my software development attention too limited for another moment
so that I did not directly pick an opportunity up from the description
like "dir/file.[ois] - Build specified target only"
(by the command "make help") that I can get assembler source files
for Linux modules so easy on demand?
Would you like to point any places out in the make scripts which
show relevant commands for such build targets?
> And that doesn't work for build-time tools,
I got the impression that they can trigger further software development challenges.
Should their source files (and corresponding make parameters) be improved anyhow?
> which I think is what the original discussion was about.
I see a few change possibilities there. Will it be useful to reconsider
the generation parameters for build-time tools in comparison to components
from other Linux software areas?
Will a variable like "EXTRA_CFLAGS" achieve a desired effect at more places?
Regards,
Markus
next prev parent reply other threads:[~2016-10-20 7:38 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 [this message]
2016-10-20 6:33 ` SF Markus Elfring
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=80d31faa-b328-b8eb-4d19-d96aef1cc16a@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 \
--cc=segher@kernel.crashing.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