Re: [Plib-users] Fedora Core 6 Compilation errors

[Stuart M. <stu...@bl...>]

I no nothing about Fedora and very little about autoconf, but here are
my thoughts....

> -----Original Message-----
> And also have the simbolic links, as requested on Plib installation 
> instructions:
> # ls -l libGL.so
> lrwxrwxrwx 1 root root 23 Apr 27 12:12 libGL.so ->
/usr/local/lib/libGL.so
>
> # ls -l libGLU.so
> lrwxrwxrwx 1 root root 24 Apr 27 12:12 libGLU.so ->
/usr/local/lib/libGLU.so
>
>
> Can anybody help me?? There no way I can solve this issue.... :-(

If the libraries aren't being found then it means the compiler search
path isn't looking in the directories. Or that the symbol isn't present
in the library.

The configure script is generating a small C program (you should have a
log somewhere showing what it couldn't compile) something like

extern void glNewList();

int main()
{
   glNewList();
   return 0;
}

Which it is compiling with something like

   gcc <options> test.c -lGL

(again the log should show what it's doing)

The glNewList is a function that should be present in the GL library.
The -L option can be used to add to the search path. So you could try

  gcc -L/usr/local/lib test.c -lGL

If that says the symbol isn't found then it means it found the library
(you can double check by putting -lBLAH and it should say it can't find
BLAH).

You can also see if the symbol is present using nm

  nm /usr/local/lib | grep glNewList

And you should get a line something like

  00000000 T _glNewList

the "T" is the "text" symbol. i.e. the code.

The symbol will definitely be there, but some things I can think of are

1) If C++ is involved anywhere in the above then it "name-mangles"
symbols (to handle class methods with the same name). e.g. if you use
g++ on the test.c program it won't find the glNewList because it looks
for the mangled name in the library.
2) I use cygwin and there is some strange windows things that I don't
understand, but the symbols I have in my GL libraries have '@' at the
end. To use the other libraries I would have to compile with
-Dno-cygwin. I doubt anything like that is happening, here.

So if you can that test.c program to compile and link then you should be
able to see why the configure script's version doesn't and fix it e.g.
by telling it the -L <library path> to use, or whatever the problem is.

Anyway, hopefully this is a starting point to understanding what's going
on..

--Stuart.