[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A couple of issues with unix builds of freetype2 and ft2demos
From: |
Tom Kacvinsky |
Subject: |
Re: A couple of issues with unix builds of freetype2 and ft2demos |
Date: |
Sun, 30 Jul 2000 12:49:25 -0400 (EDT) |
Another issue:
DEC's C compiler does not like it when optimization and debugging are
specfied with the -O and -g flags. If one wants both optimization and
debugging symbols, use -g3. I have to manually remove the -O2 and -g
from the CFLAGS line in the generated config.mk.
The answer to the BSD compatible install is to use
INSTALL="/usr/bin/installbsd"
as an argument to GNU make.
Tom
On Sun, 30 Jul 2000, Tom Kacvinsky wrote:
> Hi all,
>
> I ran into a couple of issues with the freetype2 build and the
> ft2demos build for unix. This happens on Tru64 UNIX.
>
> Not finding install-sh: I have to move builds/unix/install-sh to the
> main freetype2 directory and chmod 775 on it before the install will
> work. I believe that DEC supplies a BSD compatible install, but one
> has to set the path to it before configuring...
>
> When building the ft2demos, I do not get a "shared" binary, in the
> sense that the .so file is dynamically linked. I am not sure (just
> yet) why this is happening. The binaries in bin do work, it is just
> that they are not the type of binaries I was expecting, especially
> since the binaries tucked away in bin/.lib are dynamically linked
> binaries.
>
> I have reported this to the libtool people, but it hasn't been fixed
> yet: when running gmake for configuration, supply this
>
> NM="/usr/bin/nm -B"
>
> to the arguments of gmake. Otherwise, the libtool configuration fails
> on the tests for parsing nm output. Not sure if thisis needed for the
> freetype2 build, but since I am anal about things like this, I thought
> I would report it.
>
> Tom
>