Hey >Something that's yet to be mentioned (publicly at least) is that you can >easily tell gcc explicitely where to look for libraries. If you KNOW a >library is in a certain directory, just pass -L/path/to/the/library to gcc. >gcc -o mud file1.o file2.o file3.o -L/home/chil/lib -lmud_network >Handy for those times when you're using non-standard libs that aren't >installed at the system level, at least. >The same goes for non-standard include directories as well, only with -I >gcc -c -Wall -I/home/chil/include -o file1.o file.c >Sometimes one of the above can help when all else fails.
Yup, that's what I ended up doing. But the fault was not mine. It was aterm's configure script that was broken. Thanx all -- Francois Rossouw UCS
