linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Zhenzhong Duan <zhenzhong.duan@oracle.com>,
	David Woodhouse <dwmw@amazon.co.uk>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	x86 maintainers <x86@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Linux 4.20-rc5: Lab setup broken by build-related x86 change
Date: Wed, 05 Dec 2018 13:15:10 +0100	[thread overview]
Message-ID: <1753172.TxHhsZQBsE@aspire.rjw.lan> (raw)
In-Reply-To: <CAHk-=wizcNrsoyCM1EXQqoswMCYsJaby2iAkZb9wBAzDEhvxNg@mail.gmail.com>

On Monday, December 3, 2018 12:30:24 AM CET Linus Torvalds wrote:
> Hmm.. I'd like to say it was a normal week, but I'd be lying. rc5 is
> the biggest rc so far (with the obvious exception of rc1), and it
> looks fairly unusual in the diffstat too, with almost a third being
> arch updates. Yes, another third is drivers (normal), but even there
> almost half is in sound. The rest is tooling, mm, core networking and
> some fs updates.
> 
> So it all looks a bit odd, although none of it is hugely _alarming_.
> One of the reasons the arch side is a bit bigger than usual at this
> stage is that we got the STIPB performance regression sorted out, for
> example.

One of the changes apparently related to this broke my lab setup in which
I build everything on a central machine, export the build directory over
NFS (read-only) to some other systems and run "make modules_install" on
them from there.

After commit

commit 4cd24de3a0980bf3100c9dcb08ef65ca7c31af48
Author: Zhenzhong Duan <zhenzhong.duan@oracle.com>
Date:   Fri Nov 2 01:45:41 2018 -0700

    x86/retpoline: Make CONFIG_RETPOLINE depend on compiler support
    
    Since retpoline capable compilers are widely available, make
    CONFIG_RETPOLINE hard depend on the compiler capability.
    
    Break the build when CONFIG_RETPOLINE is enabled and the compiler does not
    support it. Emit an error message in that case:
    
     "arch/x86/Makefile:226: *** You are building kernel with non-retpoline
      compiler, please update your compiler..  Stop."
    
    [dwmw: Fail the build with non-retpoline compiler]

which is new in -rc5, the "make modules_install" step fails with the above
message, which doesn't make sense even, because the compiler on the clients
is the same as on the central machine in the lab and it can do retpolines
just fine.

Obviously this is due to the RETPOLINE_CFLAGS check added by the commit above.
Annoying that. :-)

Cheers,
Rafael


  reply	other threads:[~2018-12-05 12:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02 23:30 Linux 4.20-rc5 Linus Torvalds
2018-12-05 12:15 ` Rafael J. Wysocki [this message]
2018-12-05 14:33   ` Linux 4.20-rc5: Lab setup broken by build-related x86 change Borislav Petkov
2018-12-06 23:42     ` Rafael J. Wysocki

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=1753172.TxHhsZQBsE@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=dwmw@amazon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --cc=zhenzhong.duan@oracle.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).