RE: [ft] Linux newbie having FreeType installation problems

[Charlie Fiskeaux II]

Ok, the configure script ran fine, and 'make' and 'make install' seem to have worked, but it doesn't seem to work with the GD Library (I want to use PHP to overlay text on images using TrueType fonts).

 

I've done some research, and here's what I've done so far.

My version of the GD Library is 2.0.13, bundled with PHP 4.3.4. So I go to /usr/local/src/apachebld/php-4.3.4 and run ./configure with all the options shown in my phpinfo() (which already has GD enabled) and add '--enable-gd-native-ttf' and '--with-freetype-dir'. It seems to work, because when I scroll up to see the output, it says that truetype string functions have been enabled, and it is detecting FreeType 2. I then do 'make' and 'make install' to rebuild PHP, and then go to /usr/local/src/apachebld/apache_1.3.29_std/src/support and run 'apachectl restart' to restart Apache. But when I view my phpinfo() again, nothing has changed.

 

Do I need to rebuild Apache, too? If so, how do I find out what options were used to build it originally?

Charlie Fiskeaux II
Interactive Media Developer
Cre8tive Group
cre8tivegroup.com
859/858-9054 x29

 

---

From: Turner, David [mailto:address@hidden
Sent: Friday, October 21, 2005 3:24 AM
To: Charlie Fiskeaux II; Freetype Mailing List
Subject: RE: [ft] Linux newbie having FreeType installation problems

Hello,

 

Don't unzip on Windows, this will likely change the end-of-line convention used by text files, which is

probably why the configure scripts don't seem to work.

 

For example, I can imagine that when you type ./configure, your command shell reads the file then

tries to launch a program named "/bin/sh\r" instead of "/bin/sh". It then complains that it doesn't

find any.

 

Unfortunately, most text editors don't show the "\r", since they handle the different EOL conventions

transparently.

 

there is nothing wrong from using /bin/sh as a link to /bin/bash or anything else. just check for proper

permissions, then everything should _just_ work.

 

in other words, trying uncompressing the archive on Unix directly. If you absolutely need to do it

on Windows, use a program like 7-zip (www.7-zip.com) which will not automatically change the EOL

convention on text files.

 

Dropping WinZip is _always_ a good idea anyway, there are so many free alternatives that work just

as well.

 

Hope this helps,

 

- David Turner

- The FreeType Project  (www.freetype.org)

 

 

-----Message d'origine-----
De : address@hidden [mailto:address@hiddenDe la part de Charlie Fiskeaux II
Envoyé : vendredi 21 octobre 2005 00:55
À : Freetype Mailing List
Objet : [ft] Linux newbie having FreeType installation problems

I've using Linux lightly for a year or two on our server at work. I know how to get around it ok, but when it comes to stuff like having to compile/install software on it, I'm out of my league. I've been trying to install FreeType for use with PHP's GD library, but I've been having problems. I'll describe my process:

First, I went to savannah.nongnu.org/download/freetype and downloaded 'freetype-2.1.10.tar.gz'. I unzipped it with Winzip 9 and FTP'd the folder up to my server.

Second, I SSH'd into my server, switched to the root user, moved the folder I had uploaded to /freetype, and then copied it to /usr/local/freetype. I then changed the owner and group to root and made sure all the files had executable permissions.

Third, I ran ./configure.
It gave me the message:
Bash: ./configure: bad interpreter: No such file or directory
So after a Google search and some poking around on the server I see that the shebang at the top of the configure file is pointing to /bin/sh, but my /bin/sh is just a link to /bin/bash. So I change the shebang in the configure file to point to /bin/bash.

Fourth, I run ./configure again.
This time I get the message:
cd builds/unix; ./configure
/bin/sh: ./configure: bad interpreter: No such file or directory
make: *** [builds/unix/unix-def.mk] Error 126
So I go to builds/unix and use pico to edit the configure file there to change the shebang to /bin/bash and change all other references to /bin/sh so they point to /bin/bash now.

Fifth, I run ./configure again.
I get another message:
cd builds/unix: ./configure
configure: error: cannot run /bin/bash ./config.sub
make: *** [builds/unix/unix-def.mk] Error 1
So I go and edit builds/unix/config.sub and change all of its references from /bin/sh to /bin/bash. While I'm there, I do the same for config.guess also.

Sixth, I run ./configure again.
It seems like success! I get a whole long list of things it's checking for, and in the middle it asks, "mv: overwrite 'libtool'?" So I choose yes. It writes some files and then asks me, "rm: remove 'ftconfig.tmp'?" So I again choose yes. So then it spits out the following config info:

Freetype build system -- automatic system detection
The following settings are used:

        platform                                unix
        compiler                                cc
        configuration directory         ../builds/unix
        configuration rules                     ../builds/unix/unix.mk

If this does not correspond to your system or settings please remove the file 'config.mk' from this directory and then read the INSTALL file for help.

Otherwise, simply type 'make' again to build the library, or 'make refdoc' to build the API reference (the latter needs python).

make: Nothing to be done for 'unix'.
And that's it for that step.

Seventh, I run 'make'.
Now I'm getting stuff that I don't know what to do with:
./builds/unix/libtool --mode=compile gcc -pedantic -ansi -I/usr/local/freetype/objs -I.builds/unix -I/usr/local/freetype/include -c -Wall -g -02 -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DDARWIN_NO_CARBON -DFT_CONFIG_CONFIG_H="<ftconfig.h>" -o /usr/local/freetype/objs/ftsystem.lo builds/unix/ftsystem.c

: command not foundol:
: command not foundol:
: command not foundol:
/bin/sed: -e _expression_ #1, char 10: Unknown option to 's'
: command not foundol:
: command not foundol:
: command not foundol:
./builds/unix/libtool: line 405: syntax error near unexpected token 'elif'
'/builds/unix/libtool: line 405: 'elif test "X$1" = X--fallback-echo; then
Make *** [/usr/local/freetype/objs/ftsystem.lo] Error 2

What in the world is the problem? Does anyone have any ideas? I really don't know how to troubleshoot this.

Charlie Fiskeaux II

***********************************************************************************
Information contained in this email message is confidential and may be privileged, and is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the address@hidden and destroy the original message.
***********************************************************************************