Re: Difficulties around "fixdep" for the usage of a kernel build output directory

2016-10-18 Thread Jim Davis
On Tue, Oct 18, 2016 at 10:25 AM, SF Markus Elfring wrote: > 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

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

2016-10-18 Thread Jim Davis
On Tue, Oct 18, 2016 at 10:25 AM, SF Markus Elfring wrote: > 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

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

2016-10-18 Thread SF Markus Elfring
> Fine, but my point was to check that the basic things worked before > trying the complicated, or "advanced" stuff. Your suggestion is fine in this sense. I can observe that the following command variant works as expected here. my_build_dir=/tmp/fixdep-check-20161018-1 && mkdir

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

2016-10-18 Thread SF Markus Elfring
> Fine, but my point was to check that the basic things worked before > trying the complicated, or "advanced" stuff. Your suggestion is fine in this sense. I can observe that the following command variant works as expected here. my_build_dir=/tmp/fixdep-check-20161018-1 && mkdir

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

2016-10-18 Thread Jim Davis
On Tue, Oct 18, 2016 at 9:38 AM, SF Markus Elfring 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

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

2016-10-18 Thread Jim Davis
On Tue, Oct 18, 2016 at 9:38 AM, SF Markus Elfring 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}"

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

2016-10-18 Thread SF Markus Elfring
>> 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}"

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

2016-10-18 Thread SF Markus Elfring
>> 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}"

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

2016-10-18 Thread Jim Davis
On Tue, Oct 18, 2016 at 6:54 AM, SF Markus Elfring wrote: > Hello, > > The file "README" contains a section "BUILD directory for the kernel". > I would like to use the functionality which is described there. > > One of my commands for such a build try is working as

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

2016-10-18 Thread Jim Davis
On Tue, Oct 18, 2016 at 6:54 AM, SF Markus Elfring wrote: > Hello, > > The file "README" contains a section "BUILD directory for the kernel". > I would like to use the functionality which is described there. > > One of my commands for such a build try is working as desired. > > >