Marcus Barnes (marcus++at++multigen.com)
Thu, 20 Feb 1997 10:41:04 -0800
Two things are bad in the previous statement:
1. You do not know if the dso you've copied is binary compatible with
Performer 2.1 . Before giving a dso a version extension, you should
first verify the dso's version. The elfdump command will tell you:
% elfdump -L /usr/local/MultiGen/Performer_Loader_2.X/libpfflt_ogl.so \
| fgrep IVERSION
[4] IVERSION sgi2.0
... so this is a Performer 2.0 dso and therefore not what you need.
On our web site is the latest R15.2d loader binaries for both
2.0.2(O32) and 2.1 (O32,N32,N64). The URL is:
http://www.multigen.com/FAQ/faq.htm
2. You should never copy files into a system owned directory unless you
are _very_ sure about what you're doing (my personal opinion).
Instead, to allow pfdLoadFile() to find 3rd party loaders, set the
environment variable PFLD_LIBRARY_PATH. For example:
% setenv PFLD_LIBRARY_PATH /usr/local/MultiGen/Performer_Loader_2.X
> When we run say, perfly, the loader seems to be in an infinite loop.
> Below is part of a stack trace from dbx for perfly.
... actually it looks like its the runtime linker that's looping. The .flt
loader has not even been opened yet.
Regards.
--
+ Marcus Barnes, Technical Staff mailto:marcus++at++multigen.com +
+ Multigen Inc. http://www.multigen.com +
+ 550 S. Winchester Blvd. phoneto:1-408-556-2654 +
+ Suite 500 San Jose CA 95128 faxto:1-408-261-4102 +
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:54:41 PDT