stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Build bot for Mark Brown <broonie@kernel.org>
Cc: kernel-build-reports@lists.linaro.org,
	linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v3.10.107 build: 2 failures 79 warnings (v3.10.107)
Date: Tue, 8 Aug 2017 14:17:26 +0200	[thread overview]
Message-ID: <20170808121726.GF27367@1wt.eu> (raw)
In-Reply-To: <E1df3JF-0007mt-EU@optimist>

Hi Mark,

On Tue, Aug 08, 2017 at 01:08:29PM +0100, Build bot for Mark Brown wrote:
> Tree/Branch: v3.10.107
> Git describe: v3.10.107
> Commit: 0e3d5747a3 Linux 3.10.107
> 
> Build Time: 27 min 6 sec
> 
> Passed:    6 / 8   ( 75.00 %)
> Failed:    2 / 8   ( 25.00 %)
> 
> Errors: 3
> Warnings: 79
> Section Mismatches: 0
> 
> Failed defconfigs:
> 	x86_64-defconfig
> 	x86_64-allnoconfig
> 
> Errors:
> 
> 	x86_64-defconfig
> /home/broonie/build/linux-stable/scripts/mod/empty.c:1:0: error: code model kernel does not support PIC mode
> /home/broonie/build/linux-stable/scripts/mod/devicetable-offsets.c:1:0: error: code model kernel does not support PIC mode
> /home/broonie/build/linux-stable/kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
> 
> 	x86_64-allnoconfig
> /home/broonie/build/linux-stable/scripts/mod/empty.c:1:0: error: code model kernel does not support PIC mode
> /home/broonie/build/linux-stable/scripts/mod/devicetable-offsets.c:1:0: error: code model kernel does not support PIC mode
> /home/broonie/build/linux-stable/kernel/bounds.c:1:0: error: code model kernel does not support PIC mode

Are you sure it's not just a toolchain issue ? I can't reproduce this one
here, it completes correctly :

  $ make [$ARGS...] bzImage
  (...)
  Setup is 15084 bytes (padded to 15360 bytes).
  System is 841 kB
  CRC 9ede5b4c
  Kernel: arch/x86/boot/bzImage is ready  (#1)

  real    0m22.291s
  user    0m53.688s
  sys     0m4.268s

  $ ll scripts/mod/empty.* 
  -rw-rw-r-- 1 willy users  54 Dec 28  2010 scripts/mod/empty.c
  -rw-rw-r-- 1 willy users 637 Aug  8 14:13 scripts/mod/empty.o

Using gcc 4.7.4 here FWIW.

Thanks,
Willy

  reply	other threads:[~2017-08-08 12:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 12:08 v3.10.107 build: 2 failures 79 warnings (v3.10.107) Build bot for Mark Brown
2017-08-08 12:17 ` Willy Tarreau [this message]
2017-08-08 14:44   ` Mark Brown
2017-08-08 14:58     ` Sven Joachim
2017-08-08 15:37     ` Willy Tarreau

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=20170808121726.GF27367@1wt.eu \
    --to=w@1wt.eu \
    --cc=broonie@kernel.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=stable@vger.kernel.org \
    /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).