On Mar 28, 2006, at 5:34 AM, Michael Livshin wrote:
Nikodemus Siivola nikodemus@random-state.net writes:
Michael Livshin gmane@cmm.kakpryg.net writes:
also, make sure your system has libfreetype.so (some Debian installations lack it, so you'll have to make a symlink libfreetype.so -> libfreetype.so.6).
Lack of a symlink like that is usually an indication of a missing - dev package.
oh. right you are!
still wondering what exactly the logic behind this is, --m
The symlink is only necessary if you're going to be linking against the library as ld won't resolve -lfreetype to libfreetype.so.someversion (and if you're missing the -dev package, you don't have headers either). SBCL acts more like a linker than a user binary in this case - the SBCL runtime itself is not linked against this library, so it must find and load it at runtime.
It would be an interesting project to munge up the runtime when doing save-lisp-and-die :executable t to link to any necessary alien libraries. One could also put the core in a segment of the binary instead of dumping a technically invalid ELF image, too. -- Brian Mastenbrook http://brian.mastenbrook.net/ brian@mastenbrook.net