[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+r1ZhhqEBvV0ivz=MvaHhRquhFS2mxddJ-GOx81ZeSerKsD3g@mail.gmail.com>
Date: Tue, 18 Oct 2016 09:50:36 -0700
From: Jim Davis <jim.epost@...il.com>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc: linux-kbuild@...r.kernel.org, Michal Marek <mmarek@...e.com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Difficulties around "fixdep" for the usage of a kernel build
output directory
On Tue, Oct 18, 2016 at 9:38 AM, SF Markus Elfring
<elfring@...rs.sourceforge.net> wrote:
>>> elfring@...ne:~/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
Powered by blists - more mailing lists