linux-kernel - Re: UML doesn't compile in 2.6.21

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070521210358.GB9929@c2.user-mode-linux.org>
Date:	Mon, 21 May 2007 17:03:58 -0400
From:	Jeff Dike <jdike@...toit.com>
To:	Robert Schwebel <r.schwebel@...gutronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: UML doesn't compile in 2.6.21

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/