public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.25-rc1, weird build error
Date: Wed, 13 Feb 2008 22:07:26 +0100	[thread overview]
Message-ID: <20080213210726.GA13773@uranus.ravnborg.org> (raw)
In-Reply-To: <20080212070448.GA20033@elte.hu>

On Tue, Feb 12, 2008 at 08:04:48AM +0100, Ingo Molnar wrote:
> 
> i've got a build log from a weird build error below:
> 
>   LD      init/built-in.o
> distcc[12023] ERROR: compile (null) on localhost failed
> make: *** [vmlinux.o] Error 1
> make: *** Waiting for unfinished jobs....
>   LD      .tmp_vmlinux1
> 
> but there's no actual error visible in the logs. On a second attempt, it 
> built just fine. (unfortunately erasing most evidence of the previous 
> failure.) This happened after a rather long randconfig build series so i 
> doubt it's readily reprodicible.
> 
> any ideas? Is this something benign? Or should i start doing all builds 
> with V=1, in the hope of catching more information?

building vmlinux.o were moved up in the dependency chain so we started
to build it before the kallsym stuff. This was done to let modpost
report section mismatch bugs even when the final link failed.

Originally I had expected the dependency of $(kallsyms.o) to
cover this but it turns out that we need to be even more explicit.
With attached patch this is addressed and I now get the desired
behaviour.
The drawback is that the final steps are serialized and we seems
to be pretty CPU bound doing all the linking stuff.

I assume the patch is safe but a bit testing from your side
is appreciated.
That randconfig qa thing is excellent to find these subtle things.

	Sam

diff --git a/Makefile b/Makefile
index c162370..bec8da3 100644
--- a/Makefile
+++ b/Makefile
@@ -810,7 +810,9 @@ endif
 	$(Q)rm -f .old_version
 
 # build vmlinux.o first to catch section mismatch errors early
-$(kallsyms.o): vmlinux.o
+ifdef CONFIG_KALLSYMS
+.tmp_vmlinux1: vmlinux.o
+endif
 vmlinux.o: $(vmlinux-lds) $(vmlinux-init) $(vmlinux-main) FORCE
 	$(call if_changed_rule,vmlinux-modpost)
 

      parent reply	other threads:[~2008-02-13 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12  7:04 2.6.25-rc1, weird build error Ingo Molnar
2008-02-12  7:12 ` Roland McGrath
2008-02-12  7:39   ` Ingo Molnar
2008-02-12  7:51     ` Roland McGrath
2008-02-12 10:02 ` Sam Ravnborg
2008-02-13 21:07 ` Sam Ravnborg [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=20080213210726.GA13773@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=roland@redhat.com \
    /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