From: Tom Jolley (jolley++at++fltsim.stl.mo.boeing.com)
Date: 09/25/2002 08:34:54
Performer usually waits to open any file loader library until it is
needed. You can see this in the source code for pfdLoadFile. It
should be in /usr/share/Performer/src/lib/libpfdu. You can probably
modify pfdLoadFile to avoid the dlopen for libpfflt. A better solution
would be to specifically tell the linker to link in the flight loader
function pfdLoadFile_flt. I think the linker option is "-u symbol_name".
"Jamulla, John D. (AMHERST)" wrote:
>
> The problem I'm aving is that when we run a very specific OpenFlight
> file as input to our app, we get an error message and the app won't run.
>
>
> The app is LAZY DLOPENing the libpfflt.so (which something in performer
> is causing)
> and this is why our STATIC executable doesn't work in certain cases. I
> believe if I understand correctly, the SGI team would be the programmers
> who wrote the code to do the lazy DLOPENing. We have no control over
> this. This appears to be some sort of "bug".
>
> I was wondering if this is a known problem, maybe it's fixed if I link
> against performer 2.5 libs?
>
> Any help would be greatly appreciated.
>
> Sincerely,
> John J.
>
> ---
> John D. Jamulla - Senior Engineer
> Northrop Grumman Corporation
> Electronic Systems
> Amherst Systems
> Buffalo N.Y. 14221, (716) 631-0088
> jdj++at++amherst.com, or j.jamulla++at++ieee.org
>
> --------------------------------------------------------------------------------
> Name: John D. Jamulla.vcf
> John D. Jamulla.vcf Type: VCard (text/x-vcard)
> Encoding: 7bit
-- Tom Jolley jolley++at++fltsim.stl.mo.boeing.com
This archive was generated by hypermail 2b29 : Wed Sep 25 2002 - 08:35:24 PDT