The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: "Chen, Rong A" <rong.a.chen@intel.com>,
	kernel test robot <lkp@intel.com>,
	Masahiro Yamada <masahiroy@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: gcc: error: unrecognized command-line option '-mno-space-regs'
Date: Mon, 14 Feb 2022 10:17:47 +0100	[thread overview]
Message-ID: <bf9d7f0d-b77f-6cc2-96df-bb9f2aebeae1@gmx.de> (raw)
In-Reply-To: <5a693363-521b-3d9e-7ce7-6844a5eee7c3@intel.com>

On 2/14/22 10:15, Chen, Rong A wrote:
>
>
> On 2/14/2022 6:26 AM, Helge Deller wrote:
>> On 2/13/22 11:39, kernel test robot wrote:
>>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>> head:   b81b1829e7e39f6cebdf6e4d5484eacbceda8554
>>> commit: 5f6e0fe01b6b33894cf6f61b359ab5a6d2b7674e parisc: Fix compile failure when building 64-bit kernel natively
>>> date:   6 months ago
>>> config: parisc64-randconfig-r035-20220213 (https://download.01.org/0day-ci/archive/20220213/202202131837.mZeWy9J4-lkp@intel.com/config)
>>> compiler: hppa-linux-gcc (GCC) 11.2.0
>>> reproduce (this is a W=1 build):
>>>          wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>>          chmod +x ~/bin/make.cross
>>>          # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5f6e0fe01b6b33894cf6f61b359ab5a6d2b7674e
>>>          git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>>          git fetch --no-tags linus master
>>>          git checkout 5f6e0fe01b6b33894cf6f61b359ab5a6d2b7674e
>>>          # save the config file to linux build tree
>>>          mkdir build_dir
>>>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=parisc64 prepare
>>>
>>> If you fix the issue, kindly add following tag as appropriate
>>> Reported-by: kernel test robot <lkp@intel.com>
>>>
>>> All errors (new ones prefixed by >>):
>>>
>>>     scripts/genksyms/parse.y: warning: 9 shift/reduce conflicts [-Wconflicts-sr]
>>>     scripts/genksyms/parse.y: warning: 5 reduce/reduce conflicts [-Wconflicts-rr]
>>>>> gcc: error: unrecognized command-line option '-mno-space-regs'
>>>>> gcc: error: unrecognized command-line option '-mno-space-regs'
>>>>> gcc: error: unrecognized command-line option '-mfast-indirect-calls'; did you mean '-mforce-indirect-call'?
>>>>> gcc: error: unrecognized command-line option '-mfast-indirect-calls'; did you mean '-mforce-indirect-call'?
>>>>> gcc: error: unrecognized command-line option '-mdisable-fpregs'
>>>>> gcc: error: unrecognized command-line option '-mschedule=7200'
>>
>> Same issue as the other error.
>> Here a 64bit compiler was used to build a 32-bit kernel...
>
> Hi Helge,
>
> Thanks for the explanation, it seems kernel still can be 32-bit if using
> make ARCH=parisc64 randconfig, we'll check CONFIG_64BIT config directly
> to decide the ARCH value.

Yes, that's the best approach!
Thanks,
Helge


> Best Regards,
> Rong Chen
>
>
>>
>> I've queued up a patch in for-next which should give a better error message if
>> someone uses such a wrong combination:
>> https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id=b160628e9ebcdc85d0db9d7f423c26b3c7c179d0
>>
>> Helge
>>
>>>     make[2]: *** [scripts/Makefile.build:117: scripts/mod/devicetable-offsets.s] Error 1
>>
>>>>> gcc: error: unrecognized command-line option '-mdisable-fpregs'
>>>>> gcc: error: unrecognized command-line option '-mschedule=7200'
>>>     make[2]: *** [scripts/Makefile.build:271: scripts/mod/empty.o] Error 1
>>>     make[2]: Target '__build' not remade because of errors.
>>>     make[1]: *** [Makefile:1216: prepare0] Error 2
>>>     make[1]: Target 'prepare' not remade because of errors.
>>>     make: *** [Makefile:220: __sub-make] Error 2
>>>     make: Target 'prepare' not remade because of errors.
>>>
>>> ---
>>> 0-DAY CI Kernel Test Service, Intel Corporation
>>> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>>>
>> _______________________________________________
>> kbuild-all mailing list -- kbuild-all@lists.01.org
>> To unsubscribe send an email to kbuild-all-leave@lists.01.org
>>


      reply	other threads:[~2022-02-14  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-13 10:39 gcc: error: unrecognized command-line option '-mno-space-regs' kernel test robot
2022-02-13 22:26 ` Helge Deller
2022-02-14  9:15   ` [kbuild-all] " Chen, Rong A
2022-02-14  9:17     ` Helge Deller [this message]

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=bf9d7f0d-b77f-6cc2-96df-bb9f2aebeae1@gmx.de \
    --to=deller@gmx.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=masahiroy@kernel.org \
    --cc=rong.a.chen@intel.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