public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	x86@kernel.org, "H.J. Lu" <hjl.tools@gmail.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	linux-kbuild@vger.kernel.org
Subject: Re: kbuild: Fail if gold linker is detected
Date: Tue, 16 Jul 2019 20:13:24 +0200	[thread overview]
Message-ID: <20190716181324.GA41555@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1907161757490.1767@nanos.tec.linutronix.de>


* Thomas Gleixner <tglx@linutronix.de> wrote:

> On Tue, 16 Jul 2019, Ingo Molnar wrote:
> 
> > 
> > * Thomas Gleixner <tglx@linutronix.de> wrote:
> > 
> > > The gold linker has known issues of failing the build in random and
> > > predictible ways. H.J. stated:
> > 
> > s/predictable/unpredictable?
> 
> No. It fails randomly, but also predictable. Enable X32 support on 64bit
> and it fails the VDSO build. That's been the case for years.

Then please make this a bit more apparent, such as:

 "The gold linker has known issues of failing the build in random
  but also in more predictible ways."

or so?

Thanks,

	Ingo

  reply	other threads:[~2019-07-16 18:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 12:47 kbuild: Fail if gold linker is detected Thomas Gleixner
2019-07-16 12:54 ` Peter Zijlstra
2019-07-16 14:40 ` Ingo Molnar
2019-07-16 15:59   ` Thomas Gleixner
2019-07-16 18:13     ` Ingo Molnar [this message]
2019-07-16 18:46       ` Linus Torvalds
2019-07-16 18:52       ` Theodore Y. Ts'o
2019-07-29 17:06     ` Bernd Petrovitsch
2019-07-16 17:06 ` Nathan Chancellor
2019-07-16 18:59   ` Thomas Gleixner
2019-07-16 19:47     ` [PATCH v2] " Thomas Gleixner
2019-07-16 19:59       ` Nathan Chancellor
2019-07-16 21:20         ` Mike Lothian
2019-07-16 22:25           ` Thomas Gleixner
2019-07-16 23:37             ` Theodore Y. Ts'o
2019-07-17  6:54       ` Masahiro Yamada
2019-07-17  7:57         ` Thomas Gleixner
2019-07-20  9:12           ` Mike Lothian
2019-07-20  9:34             ` Thomas Gleixner
2019-07-20 10:13               ` Mike Lothian
2019-07-20 10:54                 ` Thomas Gleixner
2019-07-20 10:59                   ` Mike Lothian
2019-07-23  1:30             ` Masahiro Yamada
2019-07-23  6:41               ` Thomas Gleixner
2019-07-23  8:17                 ` Thomas Gleixner
2019-07-29  2:27                   ` 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=20190716181324.GA41555@gmail.com \
    --to=mingo@kernel.org \
    --cc=hjl.tools@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --cc=yamada.masahiro@socionext.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