From: Linus Torvalds <email@example.com>
To: David Laight <David.Laight@aculab.com>
Cc: Guenter Roeck <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>,
Rik van Riel <firstname.lastname@example.org>, Mike Galbraith <email@example.com>,
Dave Hansen <firstname.lastname@example.org>,
Andrew Morton <email@example.com>
Subject: Re: Build failures with gcc 4.5 and older
Date: Wed, 15 Aug 2018 09:33:32 -0700 [thread overview]
Message-ID: <CA+55aFwwon2MLEhw-ERLskWed8b58NseLYF-7OOQhhjMcD-A6A@mail.gmail.com> (raw)
On Wed, Aug 15, 2018 at 9:16 AM David Laight <David.Laight@aculab.com> wrote:
> > But some libelf bug that is less than a year old is likely to bite people.
> See https://lkml.org/lkml/2017/9/10/186 for the libelf fix.
> It isn't anything like as rare as those emails suggest.
> An 'allmodconfig' build fails on a lot of object files after 4.15-rc9.
Ok, but that patch that fixes it was merged a long time ago already.
See commit 97dab2ae7e84 ("objtool: Fix object file corruption")
So I'm a bit confused by your issue. The thing you point to from last
year was literall fixed and committed to the tree in a couple of days
> When I fell over the problem I found a few reports on the ubuntu lists
> but they all just said the ubuntu version was unsupported.
> There is this patch I did https://lkml.org/lkml/2018/7/26/266 that got
> no comments.
> But really something needs to be done to objtool.
I think you need to make a report about the exact problem with objtool
and your issue.
Not on the ubuntu lists, but to Josh.
next prev parent reply other threads:[~2018-08-15 16:33 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
2018-08-15 16:18 ` David Laight
2018-08-15 16:33 ` Linus Torvalds [this message]
2018-08-16 9:17 ` David Laight
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).