Re: [Freetype] Re: Build errors

[Mike Richards]

On Mon, 06 Dec 2004 01:01:46 +0100 (CET), Werner LEMBERG <address@hidden> wrote:
> 
> 
> > Ever since version 2.1.5 I've been unable to compile freetype. Here
> > is the error I got today trying to compile 2.1.9:
> >
> > libtool: link: `/home/mike/build/objs/ftsystem.lo'
> >                is not a valid libtool object
> > make: *** [/home/mike/build/objs/libfreetype.la] Error 1
> >
> > I thought maybe it was a libtool problem, so I upgraded from 1.5.6 to
> > 1.5.10 but it didn't make any difference. The rest of the system is
> > linux 2.4.26, gcc 3.2.3, and glibc 2.2.5.
> 
> I see this the first time.  You have typed `configure; make', haven't
> you?

Actually, I had also redefined LDFLAGS to get the linker to grab libs
from a non-standard directory. So, my 'make' command actually looked
like 'make cc="gcc ${LDFLAGS}"'.

When I took out the custom LDFLAGS setting, the compile worked fine.

As it happens, I set a custom LDFLAGS on most every package I build (I
have some libraries in odd places sometimes), and this is the only one
that I can recall having trouble with. Makes me think there is
something wrong here...

A data point that may mean something: When the compile failed,
ftsystem.lo was not an ASCII file as you suggested, but rather a
binary file. And running 'strings' on it came up totally empty.

> 
> Can you show us the contents of ftsystem.lo?  It should be an ASCII
> file, looking similar to this:
> 
>   # /home/ft/freetype2.zzz/objs/ftsystem.lo - a libtool object file
>   # Generated by ltmain.sh - GNU libtool 1.5.6 (1.1220.2.94 2004/04/10 
> 16:27:27)
>   #
>   # Please DO NOT delete this file!
>   # It is necessary for linking the library.
> 
>   # Name of the PIC object.
>   pic_object='.libs/ftsystem.o'
> 
>   # Name of the non-PIC object.
> 
>     Werner
> 
> _______________________________________________
> Freetype mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/freetype
>