>> Can it be that the passing of the adjusted parameter "HOSTCFLAGS" has got a significant >> influence (with unwanted side effects) in this use case? > > That's probably it. If I strip down your advanced original example to just > > make defconfig > make HOSTCFLAGS=-S > > then I get a similar error: > > HOSTCC scripts/basic/fixdep > scripts/basic/fixdep: 1: scripts/basic/fixdep: .file: not found … > and so forth. Thanks that you could reproduce my observation also with a simple example on your test system. > The problem is that, with -S, fixdep isn't build as an executable: > > jim@krebstar:~/linux-next/scripts/basic$ file fixdep > fixdep: assembler source, ASCII text 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? * Does this issue indicate further development challenges? * How are the chances that the involved software dependencies can be handled better in more detail? > I'm guessing that in your original example you wanted to look at the > assembly output gcc produced; Yes. - I became interested in this use case once more. > you'd probably have better luck using objdump for that. This approach can occasionally work to some degree. I am looking for a better (or more convenient) solution. I got the impression that I need to put special build parameters into the make files directly so far while I would prefer to pass extra settings as command line arguments for the tool "make". Will it make sense to distinguish such parameters for development phases (or stages) like "kernel build configuration" and corresponding "module generation" any more? Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
