On Wednesday 09 January 2002 14:29, Tom Whiting wrote: > >>It should read > >>/usr/bin/ld > >>not > >>/usr//bin/ld > > Hate to say it, but in this case you be wrong, absolutely completely and > totally wrong.. Linux/unix recognizes /usr//bin/ld exactly the same as > /usr/bin/ld. > As for why the packages aren't responding, it could be because of the > fact that your /etc/ld.so.conf doesn't point to that directory. If it > does (and I've had even that not work out occasionally), then you're not > gonna have a lot of luck getting it in unfortuantely > > ------------------------------------------- > TJW: Head tech, Dreamless Realms Mud > Personal: http://twhiting.kyndig.com > Mud: http://drealms.kyndig.com > Snippets http://drealms.kyndig.com/snippets > Telnet telnet://drealms.kyndig.com:9275 > The OLC2 Pages http://olc.kyndig.com > -------------------------------------------
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. -- Bobby "Chil" Bailey | "The only source of knowledge is Coders' Forum Moderator | experience." -- Albert Einstein Coder's Repository Admin | Dark Saghani! http://saghani.com http://www.kyndig.com/ | #Rom on IRC! irc.acestar.org:6667 Welcome To Your New Addiction | PGP Keys: http://chil.kyndig.com/pgp
