Re: [Freetype] Re: Build errors

[Werner LEMBERG]

> 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...

Can you investigate this further?  And please tell us what your
LDFLAGS variable contains.  Maybe we can simulate your problem.

> 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.

I had a feeling that you answer like that...


    Werner