On Tue, Oct 18, 2016 at 9:38 AM, SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx> wrote: >>> 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. Fine, but my point was to check that the basic things worked before trying the complicated, or "advanced" stuff. If, somehow, fixdep didn't work in a basic setup then you'd know it wasn't one of your advanced features that was causing the problem. And if fixdep did work with a basic setup , then that would suggest something wrong with your advanced command line. -- Jim -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html