Messages in this thread | | | Subject | Re: Difficulties around "fixdep" for the usage of a kernel build output directory | From | SF Markus Elfring <> | Date | Tue, 18 Oct 2016 18:38:22 +0200 |
| |
>> elfring@Sonne:~/Projekte/Linux/next-patched> my_off=-O0 && for X in off; do my_output_dir=${my_build_dir}unchanged/optimisation/${X} && my_var="my_${X}" && my_parameters="-Wall -std=gnu89 -fomit-frame-pointer ${!my_var}" && LANG=C make V=2 O="${my_output_dir}" HOSTCC='/usr/bin/gcc-6' HOSTCFLAGS="-S ${my_parameters}" drivers/md/; done … > That's a very complicated command line.
I find it "advanced".
It shows a few of my imaginations around a specific software development task.
> Does something basic, like > > make O=/tmp/$$ allmodconfig > make O=/tmp/$$ > > work for you?
Not really. - I would like to achieve the automatic selection of a few compilation settings by a for loop which I reduced in the shown example to one element.
I am looking for a "convenient" way to get assembler source files from the preferrred C compiler for some software build configurations. I hope that I can avoid the switching of compilation results in the source file directory hierarchy so that an occasional disassembly by a tool like "objdump" could be compared.
Regards, Markus
| |