[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 3.1.12 is imminent
On Fri, 23 Apr 1999, Dana Booth wrote:
> On Fri, 23 Apr 1999, Ulric Eriksson wrote:
> > I have seen that error once before, on a box running Suse Linux. I don't
> > know what the reason is, but some searching on Deja News hinted that it
> > has something to do with threads. Except that Siag et al are not
> > multithreaded, so it shouldn't apply.
> > Can you do this:
> > ldd `which siag`
> > and send me the output. There is a possibility that one of the libraries
> > Siag links with is causing it.
> Hi again, I sent you the output of the ldd stuff, but I did some other
> You were right, I did this on Suse Linux, but on the same computer, I also
> have a copy of Red Hat Linux installed. I booted Red Hat, and built your
> office suite just fine, everything worked. Now, when I boot Suse Linux, I
> also mount the Red Hat partitions. The ldd output listed a bunch of
> libraries, and I made symlinks on the Suse side, and pointed them to the
> libraries on the Red Hat side. Then I re-made the stuff on Suse, and still
> have the problem. After I put all the symlinks back to normal, I then
> renamed the binaries in /usr/local/bin to <name>-old, and copied the
> binaries from Red Hat's /usr/local/bin to the Suse side, and everything
> works great!
> I don't know why it wouldn't work, building them with Suse, but I found a
> way to get them to work, and they look good, thanks!
Well, all the library lists include this line:
libpthread.so.0 => /lib/libpthread.so.0 (0x40188000)
So it does seem like something in Suse makes applications require threads.
I still don't understand the problem, but thanks for the solution. I'll
forward it to the list, as this is bound to bite others.