Upgrade from 1.x to 2.0 problems

New Message Reply Date view Thread view Subject view Author view

Bill Myers (bill++at++rap.ucar.EDU)
Mon, 30 Jun 1997 15:36:40 -0600 (MDT)

Hi,
  I've just started working on Performer stuff again after developing
an application 4 or 5 years ago under Performer 1.x . I now need to
port the software to run on an Indigo2 Max Impact system. It appears
as if an upgrade to Perf 2.0 is necessary (and probably desirable).
After modifying the funcition names and parameters, I still don't get
a clean compile. Using elfdump -Dc, I get

tass:
                        ***CONFLICT SECTION***
         Name

.conflict
        [getRef__8pfMemoryFv ]
        [getUserData__8pfObjectFv ]
        [getGLHandle__8pfObjectCFv ]
        [isOfType__8pfMemoryFP6pfType]
        [getData__8pfMemoryCFv ]
        [isExactType__8pfMemoryFP6pfType]
        [__as__8pfMemoryFPC8pfMemory]
        [__readenv_sigfpe ]
        [__checktraps ]
        [ ]
        [ ]
        [ ]

My link library line looks like :
-limage -lfm -lGLU -lGL -lXext -lXmu -lX11 -lfpe -lm -lC -lpf_ogl
-lpfdu_ogl -lpfutil_ogl -lpfui

I also get :
Warning: Quickstart not set for tass since you are using different
versions of libGLU.so

I would like this to be an OGL compiled application, but realize I
don't know whether I'm mixing or matching GL and OGL libraries.
I suspect there are further problems here.. I currently have my
Multigen model loader stubbed out. If I include it, I get an error
indicating that gversion() and getgdesc() are unresolved.

Any suggestions on where to start?

Thanks,
Bill Myers
myers++at++ncar.ucar.edu
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:55:31 PDT

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