From: Thomas Meyer <thomas@m3y3r.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.14-rc3
Date: Tue, 3 Oct 2017 11:27:27 +0200 [thread overview]
Message-ID: <20171003092727.dqcfgil7wty4mdus@olymp> (raw)
In-Reply-To: <87vajwd1yh.fsf@concordia.ellerman.id.au>
On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
> Geert Uytterhoeven <geert@linux-m68k.org> writes:
>
> > Hi Thomas,
> >
> > On Mon, Oct 2, 2017 at 4:11 PM, Thomas Meyer <thomas@m3y3r.de> wrote:
> >> On Mon, Oct 02, 2017 at 11:49:33AM +0200, Geert Uytterhoeven wrote:
> >>> Below is the list of build error/warning regressions/improvements in
> >>> v4.14-rc3[1] compared to v4.13[2].
> >>
> >> a question regarding the um-defconfig build:
> >> http://kisskb.ellerman.id.au/kisskb/target/2974/
> >>
> >> The error thrown looks like a libc installation error. can this be fixed
> >> on the build server?
> >
> > I'll let Michael answer that question...
>
> Thanks for the report.
>
> I think the problem is simply that the toolchain has no libc, so it
> can't build UML (?).
Yes, UML needs a libc.
>
> I've switched it to using one of the toolchains from Free Electrons,
> which is built with glibc, and that seems to be working:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
>
>
> Let me know if that's no good.
Cool, excellent! Look good.
Is it also possible to add an allyesconfig and allmodconfig for UML?
Many thanks for looking into this.
with kind regards
thomas
>
> cheers
next prev parent reply other threads:[~2017-10-03 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 9:49 Build regressions/improvements in v4.14-rc3 Geert Uytterhoeven
2017-10-02 9:55 ` Geert Uytterhoeven
2017-10-02 14:11 ` Thomas Meyer
2017-10-02 14:26 ` Geert Uytterhoeven
2017-10-03 9:18 ` Michael Ellerman
2017-10-03 9:27 ` Thomas Meyer [this message]
2017-10-05 2:43 ` Michael Ellerman
2017-10-05 18:17 ` Thomas Meyer
2017-10-07 22:50 ` Michael Ellerman
2017-10-08 6:45 ` Thomas Meyer
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=20171003092727.dqcfgil7wty4mdus@olymp \
--to=thomas@m3y3r.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.