[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Tuesday 03 May 2005 03:44: I have reinstalled all the graphics related packages again. For some reasons, it worked this time. I managed to compile FlightGear without problems. But now I am having another issue: FlightGear doesn't run and gives me the following messages instead: [...] WARNING: ssgSGIHeader::: Failed to open '/usr/local/FlightGear/share/FlightGear/Textures/Sky/cl_cumulus.rgb' for reading. So? What's with theses files? Are you sure you have these, at this weird path? But anyway ... X Error of failed request: GLXUnsupportedPrivateRequest It is quite likely that the X server dynamically links against the wrong libGL, just like fgfs. So I'd stay with the easier debugging target now, and that's fgfs. Also, I don't know if the X server even needs OpenGL. I doesn't have to run in HW accelerated mode (Xrender extension) to run 3D apps with HW acceleration. (Disclaimer: I'm no X expert. :-) I suppose that there's still an old libGL around that's used instead of the new one. Try this: $ ldd `which fgfs` and check if all the relevant libraries do really use what libs you think it *should* use. I have this here: ... libglut.so.3 = /usr/X11R6/lib/libglut.so.3 (0x4005a000) libGLU.so.1 = /usr/X11R6/lib/libGLU.so.1 (0x40082000) libGL.so.1 = /usr/lib/libGL.so.1 (0x40114000) ... libGLcore.so.1 = /usr/lib/libGLcore.so.1 (0x40537000) libnvidia-tls.so.1 = /usr/lib/tls/libnvidia-tls.so.1 (0x40c28000) and I'm happy with it. Running strace again and checking the lib paths is also a good idea. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Error compiling FlightGear
On May 3, 2005 02:39 am, Melchior FRANZ wrote: WARNING: ssgSGIHeader::: Failed to open '/usr/local/FlightGear/share/FlightGear/Textures/Sky/cl_cumulus.rgb' for reading. So? What's with theses files? Are you sure you have these, at this weird path? But anyway ... Those files aren't there. As for the directory, yes, it is correct. You have no idea how much time I spent on poking around until I found out that the base-package should reside in there (as opposed to what the documentry said). =P I think it may have to do with the fact that I placed FlightGear under /usr/local/FlightGear instead of /usr/local. X Error of failed request: GLXUnsupportedPrivateRequest It is quite likely that the X server dynamically links against the wrong libGL, just like fgfs. So I'd stay with the easier debugging target now, and that's fgfs. Also, I don't know if the X server even needs OpenGL. I doesn't have to run in HW accelerated mode (Xrender extension) to run 3D apps with HW acceleration. (Disclaimer: I'm no X expert. :-) Okay. I suppose that there's still an old libGL around that's used instead of the new one. Try this: $ ldd `which fgfs` and check if all the relevant libraries do really use what libs you think it *should* use. I have this here: ... libglut.so.3 = /usr/X11R6/lib/libglut.so.3 (0x4005a000) libGLU.so.1 = /usr/X11R6/lib/libGLU.so.1 (0x40082000) libGL.so.1 = /usr/lib/libGL.so.1 (0x40114000) ... libGLcore.so.1 = /usr/lib/libGLcore.so.1 (0x40537000) libnvidia-tls.so.1 = /usr/lib/tls/libnvidia-tls.so.1 (0x40c28000) and I'm happy with it. Running strace again and checking the lib paths is also a good idea. Obviously, I don't have the libnvidia-tls.so.1 symlink. Other than that, everything else is similar to your's except libGLcore.so.1 -- it's not even listed. As for strace, FlightGear is looking at everywhere for libGL.so except in the right directory. I don't get it. =/ I am going to recompile FlightGear again tomorrow morning. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Tuesday 03 May 2005 09:39: On May 3, 2005 02:39 am, Melchior FRANZ wrote: at this weird path? But anyway ... Those files aren't there. Then you better cvs-up to the newest base package data. Not that this has anything to do with the GL problem. I think it may have to do with the fact that I placed FlightGear under /usr/local/FlightGear instead of /usr/local. Yes. /usr/local/share/ is a standard path for architecture independent data. You could use it from a Unix or Windows, from a 32 bit or 64 bit machine via network. Therefore /usr/local/share/FlightGear/ is the only reasonable place for putting fgfs (except if you are a distributor, in which case /usr/share/ would be the first choice. But that's Unix purism and has, of course, nothing to do with your case. :-) $ ldd `which fgfs` and check if all the relevant libraries do really use what libs you think it *should* use. Obviously, I don't have the libnvidia-tls.so.1 symlink. Other than that, everything else is similar to your's except libGLcore.so.1 -- it's not even listed. I don't know if libGLcore is a standard lib. The functionality could as easily be included in libGL. nvidia *does* have libGLcore, though, and if one came with your recent upgrace, then it should most likely be used. As for strace, FlightGear is looking at everywhere for libGL.so except in the right directory. I don't get it. =/ Well, it stops searching after it has found the first seemingly matching lib. So, if it really picked up the static lib (as was shown in one of your other postings), then this isn't a big surprise. Did you move the libGL.a file out of the way as I recommended? m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Saturday 30 April 2005 23:50: gcc -g -O2 -D_REENTRANT -L/usr/X11R6/lib -L/usr/local//lib -o gl-info gl-info.o -lSM -lICE -lXi -lXext -lX11 -ldl -lm gl-info.o(.text+0xd): In function `getPrints': /usr/local/src/FlightGear-0.9.8/tests/gl-info.c:28: undefined reference to `glGetString' These libs are missing from the command line: -lglut -lGLU -lGL (that is libglut, libGLU and libGL). I wonder why the configuration script didn't point this out, but it seems as if OpenGL isn't installed. Maybe only the respective *-devel packages are missing. I am seeing double slashes in the above outputs. Same here. That's ugly, but valid and certainly not the cause. I've moved to Xorg recently That explains it. Apparently you had the OpenGL libs/headers installed in the XFree86 tree, but not yet in the Xorg tree. Installing the (nvidia?) graphics drivers again (and probably glut, too -- http://freeglut.sf.net/) should fix the problem. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Monday 02 May 2005 09:17: In the attachment is a list of packaged that I have installed. Perhaps someone can point out the package that I am missing? Oh. freeglut and something that looks like opengl is already there, but the commend in brackets looks suspicious: xlibmesa-gl4.3.0.dfsg.1-1 Mesa 3D graphics library [XFree86] For XFree86? But you are running Xorg's X11R6.8.* now? Maybe you need a different [Xorg] version of these packages? m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Error compiling FlightGear
On May 2, 2005 03:39 am, Melchior FRANZ wrote: Oh. freeglut and something that looks like opengl is already there, but the commend in brackets looks suspicious: xlibmesa-gl4.3.0.dfsg.1-1 Mesa 3D graphics library [XFree86] For XFree86? But you are running Xorg's X11R6.8.* now? Maybe you need a different [Xorg] version of these packages? m. I now got the Xorg versions of mesa from ubuntu repostory. ii xlibmesa-dev 6.8.2-10 X.Org Mesa development libraries transitiona ii xlibmesa-dri 6.8.2-10 Mesa 3D graphics library modules [X.Org] ii xlibmesa-gl6.8.2-10 Mesa 3D graphics library [X.Org] ii xlibmesa-gl-de 6.8.2-10 Mesa 3D graphics library development files [ ii xlibmesa-gl1-d 2005.02.08-1 Mesa 3D graphics library [DRI trunk] ii xlibmesa-glu 6.8.2-10 Mesa OpenGL utility library [X.Org] ii xlibmesa-glu-d 6.8.2-10 Mesa OpenGL utility library development file They didn't make any different. I'm still getting the same errors when I am trying to compile FlightGear. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Monday 02 May 2005 22:35: I now got the Xorg versions of mesa from ubuntu repostory. ii xlibmesa-dri 6.8.2-10 Mesa 3D graphics library modules [X.Org] [...] They didn't make any different. I'm still getting the same errors when I am trying to compile FlightGear. Strange. Do other 3D apps work? Or is it just an fgfs compilation problem? (The worst thing that could happen, actually! ;-) My favorite strace could give you some hint in either case: A) $ strace -fF -eopen glxinfo 21|tee /tmp/strace.log B) $ strace -fF -eopen ./configure 21|tee /tmp/strace.log If you search through that log file, you'll see *where* and *what* either program searches, and why it doesn't find what it searches. Especially /libopengl would be interesting. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Monday 02 May 2005 22:16: (EE) Failed to load /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so (EE) Failed to load module GLcore (loader failed, 7) This does indeed look ugly. I assume that no 3d apps are running HW accelerated? I still wonder, though, how fgfs' configure could run through without complaint. You should also clean the source trees if you haven't already (make clean; rm -rf autom4te.cache) and configure again. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Error compiling FlightGear
On May 2, 2005 04:41 pm, Melchior FRANZ wrote: This does indeed look ugly. I assume that no 3d apps are running HW accelerated? I don't really know. glxinfo says direct rendering: yes. Xorg.0.log also reports direct rendering is enabled. Enemy Territory also runs, although it is virtually unplayable just like the days when I was using XFree. All these evidences are telling me that applications are using hardware acceleration, but I have a feeling that applications are still relying on software rendering. I still wonder, though, how fgfs' configure could run through without complaint. You should also clean the source trees if you haven't already (make clean; rm -rf autom4te.cache) and configure again. Configure returned no problem, but FlightGear still failed to compile. Same errors. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Error compiling FlightGear
On May 2, 2005 04:31 pm, Melchior FRANZ wrote: My favorite strace could give you some hint in either case: A) $ strace -fF -eopen glxinfo 21|tee /tmp/strace.log B) $ strace -fF -eopen ./configure 21|tee /tmp/strace.log If you search through that log file, you'll see *where* and *what* either program searches, and why it doesn't find what it searches. Especially /libopengl would be interesting. Interesting. It seems configure is searching for libGLcore.so and libGL.core.a in /usr/X11R6/lib and other directories, but not /usr/X11R6/lib/modules-dri-trunk where the modules are actually in. [pid 10686] open(/usr/X11R6/lib/libGL.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10686] open(/usr/X11R6/lib/libGL.a, O_RDONLY) = 13 [pid 10686] open(/usr/X11R6/lib/libGL.a, O_RDONLY) = 14 [pid 10686] open(/usr/X11R6/lib/libGL.a, O_RDONLY) = 8 [pid 10703] open(/usr/X11R6/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/X11R6/lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/local//lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/local//lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/gcc-lib/i486-linux/3.3.5/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/gcc-lib/i486-linux/3.3.5/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/gcc-lib/i486-linux/3.3.5/../../../libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/gcc-lib/i486-linux/3.3.5/../../../libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/bin/../lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/bin/../lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/i386-linux/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/i386-linux/lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/local/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/local/lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) ... ... Do you think adding /usr/X11R6/lib/modules-dri-trunk to /etc/ld.so.conf will fix the problem? Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Monday 02 May 2005 23:06: On May 2, 2005 04:41 pm, Melchior FRANZ wrote: I still wonder, though, how fgfs' configure could run through without complaint. You should also clean the source trees if you haven't already (make clean; rm -rf autom4te.cache) and configure again. Configure returned no problem, but FlightGear still failed to compile. Same errors. Sometimes configure does find some required library (because, for instance, /usr/X11R6/lib is explicitly set in configure.ac), but the compiler doesn't. Is the path where libGL resides listed in /etc/ld.so.conf? If so, did you make a ldconfig (as root) since then? And finally, did strace tell anything about libGL? :-) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Monday 02 May 2005 23:27: [pid 10686] open(/usr/X11R6/lib/libGL.so, O_RDONLY) = -1 ENOENT (No such file or directory) It doesn't find the dynamic lib ... [pid 10686] open(/usr/X11R6/lib/libGL.a, O_RDONLY) = 13 but a static one. It's an old one, right? Better remove it (or temporarily rename it). Also move other libGL.* files away (such as libGL.la). [pid 10703] open(/usr/X11R6/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [lots of ENOENT] Do you think adding /usr/X11R6/lib/modules-dri-trunk to /etc/ld.so.conf will fix the problem? Don't know if the whole tree should be searched automatically, but apparently it isn't, or there are permission problems. Yes, I'd try with this dir added to ld.so.conf. (Don't forget to run ldconfig afterwards.) But your should really first move the old cruft out of the way and make sure that only the newly donwloaded files are found. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
