info-inventor
[Top] [All Lists]

Re: Strange behavior by Inventor client programs

To: b.stolk@xxxxxxxxx (Bram Stolk)
Subject: Re: Strange behavior by Inventor client programs
From: jlim@xxxxxxxxxxxxxxxxxxxx (Jonathan Lim)
Date: Mon, 13 Nov 2000 11:12:24 -0800 (PST)
Cc: info-inventor@xxxxxxxxxxx
In-reply-to: <3A0F9834.1561DC33@chello.nl> from "Bram Stolk" at Nov 13, 2000 08:28:52 AM
Sender: owner-inventor@xxxxxxxxxxx
On Sun Nov 12 23:28:52 2000, b.stolk@xxxxxxxxx wrote:
> 
> Tom Flynn wrote:
> > 
> > I gave this a little more thought.  I'm guessing you're using NVidia's
> > drivers (given that you added to the suggestion on how to install
> > NVidia's drivers in a previous thread). I know that starting with either
> > 0.94 or 0.95 they no longer linked libGL with libpthread.  So, the pthread
> > thing is probably what you're running into.  Temporarily, that can be
> > fixed by compiling ivview on your machine.  We'll take a closer look
> > internally at the libGL we compile Inventor with on our build machine.
> 
> Err, I take it then, that on your build machine, you have linked ivview
> differently from the other iv apps, like ivinfo?

Nope.

> Is ivview the only iv app that is linked against libGL ?

They're all linked the same way: ... -lInventorXt -lInventor ...

> I wish I could examine the iv binaries better, but even 'ldd ivview'
> fails with the DYN LINK error.

I believe Tom's suggestion regarding libpthread.so is correct. I recompiled
Mesa on my build machine without -lpthread and got the same ldd error quoted
earlier on those Inventor executables and DSO's which had not been rebuilt. As
soon as I recompiled those binaries, the error went away. So it looks like it's
a libpthread.so incompatibility issue.

I have some changes to check in and will create new RPM's and tar files.


              Jonathan Lim  _  Silicon Graphics  _  Mountain View
              GPS Graphics     Computer Systems        CA, USA

<Prev in Thread] Current Thread [Next in Thread>