From: Christoph Hellwig <hch@infradead.org>
To: Kai Germaschewski <kai.germaschewski@unh.edu>
Cc: Adrian Bunk <bunk@stusta.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Andrew Morton <akpm@osdl.org>, Sam Ravnborg <sam@ravnborg.org>,
Vincent Vanackere <vincent.vanackere@gmail.com>,
keenanpepper@gmail.com,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Undefined symbols in 2.6.11-rc5-mm1
Date: Sat, 5 Mar 2005 23:57:14 +0000 [thread overview]
Message-ID: <20050305235713.GA31261@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0503051012530.20560-100000@chaos.sr.unh.edu>
On Sat, Mar 05, 2005 at 10:19:23AM -0500, Kai Germaschewski wrote:
> On Sat, 5 Mar 2005, Adrian Bunk wrote:
>
> > And this can break as soon as the "unused" object files contains
> > EXPORT_SYMBOL's.
> >
> > Is it really worth it doing it in this non-intuitive way?
>
> I don't think it non-intuitive, it's how libraries work. However, as you
> say, it is broken for files containing EXPORT_SYMBOL.
>
> The obvious fix for this case is the one that akpm mentioned way earlier
> in this thread, move parser.o into $(obj-y).
>
> It should be rather easy to have the kernel build system warn you when you
> compile library objects exporting symbols.
Or rather get rid of librarz objects completely. We manage to have explicit
depencies for 99% of our needs, do we really need a special cases that breaks
for most of it's current users?
next prev parent reply other threads:[~2005-03-06 0:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 5:37 Keenan Pepper
2005-03-02 9:23 ` Andrew Morton
2005-03-02 9:45 ` Vincent Vanackere
2005-03-02 11:24 ` Andrew Morton
2005-03-02 13:26 ` Vincent Vanackere
2005-03-02 14:00 ` Adrian Bunk
2005-03-02 16:28 ` Andrew Morton
2005-03-02 17:23 ` Valdis.Kletnieks
2005-03-02 17:34 ` Andrew Morton
2005-03-04 10:26 ` Rusty Russell
2005-03-03 13:41 ` Adrian Bunk
2005-03-04 10:23 ` Rusty Russell
2005-03-04 18:56 ` Adrian Bunk
2005-03-04 19:13 ` Adrian Bunk
2005-03-04 19:11 ` Kai Germaschewski
2005-03-04 20:28 ` Adrian Bunk
2005-03-05 5:09 ` Kai Germaschewski
2005-03-05 13:04 ` Adrian Bunk
2005-03-05 15:19 ` Kai Germaschewski
2005-03-05 15:36 ` Adrian Bunk
2005-03-05 16:36 ` Kai Germaschewski
2005-03-05 17:15 ` Adrian Bunk
2005-03-05 18:48 ` Kai Germaschewski
2005-03-05 23:58 ` Christoph Hellwig
2005-03-05 23:57 ` Christoph Hellwig [this message]
[not found] ` <4225C613.7010701@gmail.com>
2005-03-02 14:03 ` Keenan Pepper
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=20050305235713.GA31261@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=kai.germaschewski@unh.edu \
--cc=keenanpepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=vincent.vanackere@gmail.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
all inboxes | Powered by JetHome®