linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Laight <David.Laight@aculab.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rik van Riel <riel@surriel.com>, Mike Galbraith <efault@gmx.de>,
	Dave Hansen <dave.hansen@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Build failures with gcc 4.5 and older
Date: Wed, 15 Aug 2018 08:44:07 -0700	[thread overview]
Message-ID: <CA+55aFyeW7rqgGqOusZSz-jFP-CMH=hcyVGKhxyLxNeyBgLbqw@mail.gmail.com> (raw)
In-Reply-To: <aa4bedb7b1af45c59ff4e61f3f199287@AcuMS.aculab.com>

On Wed, Aug 15, 2018 at 5:38 AM David Laight <David.Laight@aculab.com> wrote:
>
> Never mind the version of gcc, the x86 kernel doesn't build with the
> default kernel options because the ORC unwinder hits a bug in libelf
> (in objtool) that was only fixed late last year.
>
> It isn't even obvious from the build log what has gone wrong.

Can you give more details? We should try to work around it.

It's one thing to care about a compiler that is almost a decade old.
At some point we just have to let it go.

But some libelf bug that is less than a year old is likely to bite people.

                     Linus

  reply	other threads:[~2018-08-15 15:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14 17:09 Build failures with gcc 4.5 and older Guenter Roeck
2018-08-14 17:20 ` Linus Torvalds
2018-08-14 17:36   ` Guenter Roeck
2018-08-14 20:19     ` Tony Luck
2018-08-15 16:09       ` Tony Luck
2018-08-15 16:34         ` Linus Torvalds
2018-08-16  0:27           ` Guenter Roeck
2018-08-15 16:49         ` Guenter Roeck
2018-08-14 17:48 ` Joe Perches
2018-08-19 21:23   ` Kees Cook
2018-08-20 17:46   ` Nick Desaulniers
2018-08-20 18:34     ` Linus Torvalds
2018-08-14 21:36 ` Andrew Morton
2018-08-14 22:15   ` Guenter Roeck
2018-08-14 23:02     ` Andrew Morton
2018-08-14 23:20       ` Linus Torvalds
2018-08-15  1:02         ` Guenter Roeck
2018-08-20 14:53           ` Thomas Gleixner
2018-08-20 16:00             ` Arnd Bergmann
2018-08-15 12:40 ` David Laight
2018-08-15 15:44   ` Linus Torvalds [this message]
2018-08-15 16:18     ` David Laight
2018-08-15 16:33       ` Linus Torvalds
2018-08-16  9:17         ` David Laight

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='CA+55aFyeW7rqgGqOusZSz-jFP-CMH=hcyVGKhxyLxNeyBgLbqw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=David.Laight@aculab.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=riel@surriel.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).