08 October 2007

is not a symbolic link SOLVED

Another minor issue is finally fixed. A number of *.so.* files--some in /usr/lib, most in /usr/local/lib--got flagged as not a symbolic link during compilation. Well, I finally got around to looking at these files. It turns out that in each case, the not a symbolic link file was identical to another file in the same directory with a slightly longer name--for example, libORBit.so.3 and libORBit.so.3.0.1, or something like that. I moved the former file to a safe place (in case it was hard-linked or something else that might cause trouble if deleted), then created a symlink: sudo ln -s /usr/local/lib/libORBit.so.3.0.1 /usr/local/lib/libORBit.so.3. And now all is beautiful. ALSO: Often during compilation, gcc vomits out a warning that [FILENAME] seems to be moved; as long as this doesn't hurt the compilation (it usually does not), then this is an ignorable warning due to a minor bug in libtool or gcc. Cool.


Post a Comment

<< Home