I cannot compile it

[Anyeos]

Sorry, but I cannot configure to compile. This claim the GLU library but I already have it! Is GLU included in XOrg?? I will continue searching in google if exists some library called GLU that is not part of XOrg (I only found some about Mesa GL but it is part of XOrg).checking for a BSD-compatible install... /bin/install -cchecking whether build environment is sane... yeschecking for gawk... gawkchecking whether make sets $(MAKE)... yeschecking for style of include used by make... GNUchecking for gcc... gccchecking for C compiler default output file name... a.outchecking whether the C compiler works... yeschecking whether we are cross compiling... nochecking for suffix of executables...checking for suffix of object files... ochecking whether we are using the GNU C compiler... yeschecking whether gcc accepts -g... yeschecking for gcc option to accept ANSI C... none neededchecking dependency style of gcc... gcc3checking for library containing strerror... none requiredchecking for g++... g++checking whether we are using the GNU C++ compiler... yeschecking whether g++ accepts -g... yeschecking dependency style of g++... gcc3checking for gcc... (cached) gccchecking whether we are using the GNU C compiler... (cached) yeschecking whether gcc accepts -g... (cached) yeschecking for gcc option to accept ANSI C... (cached) none neededchecking dependency style of gcc... (cached) gcc3checking how to run the C preprocessor... gcc -Echecking for egrep... grep -Echecking for ANSI C header files... yeschecking build system type... i686-pc-linux-gnuchecking host system type... i686-pc-linux-gnuchecking target system type... i686-pc-linux-gnuchecking for sdl-config... /usr/bin/sdl-configchecking for SDL - version >= 1.2.0... yeschecking for IMG_Load in -lSDL_image... yeschecking for glBegin in -lGL... yeschecking for gluLookAt in -lGLU... noconfigure: error: *** GLU library not found!

[Anyeos]

So, the GLU library comes with recent versions of XOrg.The GLU library is part of MesaGL but MesaGL is now developed as part of XOrg.The compiler cannot found it in the standard locations (/usr/lib) and for that reason cannot send the correct information to the linker. I don't know exactly why but it appears that we need to specify the directory locations where to find it. With the -L parameter we can add library directory locations to the list, so the compiler will be search in that directories.Here the solution for VDrift:In the file "configure.in" line 33 just reeplace:LIBS="$LIBS $SDL_LIBS"with:LIBS="-L/usr/X11R6/lib $LIBS $SDL_LIBS"and do:autoreconfso the changes take effect.For the people who don't have the X11 libraries in /usr/X11R6/lib just reeplace that with the correct location.Bye.

[thelusiv]

So, where are these libraries "supposed" to go? On my system (Ubuntu) I have them in /usr/X11R6/lib but in /usr/lib there are symlinks to the files in /usr/X11R6/lib. I guess this is why I don't have problems...Anyeos, what distribution are you running?

[Anyeos]

I'm running MCLinux (created by myself). http://micro-cyber.com.arBut just with that I solved the problem.Thank you anywhere.

[fizz]

Check this thread.There's no need to edit any files. You can control everything via environment variables.

[thelusiv]

Seems that there are a few distros that this affects, maybe it's worth adding to the configure.in to catch those few instances. I don't think it will hurt anything to do so. Any thoughts, anyone?

[fizz]

Well, simply adding hard-coded paths has the disadvantage that the builder may no longer be able to properly control which libs not to link to, e.g. when you don't want to link to the libGLU in /usr/X11R6. Plus, AFAIK X.org are planning to change the file system layout anyway, so you'd have to start supporting multiple setups, too.It's possible, but it does have its drawbacks. (Then again, it might be possible to specify an optional search path that is only checked when the lib hasn't been found anywhere else, but I'd have to look that up.)

[Anyeos]

But the effective and working solution is to hardcode that for now.I insist to hardcode that, when you have a more effective and general solution just apply it. For now hardcoding it in configure.in maybe the solution.I think to do a easy thing for the people who don't know how to specify paths and don't know what is X or some other things. I don't know, if you have a more effective solution ok, do that. bye