Re: [info-performer] Could not load DSO under linux

New Message Reply Date view Thread view Subject view Author view

From: Tom Flynn (flynnt++at++cthulhu.engr.sgi.com)
Date: 06/06/2000 15:05:19


On Tue, 6 Jun 2000, ross barna wrote:

>
> ok, back on this old thread, i downloaded OpenInventor2.5 from TGS (the sdk and
> static libs) installed the include and lib stuff, and tried to compile the
> libpfiv stuff... i got a ton of errors in the TGS code (undefined symbols and
> whatnot).
>
> has anyone been sucessfull compiling the Inventor Loader for pfLinux?

I've done this before. Specifically, what errors are you seeing? Is it
at compile time or runtime? It should at least compile. (and should run
as well)

> i would really appreciate step-by-step instructions... and how come you aren't
> shipping the IV loader!?!?!?

su -
cd /usr/share/Performer/src/lib/libpfdb/libpfiv
export OIVHOME=/usr # or wherever your Inventor includes and libs are
# actually the above step isn't really necessary if your includes and libs
# are installed in /usr since the compilier already looks there.
# I installed mine in /opt/oiv or something...don't remember,it was a
# while ago.
make
perfly windmill.iv

--
some obvious things:

make sure your LD_LIBRARY_PATH is set to where your Inventor libs are installed.

you can set PFLD_LIBRARY_PATH to where libpfiv.so is and set PFNFYLEVEL to 7 and run perfly to see a ton of debug that might help determine whatever problems might be occuring.

If you're still encountering problems, send us an email to mongoose-feedback++at++corp.sgi.com with the above debugging info as well as the Performer version (2.3 or 2.3.1) and we'll see if we can talk you through it and see where the problem lies.

-tom

> > -ross > > > ---------------------------------------------------------------------------- > On Wed, 12 Jan 2000, Angus Dorbie wrote: > > > The Template Graphics distribution will not help you. > > Actually, if they've updated their libraries to use a modern version of > libc yet, tnen it could... > > > the problem with the Performer Inventor loader is that it links to > > Inventor libs to load the Inventor file then converts from the in memory > > representation to the Performer scene graph. > > This is exactly what the loader does. And that's why it needs Inventor > libs. > > > From this you can conclude > > that an available Inventor library on your system would be essential to > > ultimately facilitate the Inventor loading process, however from your > > perspective this isn't currently possible since the Performer .iv loader > > hasn't been ported and doesn't ship (my assumption). > > That assumption is wrong. The source for the loader is ported and does > ship with performer_dev. A pre-compiled version of the loader does not > ship. At the time of ship-date, TGS's version of the Inventor libraries > were compiled against libc5. Performer is compiled against glibc2.1.1. > C++ programs are not binary compatable across those two libraries (or > against any major revision of C++ libraries for that matter). > The solution is to get a verion of Inventor that's compiled for glibc and > compile the loader source located in > /usr/share/Performer/src/lib/libpfdb/libpfiv yourself. Then you'll be > able to load Inventor files. In the meantime, if you have access to an > IRIX box with Performer and Inventor, you can write out .pfb files through > either pfconvert or perfly (see: man perfly) and you can read in the .pfb > files on your Linux box. > > hope that helps, > tom > > -- > "Mongooses are famous for their snake-fighting ability, and are > almost always victorious because of their speed, agility, and timing > and also because of their thick coat." > ----------------------------------------------------------------------- > List Archives, FAQ, FTP: http://www.sgi.com/software/performer/ > Submissions: info-performer++at++sgi.com > Admin. requests: info-performer-request++at++sgi.com >

-- "Mongooses are famous for their snake-fighting ability, and are almost always victorious because of their speed, agility, and timing and also because of their thick coat."


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Tue Jun 06 2000 - 15:05:24 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.