From: Linus Torvalds <torvalds@linux-foundation.org>
To: Frans Pop <elendil@planet.nl>
Cc: davem@davemloft.net, Andreas Schwab <schwab@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.27-rc3 - build failure: undefined reference to `.lockdep_count_forward_deps'
Date: Sat, 16 Aug 2008 17:21:31 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808161720470.3324@nehalem.linux-foundation.org> (raw)
In-Reply-To: <200808162111.23914.elendil@planet.nl>
On Sat, 16 Aug 2008, Frans Pop wrote:
> Andreas Schwab wrote:
> >> David Miller (3):
> >> lockdep: fix combinatorial explosion in lock subgraph traversal
> >
> > lockdep_count_forward_deps is only defined if CONFIG_PROVE_LOCKING but
> > used unconditionally in lockdep_proc.c.
> >
> > kernel/built-in.o: In function `.lockdep_stats_show':
> > lockdep_proc.c:(.text+0x3fea8): undefined reference to `.lockdep_count_forward_deps'
> > kernel/built-in.o: In function `.l_show':
> > lockdep_proc.c:(.text+0x401f0): undefined reference to `.lockdep_count_forward_deps'
> > lockdep_proc.c:(.text+0x40210): undefined reference to `.lockdep_count_backward_deps'
>
> I have so far been unable to build -rc3 because of this same error.
> Just tried again with current git HEAD. Failing config attached.
Ok, I think this one is fixed by df60a8441866153d691ae69b77934904c2de5e0d,
just pushed out.
Linus
next prev parent reply other threads:[~2008-08-17 0:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 2:33 Linux 2.6.27-rc3 Linus Torvalds
2008-08-13 9:24 ` Linux 2.6.27-rc3: waitpid06 Alexey Dobriyan
2008-08-13 10:03 ` Linux 2.6.27-rc3 Alan Cox
2008-08-13 22:24 ` Linus Torvalds
2008-08-13 22:35 ` Gene Heskett
2008-08-15 9:39 ` Alan Cox
2008-08-13 19:53 ` Andreas Schwab
2008-08-16 19:11 ` Linux 2.6.27-rc3 - build failure: undefined reference to `.lockdep_count_forward_deps' Frans Pop
2008-08-17 0:21 ` Linus Torvalds [this message]
2008-08-17 15:38 ` Adrian Bunk
2008-08-13 20:18 ` Linux 2.6.27-rc3 Torsten Kaiser
2008-08-13 20:23 ` Langsdorf, Mark
2008-08-14 6:04 ` Torsten Kaiser
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=alpine.LFD.1.10.0808161720470.3324@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@suse.de \
/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
all inboxes | Powered by JetHome®