From: Guenter Roeck <linux@roeck-us.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: Build failures due to commit ea4054a2384 (handle huge number of modules)
Date: Sun, 12 May 2013 20:28:17 -0700 [thread overview]
Message-ID: <20130513032817.GA17184@roeck-us.net> (raw)
In-Reply-To: <87ehdb39gu.fsf@rustcorp.com.au>
On Mon, May 13, 2013 at 11:52:09AM +0930, Rusty Russell wrote:
> Guenter Roeck <linux@roeck-us.net> writes:
> > Attached is a failing configuration for x86_64. Note that
> > drivers/staging/android/logger.c fails to build with this configuration,
> > so you have to build it with make -i to see the problem.
> >
> > Looking through my logs, it seems that the problem may be related to other
> > build errors. At least in my latest nightly builds there was always some other
> > build error when this happened.
>
> That would explain it. Perhaps some kind of race?
>
> I can't see this as a real problem, though.
>
It reduces the value of "make -i" significantly, as it creates lots of false
compile errors. If you think that is not a problem, fine with me. I can (and do)
filter the resulting errors from my auto-build scripts by now . That may cause
the scripts it to miss some real errors, but after all I can only do so much.
And it does seeem as if no one else cares, or maybe I am the only one seeing
the problem, so I guess you are right.
Thanks,
Guenter
prev parent reply other threads:[~2013-05-13 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130508213007.GA11946@roeck-us.net>
2013-05-09 0:56 ` Build failures due to commit ea4054a2384 (handle huge number of modules) Rusty Russell
2013-05-09 4:15 ` Guenter Roeck
2013-05-13 2:22 ` Rusty Russell
2013-05-13 3:28 ` Guenter Roeck [this message]
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=20130513032817.GA17184@roeck-us.net \
--to=linux@roeck-us.net \
--cc=fengguang.wu@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox