Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1503008

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

Show all headers | View 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

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Difficulties around "fixdep" for the usage of a kernel build output  directory SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-18 16:00 +0200
  Re: Difficulties around "fixdep" for the usage of a kernel build  output directory Jim Davis <jim.epost@gmail.com> - 2016-10-18 17:20 +0200
    Re: Difficulties around "fixdep" for the usage of a kernel build  output directory SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-18 18:40 +0200
      Re: Difficulties around "fixdep" for the usage of a kernel build  output directory Jim Davis <jim.epost@gmail.com> - 2016-10-18 19:00 +0200
        Re: Difficulties around "fixdep" for the usage of a kernel build  output directory SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-18 19:30 +0200
          Re: Difficulties around "fixdep" for the usage of a kernel build  output directory Jim Davis <jim.epost@gmail.com> - 2016-10-18 22:50 +0200
            Re: Challenges around the usage of different "HOSTCFLAGS" for kernel  build configuration and module generation SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-19 19:10 +0200
              Re: Challenges around the usage of different "HOSTCFLAGS" for kernel  build configuration and module generation Jim Davis <jim.epost@gmail.com> - 2016-10-19 22:00 +0200
                Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation Segher Boessenkool <segher@kernel.crashing.org> - 2016-10-20 00:10 +0200
                Re: Challenges around the usage of different "HOSTCFLAGS" for kernel  build configuration and module generation SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-20 09:40 +0200
                Re: Challenges around the usage of different "HOSTCFLAGS" for kernel  build configuration and module generation SF Markus Elfring <elfring@users.sourceforge.net> - 2016-10-20 08:40 +0200

csiph-web