linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arvind Sankar <nivedita@alum.mit.edu>
To: Rong Chen <rong.a.chen@intel.com>
Cc: Fangrui Song <maskray@google.com>,
	Nick Desaulniers <ndesaulniers@google.com>,
	kernel test robot <lkp@intel.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	kbuild-all@lists.01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-all] Re: gcc-5: error: -gz is not supported in this configuration
Date: Tue, 9 Jun 2020 23:12:25 -0400	[thread overview]
Message-ID: <20200610031225.GA1917869@rani.riverdale.lan> (raw)
In-Reply-To: <c2c2c2db-439f-5c60-068d-e53adbe960c1@intel.com>

On Wed, Jun 10, 2020 at 09:49:01AM +0800, Rong Chen wrote:
> 
> 
> On 6/10/20 8:58 AM, Fangrui Song wrote:
> > On 2020-06-10, Rong Chen wrote:
> >>
> >>
> >> On 6/10/20 1:49 AM, Fangrui Song wrote:
> >>> On 2020-06-09, Nick Desaulniers wrote:
> >>>> On Tue, Jun 9, 2020 at 6:12 AM kernel test robot <lkp@intel.com> 
> >>>> wrote:
> >>>>>
> >>>>> tree: 
> >>>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
> >>>>> master
> >>>>> head:   abfbb29297c27e3f101f348dc9e467b0fe70f919
> >>>>> commit: 10e68b02c861ccf2b3adb59d3f0c10dc6b5e3ace Makefile: support 
> >>>>> compressed debug info
> >>>>> date:   12 days ago
> >>>>> config: x86_64-randconfig-r032-20200609 (attached as .config)
> >>>>> compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
> >>>>> reproduce (this is a W=1 build):
> >>>>>         git checkout 10e68b02c861ccf2b3adb59d3f0c10dc6b5e3ace
> >>>>>         # save the attached .config to linux build tree
> >>>>>         make W=1 ARCH=x86_64
> >>>>>
> >>>>> 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 >>, old ones prefixed by <<):
> >>>>>
> >>>>>>> gcc-5: error: -gz is not supported in this configuration
> >>>>
> >>>> Hmm...I wonder if the feature detection is incomplete?  I suspect it's
> >>>> possible to not depend on zlib.
> >>>>
> >>>>> make[2]: *** [scripts/Makefile.build:277: scripts/mod/empty.o] 
> >>>>> Error 1
> >>>>> make[2]: Target '__build' not remade because of errors.
> >>>>> make[1]: *** [Makefile:1169: prepare0] Error 2
> >>>>> make[1]: Target 'prepare' not remade because of errors.
> >>>>> make: *** [Makefile:185: __sub-make] Error 2
> >>>
> >>> The output of gcc-5 -v --version on that machine may help. The
> >>> convoluted gcc_cv_ld_compress_de logic in gcc/configure.ac may be
> >>> related, but I can't find any mistake that our
> >>> CONFIG_DEBUG_INFO_COMPRESSED conditions may make.
> >>

The output of gcc-5 -dumpspecs may also be useful.

The exact Kconfig check should have been
	gcc-5 -Werror -gz=zlib -S -x c /dev/null -o /dev/null

I can't see how that would succeed if the a.c test didn't but maybe just
in case?

  reply	other threads:[~2020-06-10  3:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 13:11 gcc-5: error: -gz is not supported in this configuration kernel test robot
2020-06-09 17:28 ` Nick Desaulniers
2020-06-09 17:49   ` Fangrui Song
2020-06-10  0:30     ` [kbuild-all] " Rong Chen
2020-06-10  0:58       ` Fangrui Song
2020-06-10  1:49         ` Rong Chen
2020-06-10  3:12           ` Arvind Sankar [this message]
2020-06-10  3:23             ` Arvind Sankar
2020-06-10  4:26               ` Arvind Sankar
2020-06-10  6:37                 ` Fangrui Song
2020-06-10 19:11                   ` [PATCH] Makefile: Improve compressed debug info support detection Arvind Sankar
2020-06-10 21:27                     ` Nick Desaulniers
2020-06-10 23:30                       ` Arvind Sankar
2020-06-10 23:39                         ` Arvind Sankar
2020-06-11 20:44                           ` Nick Desaulniers
2020-06-11 21:44                             ` Arvind Sankar
2020-06-11 21:09                         ` Nick Desaulniers
2020-06-11 21:52                           ` Arvind Sankar
2020-06-11 22:03                           ` [PATCH v2] " Arvind Sankar
2020-06-11 23:38                             ` Nick Desaulniers
2020-06-14  2:21                               ` Masahiro Yamada

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=20200610031225.GA1917869@rani.riverdale.lan \
    --to=nivedita@alum.mit.edu \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=masahiroy@kernel.org \
    --cc=maskray@google.com \
    --cc=ndesaulniers@google.com \
    --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;
as well as URLs for NNTP newsgroup(s).