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"

co	"cross"

do	"dynamic"

eo
fo
go
io	lIbrary
jo
ko	better for kernel objects.
mo
no
oo
qo
to
uo
vo	"variable"
wo
xo	"cross"
yo
zo	backwards-s

os