public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: UML doesn't compile in 2.6.21
Date: Mon, 21 May 2007 17:03:58 -0400	[thread overview]
Message-ID: <20070521210358.GB9929@c2.user-mode-linux.org> (raw)
In-Reply-To: <20070516224938.GN12319@pengutronix.de>

On Thu, May 17, 2007 at 12:49:38AM +0200, Robert Schwebel wrote:
> Jeff,
> 
> Any idea how this could happen? I'm trying to build 2.6.21 for
> ARCH=um, and the linker stage explodes here:
> 
>   CHK     include/linux/compile.h
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> lib/lib.a(bug.o): In function `find_bug':
> bug.c:(.text+0x171): undefined reference to `__start___bug_table'
> bug.c:(.text+0x177): undefined reference to `__stop___bug_table'
> bug.c:(.text+0x180): undefined reference to `__start___bug_table'
> bug.c:(.text+0x193): undefined reference to `__stop___bug_table'

No, I don't.  The bug_table symbols are rather unconditionally defined
in asm-generic/vmlinux.lds.h.  This can't be affected by any config
settings that I can see, let alone module support.  Further, the
config I always build has modules enabled, and I've never seen this.

Can you try starting over with an mrproper and see if you can
reproduce it?

				Jeff

-- 
Work email - jdike at linux dot intel dot com

      parent reply	other threads:[~2007-05-21 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 22:49 UML doesn't compile in 2.6.21 Robert Schwebel
2007-05-17  1:11 ` Rob Landley
2007-05-17 21:05   ` Robert Schwebel
2007-05-17 21:12     ` Robert Schwebel
2007-05-18  7:25     ` Rob Landley
2007-05-21 21:03 ` Jeff Dike [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=20070521210358.GB9929@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r.schwebel@pengutronix.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