Why do many buildroot library package scripts replace .lo with .o ?

Mike Frysinger vapier at gentoo.org
Fri Nov 11 15:21:34 UTC 2005


On Fri, Nov 11, 2005 at 09:10:23AM -0600, Brent Cook wrote:
> On Thursday 10 November 2005 17:53, Mike Frysinger wrote:
> > On Thu, Nov 10, 2005 at 03:31:10PM -0600, Brent Cook wrote:
> > > I have been adding packages to buildroot for a project, and noticed that
> > > in several cases, adding the magic "sed 's/\.lo/.o/g'" line on Makefiles
> > > fixed some libtool problems.
> >
> > what are you referring to ?  i dont see this in any buildroot scripts (or
> > my grep isnt showing it ...)
> 
> I looked again and appear to have mispoken; it was just berkeleydb that does 
> it. Still, what does this do? I'm currently reading the libtool documentation 
> for more insight on all this .la, .lo mess.

.la -> linker scripts
.lo -> objects built for shared libraries (usually are PIC)
.o  -> objects built for static libraries (usually not PIC)

the berkeleydb.mk looks like it's just a broken build script ... i'll
look at it later and see what's going on
-mike



More information about the uClibc mailing list