From: Rusty Russell <rusty@rustcorp.com.au>
To: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: lib-y vs EXPORT_SYMBOL: who wins?
Date: Tue, 25 Sep 2007 15:07:44 +1000 [thread overview]
Message-ID: <1190696865.27805.317.camel@localhost.localdomain> (raw)
Various files under lib/ are linked into a .a so they only get linked if
needed. But many of these functions are also EXPORT_SYMBOL()ed.
This doesn't really make sense: if it's exported it really needs to be
present. Certain configurations can hit this (lguest uses kasprintf,
and can be a module).
We could do something hacky and try to figure out if any modules need
the symbols, which screws modules built later, but is no worse than a
CONFIG_-based solution.
Or to we just move all the exported functions out of the .a?
Cheers,
Rusty.
next reply other threads:[~2007-09-25 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 5:07 Rusty Russell [this message]
2007-09-25 6:13 ` Sam Ravnborg
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=1190696865.27805.317.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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®