From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.com>
Cc: linux-kernel@vger.kernel.org
Subject: Difficulties around "fixdep" for the usage of a kernel build output directory
Date: Tue, 18 Oct 2016 15:54:59 +0200 [thread overview]
Message-ID: <4f2251fc-94ee-41d3-cc03-a39cee5a084c@users.sourceforge.net> (raw)
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.
elfring@Sonne:~/Projekte/Linux/next-patched> git checkout next-20161014 && 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}" && make O="${my_output_dir}" HOSTCC='/usr/bin/gcc-6' HOSTCFLAGS="${my_parameters}" allmodconfig; done
…
#
# configuration written to .config
#
I stumble on the following messages for another build command.
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
make[1]: Entering directory …
HOSTCC scripts/basic/fixdep - due to command line change
scripts/basic/fixdep: line 1: .file: command not found
scripts/basic/fixdep: line 2: .comm: command not found
…
scripts/basic/fixdep: line 6: .section: command not found
scripts/basic/fixdep: line 7: .align: command not found
scripts/basic/fixdep: line 8: .LC0:: command not found
scripts/basic/fixdep: line 9: .string: command not found
…
I wonder why this approach does not work so far.
I would appreciate your advices.
Regards,
Markus
next reply other threads:[~2016-10-18 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 13:54 SF Markus Elfring [this message]
2016-10-18 15:12 ` Difficulties around "fixdep" for the usage of a kernel build output directory Jim Davis
2016-10-18 16:38 ` SF Markus Elfring
2016-10-18 16:50 ` Jim Davis
2016-10-18 17:25 ` SF Markus Elfring
2016-10-18 20:44 ` Jim Davis
2016-10-19 7:25 ` Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation SF Markus Elfring
2016-10-19 19:51 ` Jim Davis
2016-10-19 22:03 ` Segher Boessenkool
2016-10-20 7:37 ` SF Markus Elfring
2016-10-20 6:33 ` SF Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f2251fc-94ee-41d3-cc03-a39cee5a084c@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox