drmarkandersen wrote:
Still no luck.
When I run 'sudo ldconfig -v', the output includes the line: libgcc_s.so.1 -> libgcc_s.so.1 (under /lib/i386-linux-gnu:), which indicates to me that the system knows where that file is. In addition, running 'ldd t-engine' yields (among lots of other output) 'libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb741c000)', so it looks to me like t-engine should know where libgcc_s.so.1 is, since /lib/i386-linux-gnu is the actual directory where libgcc_s.so.1 lives.
I agree with this, except I'm not sure that it has been verified that /lib/i386-linux-gnu is the actual directory where libgcc_s.so.1 lives.
I mention a way to verify that below.
Quote:
I'm tempted to just copy libgcc_s.so.1 to the other locations listed in your 'find' output and see if that fixes the problem.
I recommend you don't do that. Quite aside from anything else, copying system files tends to lead to trouble when you upgrade and the copies remain at the old version.
Instead, if you want to pursue that path, I suggest creating a symlink to the actual file. This would involve two steps.
1. Make sure you know what the real path is that you should link to: run
realpath /lib/i386-linux-gnu/libgcc_s.so.1. The real path probably -is- /lib/i386-linux-gnu/libgcc_s.so.1 , but I wouldn't guarantee it.
2.
cd /usr/lib, then
sudo ln -s REALPATH, where REALPATH is the path generated by step 1.
I do not recommend doing anything with directories other than /usr/lib or /lib -- these are generally the only two plausible system directories that libraries are placed in.
That said, since ToME seems to incorporate its own copy of pthreads, you might consider placing a similar symlink in the same directory that you have installed ToME into. (If this fixes the problem, I would strongly suspect that there is something a bit wrong with ToME's copy of pthreads.)
Quote:
On the other hand, I'm not at all tempted to try compiling t-engine from source; I'd be way out of my depth there.
Personally, I have the policy that it is always worth a try, but in this case I don't believe it's at all likely that recompiling will change anything, since the problem seems to be with the way Ubuntu has set up the system.