From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] RFC: Kernel tinification - kernel config reduction
Date: Wed, 13 Aug 2014 17:38:27 -0700 [thread overview]
Message-ID: <20140814003827.GA359@roeck-us.net> (raw)
In-Reply-To: <20140814001450.GW17528@sirena.org.uk>
On Thu, Aug 14, 2014 at 01:14:50AM +0100, Mark Brown wrote:
> On Wed, Aug 13, 2014 at 03:45:07PM -0700, Guenter Roeck wrote:
>
> > > The few allmodconfig/allyesconfig builds on
> > > kisskb.ellerman.id.au/kisskb/matrix/ are actually not in such a bad shape.
> > > Shall more be added?
>
> I can't get that site to load...
>
Takes forever for me, but after a minute or so I get the results.
> > I don't think there are any you could add, at least none which actually build.
>
> arm64 should work most of the time - I've been building it daily and
> reporting the results, it's also pretty clear of warnings which is good.
> There's a couple of disappointing problems at the minute though.
>
I don't get past
scripts/mod/devicetable-offsets.c: In function 'main':
scripts/mod/devicetable-offsets.c:190:1: sorry, unimplemented: function
profiling
This is with gcc 4.8.1 for aarch64, built from buildroot, and host gcc
4.8.2-19ubuntu1. Do I need a new/different compiler ?
> > arm:allmodconfig was quite useful, but it has been broken since 3.10 or so,
> > and I don't think it will ever get fixed.
>
> Why not?
>
Beats me. The longer it is broken, the more difficult it will become
to fix it, and thus less likely.
Guenter
next prev parent reply other threads:[~2014-08-14 0:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 17:29 Bird, Tim
2014-08-13 18:07 ` Guenter Roeck
2014-08-13 19:53 ` Geert Uytterhoeven
2014-08-13 22:45 ` Guenter Roeck
2014-08-14 0:14 ` Mark Brown
2014-08-14 0:38 ` Guenter Roeck [this message]
2014-08-14 15:33 ` Mark Brown
2014-08-14 7:49 ` Geert Uytterhoeven
2014-08-14 16:39 ` Mark Brown
2014-08-14 7:40 ` Geert Uytterhoeven
2014-08-14 8:50 ` Guenter Roeck
2014-08-14 9:02 ` Geert Uytterhoeven
2014-08-15 11:04 ` Guenter Roeck
2014-08-14 19:57 ` Stefan Hengelein
2014-08-13 19:19 ` josh
2014-08-14 16:30 ` Tim Bird
2014-08-14 17:17 ` Josh Triplett
2014-08-14 16:03 ` Christoph Lameter
2014-08-14 18:54 ` Jan Kara
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=20140814003827.GA359@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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