For freetype219, you had the build error
Can't open builds/unix/libtool: No such file or directory. make config.mk:25: /unix-def.mk: No such file or directory config.mk:26: /unix-cc.mk: No such file or directory
This hints also at either some strange environment or at a problem with your basic build tools, like sed or make. I have only seen this once, 6 weeks ago on fink-beginners, but unfortunately we were not able to find the reason for this error.
Ok, the full error is
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 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).
perl -pi.bak -e 's/^allow_undefined_flag.*/allow_undefined_flag=\"\"/' builds/unix/libtool
Can't open builds/unix/libtool: No such file or directory.
make
config.mk:25: /unix-def.mk: No such file or directory
config.mk:26: /unix-cc.mk: No such file or directory
make: *** No rule to make target `/unix-cc.mk'. Stop.
### execution of make failed, exit code 2
Removing build lock...
dpkg -r fink-buildlock-freetype219-2.1.9-1
(Reading database ... 68462 files and directories currently installed.)
Removing fink-buildlock-freetype219-2.1.9-1 ...
Failed: phase compiling: freetype219-2.1.9-1 failed
Ok, that "libtool" thing is indeed not there. However, earlier in the installation
configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fno-common checking if g++ PIC flag -fno-common works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... darwin7.8.0 dyld checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for g77 option to produce PIC... -fno-common checking if g77 PIC flag -fno-common works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... darwin7.8.0 dyld checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes configure: creating ./config.status config.status: creating unix-cc.mk config.status: creating unix-def.mk config.status: creating freetype-config config.status: creating freetype2.pc config.status: creating ftconfig.h
so it looks like it got created. I can't figure out by who, though: the phrase "creating libtool" does not occur anywhere.
--
Victor Eijkhout <[EMAIL PROTECTED]>, 329 Claxton, Comp Sci, UT, Knoxville TN 37996.
tel: 865 974 9308 (W), 865 673 6998 (H), 865 974 8296 (F)
http://www.cs.utk.edu/~eijkhout/
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
