Frederic Bouvier wrote: > Chris Perry a écrit : > >> LeeE wrote: >> >> >>> On Thursday 08 January 2009, Jon Stockill wrote: >>> >>> >>> >>>> Chris Perry wrote: >>>> >>>> >>>> >>>>> I am using a Debian 64bit distribution Etch (AMD64). >>>>> >>>>> I have compiled the OSG, glutl, openAL, plib and simgear >>>>> ibraries under /usr/local/lib include and lib64 and find it >>>>> necessary to: export >>>>> LD_LIBRARY_PATH=/usr/local/lib:/usr/local/lib64 and then >>>>> fgfs >>>>> >>>>> Specifically the error I get is: >>>>> Warning: Could not find plugin to read objects from file >>>>> "/usr/local/share/FlightGear/data/Aircraft/c172p/splash.png". >>>>> Warning: Could not find plugin to read objects from file >>>>> "/usr/local/share/FlightGear/data/Aircraft/c172p/Models/interio >>>>> r.png". osgDB ac3d reader: could not read texture "interior.png" >>>>> ... >>>>> Segmentation fault >>>>> >>>>> The png files are on the system. The error message from osgDB >>>>> says it could not find a plugin to read the png files. >>>>> >>>>> Can you advise which software component is broken (osg?) and >>>>> how I might troble-shoot the missing plugin? >>>>> I recieved one bad message from ./configure when compiling OSG. >>>>> That was: -- ERROR: wxWidgets was not found. >>>>> configure completed ok and I went on to make without >>>>> encountering errors. >>>>> >>>>> I also failed 1 of the two test when compiling SimGear v1.9 >>>>> (make check). I gathered this was ok, or expected. Right? >>>>> >>>> The libs (or possibly just the dev package) for png support >>>> wasn't found, so OSG didn't build the png plugin. >>>> >>>> Jon >>>> >>>> >>>> >>> Yes - check that you have the libpng-dev package installed. It will >>> probably be called libpngXX-dev, where XX seems to be '12' on etch. >>> >>> LeeE >>> >>> >>> >> libpng12-dev looks like it will help. I have installed and re-run >> configure for OSG. Output for that now contains the following new line: >> Found PNG: /usr/lib64/libpng.so >> >> > > This is not enough. You should check that osgdb_png.so was correctly > compiled and installed. > I have found it at ... To check it is correctly compiled and installed I would ??? > >> I have compiled OSG and FG and still get the same errors. I would not >> have thought all the other programs would need recompiling too... Any >> thoughts? >> >> What of the >> >> -- ERROR: wxWidgets was not found. >> >> Message? >> > > Don't worry for that > Thanks. >> Another thing that look a lot of my time when building the system was >> plib. I removed the correct version for Etch (v1.8.4c2) and replaced it >> with an Etch backport for v1.8.5. To build it I had to change >> LIBS="$LIBS $X_PRE_LIBS -lXi -lXmu -lXext -lX11 $X_EXTRA_LIBS -lm" >> to >> LIBS="$LIBS $X_PRE_LIBS -lXext -lX11 $X_EXTRA_LIBS -lm" >> In the configure file. I.E. -lXi and -lXmu resulted in config errors, >> so I removed them. >> Should I attempt to track down the proper source of these errors? What >> do I need to put on the system to get plib to configure properly with >> the -lXi and -lXmu switches? >> >> All difficult questions, I know. Any help appreciated. >> > > Instead of removing vital options, I'd install libxmu-dev and libxi-dev > > -Fred > Fred, Point taken. Libraries installed (did not know what they were or that they are related to the switches.) When I reconfigured plib with the standard switches, it completed without a complaint. Thanks for that.
Should I suggest the plib Team be consulted and asked to add checks for this libs to configure? Ok, Compiling has completed. I can now start fgfs. Huray! Thanks for the help thus far. Next problem: The dashboard seems to be transparent. My start messages are: ===================== Nasal runtime error: Dialog class: XML dialog must have <name> at /usr/local/share/FlightGear/data/Nasal/gui.nas, line 246 called from: /usr/local/share/FlightGear/data/Nasal/gui.nas, line 231 called from: /usr/local/share/FlightGear/data/Nasal/globals.nas, line 96 Nasal runtime error: container index not scalar at /usr/local/share/FlightGear/data/Nasal/gui.nas, line 233 called from: /usr/local/share/FlightGear/data/Aircraft/CitationX/Nasal/flightdirector.nas, line 36 Chat [*FGMS*] Welcome to pigeond.net Chat [*FGMS*] this is version v0.9.11 (LazyRelay rev 1.14) Chat [*FGMS*] using protocol version v1.1This server is tracked. Chat [*FGMS*] chris is now online, using Chat [*FGMS*] Aircraft/CitationX/Models/Citation-X.xml Electrical System ... ok Primus 1000 systems ... check VERTEX glCompileShader "" FAILED VERTEX Shader "" infolog: (1) : error C0201: unsupported version 120 glLinkProgram "" FAILED Program "" infolog: Vertex info ----------- (1) : error C0201: unsupported version 120 ====================================== Do I need to do anything about the following messages? VERTEX glCompileShader "" FAILED glLinkProgram "" FAILED What suggestions are there to get a dashboard? I have tried the c172 and the CitationX. Same thing. The whole aircraft is invisible from all views except the Tower. Suggestions? Thanks, Chris. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Flightgear-users mailing list Flightgear-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-users
