Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1504359
| From | Segher Boessenkool <segher@kernel.crashing.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation |
| Date | 2016-10-20 00:10 +0200 |
| Message-ID | <su7dE-7iT-5@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <stFU6-4q4-23@gated-at.bofh.it> <stGn8-4Sx-37@gated-at.bofh.it> <stJuF-759-25@gated-at.bofh.it> <su2xk-4eW-27@gated-at.bofh.it> <su5bP-5KC-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Oct 19, 2016 at 12:51:44PM -0700, Jim Davis wrote: > On Wed, Oct 19, 2016 at 12:25 AM, SF Markus Elfring > <elfring@users.sourceforge.net> wrote: > > > > Are you interested that a software generation parameter like "-S" > > (for output of assembler source files) could be directly supported > > for a special build variant? > > No, if you want to see the assembly code then something like > > make defconfig; make EXTRA_CFLAGS="-g" drivers/md/; objdump -S > drivers/md/whatever.o > > seems easy enough. You could write a little shell wrapper to save > some keystrokes if you find you're running those commands frequently. Don't forget -r when running objdump on an object file. But, you want to use make drivers/md/whatever.s if you want to see the assembler code. And that doesn't work for build-time tools, which I think is what the original discussion was about. Segher
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Difficulties around "fixdep" for the usage of a kernel build output directory SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-18 16:00 +0200
Re: Difficulties around "fixdep" for the usage of a kernel build output directory Jim Davis <jim.epost@gmail.com> - 2016-10-18 17:20 +0200
Re: Difficulties around "fixdep" for the usage of a kernel build output directory SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-18 18:40 +0200
Re: Difficulties around "fixdep" for the usage of a kernel build output directory Jim Davis <jim.epost@gmail.com> - 2016-10-18 19:00 +0200
Re: Difficulties around "fixdep" for the usage of a kernel build output directory SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-18 19:30 +0200
Re: Difficulties around "fixdep" for the usage of a kernel build output directory Jim Davis <jim.epost@gmail.com> - 2016-10-18 22:50 +0200
Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-19 19:10 +0200
Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation Jim Davis <jim.epost@gmail.com> - 2016-10-19 22:00 +0200
Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation Segher Boessenkool <segher@kernel.crashing.org> - 2016-10-20 00:10 +0200
Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-20 09:40 +0200
Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-20 08:40 +0200
csiph-web