This is really weird.
Kevin Walzer wrote: []
creating libtool configure: creating ./config.status config.status: creating unix-cc.mk config.status: creating unix-def.mk config.status: creating freetype-config config.status: creating ftconfig.h
So the files are created.
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
This looks still normal. []
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.
Could you look where the libtool file was created. It should be in /sw/src/freetype2-2.1.3-22/freetype-2.1.3/builds/unix/
make config.mk:21: /unix-def.mk: No such file or directory config.mk:22: /unix-cc.mk: No such file or directory
This is strange, too. It means that it does not see the file
$(TOP_DIR)/builds/unix/unix-def.mk where TOP_DIR is ".", whereas it just before saw ./builds/unix/unix.mk in the same way.
builds/freetype.mk:206: no file name for `include'
Same problem here.
It seems like your "make" is not behaving as expected. Do you have some unusual make in /usr/local/bin or in /opt/local/bin? What do you get from "make --version"?
-- Martin
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Fink-beginners mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-beginners
