Subject: Re: Reworking the .o suffices in our Makefiles
To: Luke Mewburn <lukem@NetBSD.org>
From: Bill Sommerfeld <firstname.lastname@example.org>
Date: 10/20/2004 23:24:18
On Wed, 2004-10-20 at 21:50, Luke Mewburn wrote:
> Thoughts / other comments?
because this is an A->B B->C rename, we run the risk that an old .lo
file in somebody's build tree will be linked into a shared library even
if we leave some number of months or years between the two renames.
Are we confident that this will always be caught at shared-library build
time on a non-cross build?
Are all .ho bits built non-PIC?
Random alternatives to using .lo:
bo +: the various words for library in german, italian, spanish,
french, and aybe a few other languages all start with "b".
-: american colloquialism for (foul) "body odor"
ko better for kernel objects.