LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: kbuild-all@01.org, linuxppc-dev@lists.ozlabs.org,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: [powerpc:topic/kbuild 4/4] arch/powerpc/Kconfig:466: syntax error
Date: Sun, 20 May 2018 14:20:03 +0800	[thread overview]
Message-ID: <201805201459.Il5gwYkF%fengguang.wu@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git topic/kbuild
head:   023eff0e59052c52bc4f077e66e82d68be486d7f
commit: 023eff0e59052c52bc4f077e66e82d68be486d7f [4/4] powerpc/kbuild: Move -mprofile-kernel check to Kconfig
config: powerpc-asp8347_defconfig
compiler: powerpc-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 023eff0e59052c52bc4f077e66e82d68be486d7f
        make.cross ARCH=powerpc  83xx/asp8347_defconfig
        make.cross ARCH=powerpc 

All errors (new ones prefixed by >>):

   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
>> arch/powerpc/Kconfig:466: syntax error
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
>> arch/powerpc/Kconfig:465: invalid option
   make[2]: *** [83xx/asp8347_defconfig] Error 1
   make[1]: *** [83xx/asp8347_defconfig] Error 2
   make: *** [sub-make] Error 2
--
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
>> arch/powerpc/Kconfig:466: syntax error
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
>> arch/powerpc/Kconfig:465: invalid option
   make[2]: *** [oldconfig] Error 1
   make[1]: *** [oldconfig] Error 2
   make: *** [sub-make] Error 2
--
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
>> arch/powerpc/Kconfig:466: syntax error
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
   arch/powerpc/Kconfig:465:warning: ignoring unsupported character '$'
>> arch/powerpc/Kconfig:465: invalid option
   make[2]: *** [olddefconfig] Error 1
   make[2]: Target 'oldnoconfig' not remade because of errors.
   make[1]: *** [oldnoconfig] Error 2
   make: *** [sub-make] Error 2

vim +466 arch/powerpc/Kconfig

e05c0e81 Kevin Hao       2013-07-16  441  
3d72bbc4 Michael Neuling 2013-02-13  442  config PPC_TRANSACTIONAL_MEM
3d72bbc4 Michael Neuling 2013-02-13  443         bool "Transactional Memory support for POWERPC"
3d72bbc4 Michael Neuling 2013-02-13  444         depends on PPC_BOOK3S_64
3d72bbc4 Michael Neuling 2013-02-13  445         depends on SMP
7b37a123 Michael Neuling 2014-01-08  446         select ALTIVEC
7b37a123 Michael Neuling 2014-01-08  447         select VSX
3d72bbc4 Michael Neuling 2013-02-13  448         default n
3d72bbc4 Michael Neuling 2013-02-13  449         ---help---
3d72bbc4 Michael Neuling 2013-02-13  450           Support user-mode Transactional Memory on POWERPC.
3d72bbc4 Michael Neuling 2013-02-13  451  
951eedeb Nicholas Piggin 2017-05-29  452  config LD_HEAD_STUB_CATCH
951eedeb Nicholas Piggin 2017-05-29  453  	bool "Reserve 256 bytes to cope with linker stubs in HEAD text" if EXPERT
951eedeb Nicholas Piggin 2017-05-29  454  	depends on PPC64
951eedeb Nicholas Piggin 2017-05-29  455  	default n
951eedeb Nicholas Piggin 2017-05-29  456  	help
951eedeb Nicholas Piggin 2017-05-29  457  	  Very large kernels can cause linker branch stubs to be generated by
951eedeb Nicholas Piggin 2017-05-29  458  	  code in head_64.S, which moves the head text sections out of their
951eedeb Nicholas Piggin 2017-05-29  459  	  specified location. This option can work around the problem.
951eedeb Nicholas Piggin 2017-05-29  460  
951eedeb Nicholas Piggin 2017-05-29  461  	  If unsure, say "N".
951eedeb Nicholas Piggin 2017-05-29  462  
8c50b72a Torsten Duwe    2016-03-03  463  config MPROFILE_KERNEL
8c50b72a Torsten Duwe    2016-03-03  464  	depends on PPC64 && CPU_LITTLE_ENDIAN
023eff0e Nicholas Piggin 2018-05-17 @465  	def_bool $(success $(srctree)/arch/powerpc/tools/gcc-check-mprofile-kernel.sh $(CC) -I$(srctree)/include -D__KERNEL__)
8c50b72a Torsten Duwe    2016-03-03 @466  

:::::: The code at line 466 was first introduced by commit
:::::: 8c50b72a3b4f1f7cdfdfebd233b1cbd121262e65 powerpc/ftrace: Add Kconfig & Make glue for mprofile-kernel

:::::: TO: Torsten Duwe <duwe@lst.de>
:::::: CC: Michael Ellerman <mpe@ellerman.id.au>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

             reply	other threads:[~2018-05-20  6:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-20  6:20 kbuild test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-30 18:26 [powerpc:topic/kbuild 4/4] arch/powerpc/Kconfig:466: syntax error kbuild test robot

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=201805201459.Il5gwYkF%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.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