check your config.log
and paste the parts that failed (with respect to GLU)
maybe your GLU has some strange library xtra requirements that need to be added
then you can hack configure.in to add those lib requirements
ugh either way it's your distro's/Mesa's fault
cus GLU shouldn't need anything else to be compiled other than GL
anyhow paste the config.log that has something like
gcc test.cpp -lGL -lGLU ...
... unresolved external...
... libGLU unavailable
donate money for RPMs?
-
- Developer
- Posts: 3980
- Joined: Fri Jan 03, 2003 4:53 am
- Location: Stanford, CA
- Contact:
Vega Strike Lead Developer
http://vegastrike.sourceforge.net/
http://vegastrike.sourceforge.net/
-
- Artisan
- Posts: 1270
- Joined: Fri Jan 03, 2003 3:27 am
- Location: Perth, Western Australia
- Contact:
config.log
I did, what Dan told me. It didn't help.
May I really post my whole config.log here? It's 78 kByte big, which is no problem for me but perhaps for the forum?
spunti
May I really post my whole config.log here? It's 78 kByte big, which is no problem for me but perhaps for the forum?
spunti
-
- Artisan
- Posts: 1270
- Joined: Fri Jan 03, 2003 3:27 am
- Location: Perth, Western Australia
- Contact:
config.log
Hm, the whole file seems to handle of Glu and MesaGlu, so I put the file there:
http://mitglied.lycos.de/ronnypriv/config.log
spunti
http://mitglied.lycos.de/ronnypriv/config.log
spunti