Jeffrey Walton <noloader@xxxxxxxxx> writes: > GCC silently consumes non-existent paths. So when I do the following, > I assume its a failure since I have link problems: > gcc ... -L/smb://fileserver/fileshar/dir/ -llibcoolstuff Why do you think this is a gcc problem...? AFAICT, gcc basically doesn't do any mucking about with names given to -L. You can see exactly what's happening by using "gcc -v" to see exactly how gcc invokes the linker, and then run the linker yourself (copying the linker line form the gcc -v output) using the "strace -f" or something. -Miles -- We live, as we dream -- alone....
