From: =?unknown-8bit?Q?J=F6rn?= Engel <joern@wohnheim.fh-wedel.de>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
Arun Prasad <arun@netlab.hcltech.com>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: 2.5.51 CRC32 undefined
Date: Mon, 10 Mar 2003 14:14:22 +0100 [thread overview]
Message-ID: <20030310131422.GA525@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0303070922580.26430-100000@chaos.physics.uiowa.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1087 bytes --]
On Fri, 7 March 2003 09:27:07 -0600, Kai Germaschewski wrote:
> On 7 Mar 2003, David Woodhouse wrote:
>
> > The problem is that crc32.o isn't actually linked into the kernel,
> > because no symbols from it are referenced when the linker is asked to
> > pull in lib/lib.a
> >
> > Set CONFIG_CRC32=m. We probably shouldn't allow it to be set to 'Y' in
> > the first place., given the above.
>
> I think it'd be much nicer to just make it work, which can easily be done
> by moving the EXPORT_SYMBOL() to kernel/ksyms.c. Or, just move the entire
> file into kernel/ (which unfortunately isn't a very natural place for it.
> The real problem is that we need a lib/dont_drop_unreferenced/)
Is it just me, or does lib/lib._a_ not make too much sense? It is nice
to be speaking about the kernel library, but what are the benefits of
it being a .a instead of a .o?
Jörn
--
Don't worry about people stealing your ideas. If your ideas are any good,
you'll have to ram them down people's throats.
-- Howard Aiken quoted by Ken Iverson quoted by Jim Horning quoted by
Raph Levien, 1979
next prev parent reply other threads:[~2003-03-10 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 13:22 Arun Prasad
2003-03-07 12:40 ` David Woodhouse
2003-03-07 15:27 ` Kai Germaschewski
2003-03-07 15:43 ` Jeff Garzik
2003-03-10 13:14 ` =?unknown-8bit?Q?J=F6rn?= Engel [this message]
2003-03-07 15:49 ` Linus Torvalds
2003-03-07 15:59 ` David Woodhouse
2003-03-07 16:10 ` Jeff Garzik
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=20030310131422.GA525@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=arun@netlab.hcltech.com \
--cc=dwmw2@infradead.org \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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®