Date: Wed, 2 Mar 2005 08:28:46 -0800
From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: kai@germaschewski.name, sam@ravnborg.org, rusty@rustcorp.com.au,
       vincent.vanackere@gmail.com, keenanpepper@gmail.com,
       linux-kernel@vger.kernel.org
Subject: Re: Undefined symbols in 2.6.11-rc5-mm1
Message-Id: <20050302082846.1b355fa4.akpm@osdl.org>
In-Reply-To: <20050302140019.GC4608@stusta.de>
References: <422550FC.9090906@gmail.com>
	<20050302012331.746bf9cb.akpm@osdl.org>
	<65258a58050302014546011988@mail.gmail.com>
	<20050302032414.13604e41.akpm@osdl.org>
	<20050302140019.GC4608@stusta.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1180
Lines: 29

Adrian Bunk <bunk@stusta.de> wrote:
>
> > In lib/Makefile, remove parser.o from the lib-y: rule and add
>  > 
>  > obj-y	+= parser.o
> 
>  This I didn't find.
> 
>  Is it really the intention to silently omit objects that are not 
>  referenced or could this be changed?

In some cases, yes, it it desirable.  For example, lib/extable.c provides a
default implementation of an exception table sorter but if the architecture
defies its own, the linker will skip the default version in lib/.

At least, that's what the thinking was a few years ago.  But it's such a
special-case that we can probably forget about it and just drive the build
and linkage with config now.

>  Why doesn't an EXPORT_SYMBOL create a reference?

It does, but that reference is within the same compilation unit as the
definition.  IOW: there are no references to the symbol which are external
to the symbol's file.   There's still nothing to drag that file in.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/