[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <80d31faa-b328-b8eb-4d19-d96aef1cc16a@users.sourceforge.net>
Date: Thu, 20 Oct 2016 09:37:34 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Segher Boessenkool <segher@...nel.crashing.org>
Cc: Jim Davis <jim.epost@...il.com>, linux-kbuild@...r.kernel.org,
Michal Marek <mmarek@...e.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: Challenges around the usage of different "HOSTCFLAGS" for kernel
build configuration and module generation
> 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
Powered by blists - more mailing lists