libGLC.so.0: cannot open shared object file: No such file or directory

[Lasair]

First of all - hello world!

I ran across this idiocy after a rather problem-free compilation from the trunk. Or rather a bundle of idiocies.

First of all, although warzone2100 is in /usr/local/bin/ (it is even auto-completed in the command line) after calling it I got bash: warzone2100: command not found. It could be still invoked from the location in question, only to display (I managed to solve the first 'problem' in the mean time):

lasair@lap:~$ warzone2100
warzone2100: error while loading shared libraries: libGLC.so.0: cannot open shared object file: No such file or directory

on the other hand

lasair@lap:~$ ls /usr/local/lib/libGLC*
/usr/local/lib/libGLC.a  /usr/local/lib/libGLC.la  /usr/local/lib/libGLC.so  /usr/local/lib/libGLC.so.0

it seems to me that everything should be fine...

I looked the board through only to find a this issue mentioned in an already solved problem. Here.

Suggestions?

Running Ubuntu 7.10

[edit] the link provided leads to a similar not the same issue...

[Per]

I guess you don't have /usr/local/lib listed in /etc/ld.conf? Try running /sbin/ldconfig /usr/local/lib as root.

Does Ubuntu run SELinux?

[Lasair]

The problem seems to have solved itself. After system restart. In fact, I can't even find an evidence that there was a problem at all... Things like this make me consider the possibility of a malicious conscience within my CPU.

I guess you don't have /usr/local/lib listed in /etc/ld.conf? Try running /sbin/ldconfig /usr/local/lib as root.

I checked that. Everything was fine.

Does Ubuntu run SELinux?

To the best of my knowledge - no

Still - thanks for wasting a bit of your time.

[DevUrandom]

The problem seems to have solved itself. After system restart. In fact, I can't even find an evidence that there was a problem at all... Things like this make me consider the possibility of a malicious conscience within my CPU.

Probably Ubuntu regenerates the ld.so.cache on reboot?

The fact that you couldn't run might have been because /usr/local/bin was not listed in $PATH. (Maybe Ubuntu also adapted that when rebooting?)

[Giel]

Probably Ubuntu regenerates the ld.so.cache on reboot?

Seems reasonable, yes.

The fact that you couldn't run might have been because /usr/local/bin was not listed in $PATH. (Maybe Ubuntu also adapted that when rebooting?)

I'd say that this is quite unlikely, since AFAIK even a default Ubuntu installation already has /usr/local/bin created (I know Debian has it). Obviously it isn't impossible though.