From: Keith Owens <kaos@ocs.com.au>
Date: Fri, 01 Feb 2002 21:28:52 +1100
On Fri, 01 Feb 2002 11:07:42 +0100,
Horst von Brand <brand@jupiter.cs.uni-dortmund.de> wrote:
>libc.a was invented precisely to handle such stuff automatically when
>linking... if it doesn't work, it should be fixed. I.e., making .a --> .o
>is a step in the wrong direction IMVHO.
There are two contradictory requirements. crc32.o must only be linked
if anything in the kernel needs it, linker puts crc32.o after the code
that uses it. crc32.o must be linked before anything that uses it so
the crc32 __init code can initialize first.
Horst isn't even talking about the initcall issues, he's talking about
how linking with libc works in that it only brings in the routines you
actually reference.
Will you get over the initcall thing already, you must be dreaming
about it at this point. I mean really, just GET OVER IT. :-)
-
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/
This archive was generated by hypermail 2b29 : Thu Feb 07 2002 - 21:00:13 EST