Thread: [Plib-users] Can't compile pui examples
Brought to you by:
sjbaker
From: Daniel T K. <dan...@dy...> - 2003-11-06 19:51:43
|
I'm trying to compile & use plib. I finally got the libraries to compile & now I want to test the libraries. I try to compile the pui examples & I get these message which I can't understand. The plibs are located in /usr/lib32 and the headers are in /usr/include/plib I have glut installed. Any help would be appreciated. Danny cc -g -o simple simple.o -lplibpu -lplibfnt -lplibsg -lplibul -lglut -lGLU -lGL -lXi -lXmu -lXext -lX11 -lm ld32: WARNING 84 : /usr/lib32/libplibfnt.a is not used for resolving any symbol. ld32: WARNING 84 : /usr/lib32/libplibsg.a is not used for resolving any symbol. ld32: WARNING 84 : /usr/lib32/libXi.so is not used for resolving any symbol. ld32: WARNING 84 : /usr/lib32/libXmu.so is not used for resolving any symbol. ld32: ERROR 33 : Unresolved text symbol "__nw__GUi" -- 1st referenced by simple.o. Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved text symbol "__dl__GPv" -- 1st referenced by simple.o. Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved text symbol "__record_needed_destruction" -- 1st referenced by /usr/lib32/libplibpu.a(puOneShot.o). Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved text symbol "__dla__GPv" -- 1st referenced by /usr/lib32/libplibpu.a(puValue.o). Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved text symbol "__nwa__GUi" -- 1st referenced by /usr/lib32/libplibpu.a(puValue.o). Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved data symbol "__vtbl__9type_info" -- 1st referenced by /usr/lib32/libplibpu.a(puOneShot.o). Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: ERROR 33 : Unresolved text symbol "__pure_virtual_called" -- 1st referenced by /usr/lib32/libplibpu.a(puObject.o). Use linker option -v to see when and which objects, archives and dsos are loaded. ld32: INFO 152: Output file removed because of error. *** Error code 2 (bu21) |
From: Daniel T K. <dan...@dy...> - 2003-11-06 19:58:34
|
I running on an SGI with IRIX 6.5.x MIPS Pro Compilers At 01:50 PM 11/6/2003, Daniel T Konkle wrote: >I'm trying to compile & use plib. >I finally got the libraries to compile & now I want to test the libraries. >I try to compile the pui examples & I get these message which I can't >understand. > >The plibs are located in /usr/lib32 and the headers are in /usr/include/plib >I have glut installed. > >Any help would be appreciated. >Danny > > > cc -g -o simple simple.o -lplibpu -lplibfnt -lplibsg -lplibul > -lglut -lGLU -lGL -lXi -lXmu -lXext -lX11 -lm >ld32: WARNING 84 : /usr/lib32/libplibfnt.a is not used for resolving any >symbol. >ld32: WARNING 84 : /usr/lib32/libplibsg.a is not used for resolving any >symbol. >ld32: WARNING 84 : /usr/lib32/libXi.so is not used for resolving any symbol. >ld32: WARNING 84 : /usr/lib32/libXmu.so is not used for resolving any symbol. >ld32: ERROR 33 : Unresolved text symbol "__nw__GUi" -- 1st referenced by >simple.o. > Use linker option -v to see when and which objects, archives and > dsos are loaded. >ld32: ERROR 33 : Unresolved text symbol "__dl__GPv" -- 1st referenced by >simple.o. > Use linker option -v to see when and which objects, archives and > dsos are loaded. >ld32: ERROR 33 : Unresolved text symbol "__record_needed_destruction" -- >1st referenced by /usr/lib32/libplibpu.a(puOneShot.o). > Use linker option -v to see when and which objects, archives and > dsos are loaded. >ld32: ERROR 33 : Unresolved text symbol "__dla__GPv" -- 1st referenced >by /usr/lib32/libplibpu.a(puValue.o). > Use linker option -v to see when and which objects, archives and > dsos are loaded. >ld32: ERROR 33 : Unresolved text symbol "__nwa__GUi" -- 1st referenced >by /usr/lib32/libplibpu.a(puValue.o). > Use linker option -v to see when and which objects, archives and > dsos are loaded. >ld32: ERROR 33 : Unresolved data symbol "__vtbl__9type_info" -- 1st >referenced by /usr/lib32/libplibpu.a(puOneShot.o). > Use linker option -v to see when and which objects, archives and > dsos are loaded. >ld32: ERROR 33 : Unresolved text symbol "__pure_virtual_called" -- 1st >referenced by /usr/lib32/libplibpu.a(puObject.o). > Use linker option -v to see when and which objects, archives and > dsos are loaded. >ld32: INFO 152: Output file removed because of error. >*** Error code 2 (bu21) > > > > > >------------------------------------------------------- >This SF.net email is sponsored by: SF.net Giveback Program. >Does SourceForge.net help you be more productive? Does it >help you create better code? SHARE THE LOVE, and help us help >YOU! Click Here: http://sourceforge.net/donate/ >_______________________________________________ >plib-users mailing list >pli...@li... >https://lists.sourceforge.net/lists/listinfo/plib-users |
From: Eero P. <epa...@ko...> - 2003-11-07 06:33:27
|
Daniel T Konkle wrote: > I'm trying to compile & use plib. > I finally got the libraries to compile & now I want to test the libraries. > I try to compile the pui examples & I get these message which I can't > understand. > > The plibs are located in /usr/lib32 and the headers are in > /usr/include/plib > I have glut installed. > > Any help would be appreciated. > Danny > > > cc -g -o simple simple.o -lplibpu -lplibfnt -lplibsg > -lplibul -lglut -lGLU -lGL -lXi -lXmu -lXext -lX11 -lm I have never compiled with a SGI, but maybe you should be using a C++ compiler here, some of the following error messages seem to be related to C++ specifics. (I am here assuming that cc is the C-compiler and you have a separate C++ compiler, which might be called CC or C++ or something) Eero |
From: Daniel T K. <dan...@dy...> - 2003-11-07 14:32:29
|
You are right. Yesterday, I went back through the mailing list archives and found what would work: env CC="cc -Xcpluscomm" CXX=CC ./configure the 'CC' is the compiler I should have been using. my brain was obvious not engaged. There are still several problems with the configure scripts on an SGI/Irix operating system. I have glut & opengl properly installed and the configure script would not find them. Danny At 12:33 AM 11/7/2003, you wrote: >Daniel T Konkle wrote: > >>I'm trying to compile & use plib. >>I finally got the libraries to compile & now I want to test the libraries. >>I try to compile the pui examples & I get these message which I can't >>understand. >>The plibs are located in /usr/lib32 and the headers are in /usr/include/plib >>I have glut installed. >>Any help would be appreciated. >>Danny >> >> cc -g -o simple simple.o -lplibpu -lplibfnt -lplibsg >> -lplibul -lglut -lGLU -lGL -lXi -lXmu -lXext -lX11 -lm > >I have never compiled with a SGI, but maybe you should be using a C++ >compiler here, some of the following error messages seem to >be related to C++ specifics. > >(I am here assuming that cc is the C-compiler and you have a separate >C++ compiler, which might be called CC or C++ or something) > > Eero > > > > > > >------------------------------------------------------- >This SF.net email is sponsored by: SF.net Giveback Program. >Does SourceForge.net help you be more productive? Does it >help you create better code? SHARE THE LOVE, and help us help >YOU! Click Here: http://sourceforge.net/donate/ >_______________________________________________ >plib-users mailing list >pli...@li... >https://lists.sourceforge.net/lists/listinfo/plib-users |