From: Bob Tracy <rct@gherkin.frus.com>
To: Matt Turner <mattst88@gmail.com>
Cc: Debian Alpha Mailing List <debian-alpha@lists.debian.org>,
linux-alpha <linux-alpha@vger.kernel.org>,
Michael Cree <mcree@orcon.net.nz>, Helge Deller <deller@gmx.de>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [BUG] 4.13.0 kernel build error on Alpha
Date: Sun, 10 Sep 2017 22:23:40 -0500 [thread overview]
Message-ID: <20170911032340.GA26971@gherkin.frus.com> (raw)
In-Reply-To: <20170911031641.GA26870@gherkin.frus.com>
On Sun, Sep 10, 2017 at 10:16:41PM -0500, Bob Tracy wrote:
> On Sun, Sep 10, 2017 at 07:59:40PM -0700, Matt Turner wrote:
> > On Sun, Sep 10, 2017 at 3:34 PM, Bob Tracy <rct@gherkin.frus.com> wrote:
> > > Here we go again :-(. Tool versions as follows:
> > > (...)
> > >
> > > MODPOST vmlinux.o
> > > WARNING: EXPORT symbol "callback_setenv" [vmlinux] version generation failed, symbol will not be versioned.
> > > (...)
> > > WARNING: modpost: Found 24 section mismatch(es).
> > > To see full details build your kernel with:
> > > 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> >
> > All of this is fixed by
> >
> > commit 873f9b5bcbf27f6e89e1879714abe4532cacf5d7
> > Author: Ben Hutchings <ben@decadent.org.uk>
> > Date: Wed Jul 19 01:01:16 2017 +0100
> >
> > alpha: Restore symbol versions for symbols exported from assembly
>
> I guess that commit hasn't made it into Linus' tree :-(. If the patch
> is short, please forward if you would be so kind. Many thanks in
> advance.
Never mind. Linus pulled it five days ago as I type this. The fixes
obviously didn't make it in time for 4.13-final, but should be in 4.14.
--Bob
next prev parent reply other threads:[~2017-09-11 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 22:34 [BUG] 4.13.0 kernel build error on Alpha Bob Tracy
2017-09-11 2:59 ` Matt Turner
2017-09-11 3:16 ` Bob Tracy
2017-09-11 3:23 ` Bob Tracy [this message]
2017-09-11 6:02 ` Michael Cree
2017-09-12 4:06 ` Bob Tracy
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=20170911032340.GA26971@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=deller@gmx.de \
--cc=linux-alpha@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
/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