Re: [Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file
taking this thread from -devel to -users On 11-08-04 11:29 AM, marthter wrote: On 11-08-04 10:38 AM, TDO_Brandano - wrote: try running download_and_compile.sh (-an -pn) DATA the -an switch disables the apt-get update, and -pn disables the apt-get upgrade, you won't really need those for the data anyway. Alessandro ... Okay, spoke too soon. When I click on an aircraft like Cessna 172R my mouse pointer turns to the please wait icon and nothing else seems to happen (5+ minutes now). Is this normal? Is it building a cached copy of the aircraft geometry or something? I suppose this last question is getting into a -users list type question but I should explain that my desire to build this from source is to expand the nmea protocol output, as I asked about the other week on the -users list. -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file
On 11-08-03 08:22 PM, Csaba Halász wrote: On Thu, Aug 4, 2011 at 12:22 AM, marthtermarth...@yahoo.ca wrote: I also have separately installed FlightGear via the package manager, so I tried pointing FG_AIRCRAFT at what appears to be the Aircraft directory, Also when I guessed at what to put for the terrasync exe spot, which I found in ~/flightsim/install/fgfs/bin/terrasync, the Next button is still greyed out. No idea about fgrun, but these two settings are optional. FG knows to look for the default aircraft in FG_ROOT/Aircraft, you only need to set this if you have an additional custom location. Terrasync is not required. Okay thanks for the clarification. okay, well the pre-filled defaults in that run_fgrun Wizard, as (I assume) set up by the download_and_compile script are: 1. Executable: /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/bin/fgfs ...which exists and is executable: $ ll /home/mmuc/flight.simulator/install/fgfs/bin/fgfs -rwxr-xr-x 1 mmuc mmuc 135333892 2011-08-03 17:38 /home/mmuc/flight.simulator/install/fgfs/bin/fgfs* 2. FG_ROOT: /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/fgdata ...which exists but has not much in it: $ ll /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/fgdata total 12 drwxr-xr-x 3 mmuc mmuc 4096 2011-07-28 10:43 ./ drwxr-xr-x 5 mmuc mmuc 4096 2011-07-28 10:43 ../ drwxr-xr-x 8 mmuc mmuc 4096 2011-07-28 15:27 .git/ 3. FG_AIRCRAFT: [blank] 4. FG_SCENERY: /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/fgdata/Scenery ...which doesn't exist as shown in the FG_ROOT directory listing above 5. Terrasync exe: [blank] 6. Airports Cache: /home/mmuc/.fltk/flightgear.org/fgrun//airports.txt ...which does not exist but I'm guessing it will be created after I eventually get to run this successfully. So although I'm a newbie and not knowing what to expect in each folder, I would nonetheless assume that #2 and #4 are the problem causing run_fgrun's Next button to be greyed out. Can anyone comment/agree? I've retried sh download_and_compile.sh DATA... should this fix the above missing folder contents or is there something else I should be doing? Anyway I'm currently getting an error from gitorious.org within the sh download_and_compile.sh DATA output (although I don't think this was a problem when I ran the script yesterday and days before): $ sh download_and_compile.sh DATA ** ** * Warning, the compilation process * * is going to use 9 or more Gbytes * * of space and at least a couple of * * hours to download and build FG.* ** * Please, be patient .. * ** ** Asking your password to perform an apt-get update Ign http://extras.ubuntu.com natty InRelease ... Ign http://ca.archive.ubuntu.com natty-updates/universe Translation-en_CA Ign http://ca.archive.ubuntu.com natty-updates/universe Translation-en Reading package lists... Done Asking your password to perform an apt-get install ... Reading package lists... Done Building dependency tree Reading state information... Done automake is already the newest version. build-essential is already the newest version. ... libqt4-dev is already the newest version. subversion is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. FGFS ** gitorious.org[0: 87.238.52.168]: errno=No route to host gitorious.org[0: 2a02:c0:1014::1]: errno=Network is unreachable fatal: unable to connect a socket (Network is unreachable) $ I also tried this without using run_fgrun, but just using fgrun: $ cd ~/flightsim/install/fgrun/bin $ ./fgrun ./fgrun: error while loading shared libraries: libosgParticle.so.66: cannot open shared object file: No such file or directory $ I also tried without using $ cd ~/flightsim/install/fgfs/bin $ ./fgfs ./fgfs: error while loading shared libraries: libosgFX.so.66: cannot open shared object file: No such file or directory These are normal, the wrapper scripts contain code to set LD_LIBRARY_PATH such that the system can locate the required dependencies. You can of course do that manually too. Note that you'll have to supply fgfs with the path to the data directory using the --fg-root option. Verify that the script downloaded the data for you. Should be easy to notice, it is a3GB download :) Looks similar to what you have found in the installed package (but the two versions are not compatible). okay well the total folder structure that download_and_compile created is almost 9 GB: $ du -ms . 8906. ...but as noted above, there is next to nothing in the ~/flight.simulator/install/fgfs/fgdata directory. Thanks again and I will appreciate a little more feedback if anyone can
Re: [Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file
try running download_and_compile.sh (-an -pn) DATA the -an switch disables the apt-get update, and -pn disables the apt-get upgrade, you won't really need those for the data anyway. Alessandro Date: Thu, 4 Aug 2011 09:59:29 -0400 From: marth...@yahoo.ca To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file On 11-08-03 08:22 PM, Csaba Halász wrote: On Thu, Aug 4, 2011 at 12:22 AM, marthtermarth...@yahoo.ca wrote: I also have separately installed FlightGear via the package manager, so I tried pointing FG_AIRCRAFT at what appears to be the Aircraft directory, Also when I guessed at what to put for the terrasync exe spot, which I found in ~/flightsim/install/fgfs/bin/terrasync, the Next button is still greyed out. No idea about fgrun, but these two settings are optional. FG knows to look for the default aircraft in FG_ROOT/Aircraft, you only need to set this if you have an additional custom location. Terrasync is not required. Okay thanks for the clarification. okay, well the pre-filled defaults in that run_fgrun Wizard, as (I assume) set up by the download_and_compile script are: 1. Executable: /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/bin/fgfs ...which exists and is executable: $ ll /home/mmuc/flight.simulator/install/fgfs/bin/fgfs -rwxr-xr-x 1 mmuc mmuc 135333892 2011-08-03 17:38 /home/mmuc/flight.simulator/install/fgfs/bin/fgfs* 2. FG_ROOT: /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/fgdata ...which exists but has not much in it: $ ll /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/fgdata total 12 drwxr-xr-x 3 mmuc mmuc 4096 2011-07-28 10:43 ./ drwxr-xr-x 5 mmuc mmuc 4096 2011-07-28 10:43 ../ drwxr-xr-x 8 mmuc mmuc 4096 2011-07-28 15:27 .git/ 3. FG_AIRCRAFT: [blank] 4. FG_SCENERY: /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/fgdata/Scenery ...which doesn't exist as shown in the FG_ROOT directory listing above 5. Terrasync exe: [blank] 6. Airports Cache: /home/mmuc/.fltk/flightgear.org/fgrun//airports.txt ...which does not exist but I'm guessing it will be created after I eventually get to run this successfully. So although I'm a newbie and not knowing what to expect in each folder, I would nonetheless assume that #2 and #4 are the problem causing run_fgrun's Next button to be greyed out. Can anyone comment/agree? I've retried sh download_and_compile.sh DATA... should this fix the above missing folder contents or is there something else I should be doing? Anyway I'm currently getting an error from gitorious.org within the sh download_and_compile.sh DATA output (although I don't think this was a problem when I ran the script yesterday and days before): $ sh download_and_compile.sh DATA ** ** * Warning, the compilation process * * is going to use 9 or more Gbytes * * of space and at least a couple of * * hours to download and build FG.* ** * Please, be patient .. * ** ** Asking your password to perform an apt-get update Ign http://extras.ubuntu.com natty InRelease ... Ign http://ca.archive.ubuntu.com natty-updates/universe Translation-en_CA Ign http://ca.archive.ubuntu.com natty-updates/universe Translation-en Reading package lists... Done Asking your password to perform an apt-get install ... Reading package lists... Done Building dependency tree Reading state information... Done automake is already the newest version. build-essential is already the newest version. ... libqt4-dev is already the newest version. subversion is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. FGFS ** gitorious.org[0: 87.238.52.168]: errno=No route to host gitorious.org[0: 2a02:c0:1014::1]: errno=Network is unreachable fatal: unable to connect a socket (Network is unreachable) $ I also tried this without using run_fgrun, but just using fgrun: $ cd ~/flightsim/install/fgrun/bin $ ./fgrun ./fgrun: error while loading shared libraries: libosgParticle.so.66: cannot open shared object file: No such file or directory $ I also tried without using $ cd ~/flightsim/install/fgfs/bin $ ./fgfs ./fgfs: error while loading shared libraries: libosgFX.so.66: cannot open shared object file: No such file or directory These are normal, the wrapper scripts contain code to set LD_LIBRARY_PATH such that the system can locate the required dependencies. You can of course do that manually too. Note that you'll have
Re: [Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file
On 11-08-04 10:38 AM, TDO_Brandano - wrote: try running download_and_compile.sh (-an -pn) DATA the -an switch disables the apt-get update, and -pn disables the apt-get upgrade, you won't really need those for the data anyway. Alessandro Thanks Alessandro, I more or less tried that, at least the DATA part. I agree I don't need the apt stuff but it's not hurting me I don't think. When I do download_and_compile.sh DATA, I get the git error: You asked me to pull without telling me which branch you want to merge with, and 'branch.master.merge' in your configuration file does not tell me, either. Please specify which branch you want to use on the command line and try again (e.g. 'git pull repository refspec'). And when I do download_and_compile.sh -s DATA (for the stable version of fgdata), I get: You asked to pull from the remote 'origin', but did not specify a branch. Because this is not the default configured remote for your current branch, you must specify a branch on the command line. These two problems are around line 687 of the download_and_compile.sh script. I noticed that there were in fact 7.2 GB in the fgdata/.git folder (and no other folders present within fgdata at all), so it seemed all the downloading had been done, just none of the git magic to actually show any files. After googling the above git messages, it seems I can run git pull origin master (instead of what the script has, git pull origin), so I manually ran this and about 5 GB of Aircract, Models, and other folders are now there, so I think I am over the hurdle for now. However the script does not appear to be working as automatically as it is described so it would be nice if the script and/or the Scripted Compile wiki page would be updated by someone who knows these git details. This is my first day with git (although I've used and administered cvs and svn extensively) so I'm just grasping at straws here. Now when I run sh run_fgrun.sh it doesn't even take me to the Select Paths window with the greyed out Next button, it takes me directly to the Select an aircraft window, so I'm all good now. : - ) Okay, spoke too soon. When I click on an aircraft like Cessna 172R my mouse pointer turns to the please wait icon and nothing else seems to happen (5+ minutes now). Is this normal? Is it building a cached copy of the aircraft geometry or something? I suppose this last question is getting into a -users list type question but I should explain that my desire to build this from source is to expand the nmea protocol output, as I asked about the other week on the -users list. Cheers. Martin Date: Thu, 4 Aug 2011 09:59:29 -0400 From: marth...@yahoo.ca To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file On 11-08-03 08:22 PM, Csaba Halász wrote: On Thu, Aug 4, 2011 at 12:22 AM, marthtermarth...@yahoo.ca wrote: I also have separately installed FlightGear via the package manager, so I tried pointing FG_AIRCRAFT at what appears to be the Aircraft directory, Also when I guessed at what to put for the terrasync exe spot, which I found in ~/flightsim/install/fgfs/bin/terrasync, the Next button is still greyed out. No idea about fgrun, but these two settings are optional. FG knows to look for the default aircraft in FG_ROOT/Aircraft, you only need to set this if you have an additional custom location. Terrasync is not required. Okay thanks for the clarification. okay, well the pre-filled defaults in that run_fgrun Wizard, as (I assume) set up by the download_and_compile script are: 1. Executable: /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/bin/fgfs ...which exists and is executable: $ ll /home/mmuc/flight.simulator/install/fgfs/bin/fgfs -rwxr-xr-x 1 mmuc mmuc 135333892 2011-08-03 17:38 /home/mmuc/flight.simulator/install/fgfs/bin/fgfs* 2. FG_ROOT: /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/fgdata ...which exists but has not much in it: $ ll /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/fgdata total 12 drwxr-xr-x 3 mmuc mmuc 4096 2011-07-28 10:43 ./ drwxr-xr-x 5 mmuc mmuc 4096 2011-07-28 10:43 ../ drwxr-xr-x 8 mmuc mmuc 4096 2011-07-28 15:27 .git/ 3. FG_AIRCRAFT: [blank] 4. FG_SCENERY: /home/mmuc/flight.simulator/install/fgrun/bin/../../fgfs/fgdata/Scenery ...which doesn't exist as shown in the FG_ROOT directory listing above 5. Terrasync exe: [blank] 6. Airports Cache: /home/mmuc/.fltk/flightgear.org/fgrun//airports.txt ...which does not exist but I'm guessing it will be created after I eventually get to run this successfully. So although I'm a newbie and not knowing what to expect in each folder, I would nonetheless assume that #2 and #4 are the problem causing run_fgrun's Next button to be greyed out. Can anyone comment/agree? I've
Re: [Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file
Hi, the script is made to duild both fgrun and fgfs if you give no arguments, unfortunatelly, it is quite easy that something can go wrong (Compilation,data fetching etc...). when this happens, you can end up with an inconsistent fgdata folder that makes the git problems. Further more if data fetching stops before finishing, the script is set to stop, so you don't get fgfs nor fgrun. You have to try again, best to wipe out fgdata folder under installation/fgfs prior to relaunch the script. The problem with the blanck parameters in fgrun are due to the fist launch of it, I don't know yet how to make it work without user interaction. If you have problems with fgrun, just launch fgfs only first (sh run_fgfs.sh) and see if it works or not. Cheers Francesco -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file
On Thu, Aug 4, 2011 at 5:29 PM, marthter marth...@yahoo.ca wrote: I noticed that there were in fact 7.2 GB in the fgdata/.git folder (and no other folders present within fgdata at all), so it seemed all the downloading had been done, just none of the git magic to actually show any files. Ok, then try the git magic: git checkout master If that doesn't work, try: git branch -vr, check if that shows maybe origin/master. If so, do git checkout -b master -t origin/master. -- Csaba/Jester -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file
Hello Francesco How are you doing lately? :) Hope all are well with you... With respect to FGRUN in your script, maybe you can consider FGO in your future scripts. I find FGO to be light on system memory and easier to manage. This is just a suggestion and i hope you do not mind... Cheers! :) On Friday 05,August,2011 12:37 AM, Francesco Angelo Brisa wrote: Hi, the script is made to duild both fgrun and fgfs if you give no arguments, unfortunatelly, it is quite easy that something can go wrong (Compilation,data fetching etc...). when this happens, you can end up with an inconsistent fgdata folder that makes the git problems. Further more if data fetching stops before finishing, the script is set to stop, so you don't get fgfs nor fgrun. You have to try again, best to wipe out fgdata folder under installation/fgfs prior to relaunch the script. The problem with the blanck parameters in fgrun are due to the fist launch of it, I don't know yet how to make it work without user interaction. If you have problems with fgrun, just launch fgfs only first (sh run_fgfs.sh) and see if it works or not. Cheers Francesco -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file
I used the download_and_compile.sh script as described here: http://wiki.flightgear.org/Scripted_Compilation_on_Linux_Debian/Ubuntu. I have done this all under my home directory under a flightsim directory I made, and my system is $ cat /etc/issue Ubuntu 11.04 $ uname -a Linux software1 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux First off, those instructions seem to say to run the script with no arguments, and it will download and compile everything. Then sh run_fgfs.sh or sh run_fgrun.sh should immediately work. Those shell scripts weren't there unless I re-ran the script with added arguments. I've tried FGRUN (which seemed to help that one shell script to show up), DATA, and ALL. When I then do sh run_fgrun.sh it pops up a window titled FlightGear Wizard, and subtitled Select Paths, however, the Next button is greyed out. There are directories pre-filled in for Executable, FG_ROOT, FG_SCENERY, and (a file for) Airports Cache. There is nothing pre-filled for FG_AIRCRAFT nor Terrasync exe, and I don't know what to put there, and I don't know if it is those missing, or some other problem, that is greying out the Next button. I googled a bit and it seems one would normally point FG_AIRCRAFT to FGROOT/Aircraft but I don't know where that is supposed to be in this download_and_compile folder structure. The only Aircraft folder I have, at least within the flightsim folder heirarchy is fgfs/flightgear/src/Aircraft but it looks more like code, not data: CMakeLists.txt controls.hxx libAircraft.a Makefile.am replay.cxx replay.o controls.cxxcontrols.oMakefile Makefile.in replay.hxx I also have separately installed FlightGear via the package manager, so I tried pointing FG_AIRCRAFT at what appears to be the Aircraft directory, /usr/share/games/FlightGear/Aircraft, however this did not help in the sense that the Next button is still greyed out. Also when I guessed at what to put for the terrasync exe spot, which I found in ~/flightsim/install/fgfs/bin/terrasync, the Next button is still greyed out. I also tried this without using run_fgrun, but just using fgrun: $ cd ~/flightsim/install/fgrun/bin $ ./fgrun ./fgrun: error while loading shared libraries: libosgParticle.so.66: cannot open shared object file: No such file or directory $ I also tried without using $ cd ~/flightsim/install/fgfs/bin $ ./fgfs ./fgfs: error while loading shared libraries: libosgFX.so.66: cannot open shared object file: No such file or directory Are these problems with the download_and_compile.sh script? or with the instructions on that wiki page? or with something I'm doing? Thank you for any tips. Martin p.s. the download_and_compile seemed to finish without errors, unless the you asked me to pull without telling me which branch... message is an error that I should know how to correct. $ sh download_and_compile.sh ALL PLIB ... At revision 2166. ... OSG ... Checked out revision 12741. ... SIMGEAR ... simgear exists already. Already up-to-date. ... FGFS ... make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils/propmerge' make[2]: Leaving directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils/propmerge' Making install in fgviewer make[2]: Entering directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgviewer' make[3]: Entering directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgviewer' test -z /home/mmuc/flight.simulator/install/fgfs/bin || /bin/mkdir -p /home/mmuc/flight.simulator/install/fgfs/bin /usr/bin/install -c -p fgviewer '/home/mmuc/flight.simulator/install/fgfs/bin' make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgviewer' make[2]: Leaving directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgviewer' Making install in fgpanel make[2]: Entering directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgpanel' make[3]: Entering directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgpanel' test -z /home/mmuc/flight.simulator/install/fgfs/bin || /bin/mkdir -p /home/mmuc/flight.simulator/install/fgfs/bin make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgpanel' make[2]: Leaving directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils/fgpanel' make[2]: Entering directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils' make[3]: Entering directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/home/mmuc/flight.simulator/fgfs/flightgear/utils' make[2]: Leaving directory
Re: [Flightgear-devel] scripted compile from source... results in run_fgrun buttons greyed out, or fgfs cannot open shared object file
On Thu, Aug 4, 2011 at 12:22 AM, marthter marth...@yahoo.ca wrote: I also have separately installed FlightGear via the package manager, so I tried pointing FG_AIRCRAFT at what appears to be the Aircraft directory, Also when I guessed at what to put for the terrasync exe spot, which I found in ~/flightsim/install/fgfs/bin/terrasync, the Next button is still greyed out. No idea about fgrun, but these two settings are optional. FG knows to look for the default aircraft in FG_ROOT/Aircraft, you only need to set this if you have an additional custom location. Terrasync is not required. I also tried this without using run_fgrun, but just using fgrun: $ cd ~/flightsim/install/fgrun/bin $ ./fgrun ./fgrun: error while loading shared libraries: libosgParticle.so.66: cannot open shared object file: No such file or directory $ I also tried without using $ cd ~/flightsim/install/fgfs/bin $ ./fgfs ./fgfs: error while loading shared libraries: libosgFX.so.66: cannot open shared object file: No such file or directory These are normal, the wrapper scripts contain code to set LD_LIBRARY_PATH such that the system can locate the required dependencies. You can of course do that manually too. Note that you'll have to supply fgfs with the path to the data directory using the --fg-root option. Verify that the script downloaded the data for you. Should be easy to notice, it is a 3GB download :) Looks similar to what you have found in the installed package (but the two versions are not compatible). I suspect your GIT error message might indicate failed data download. For the already filled out paths in the fgrun page, verify that those actually exist and are readable. -- Csaba/Jester -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
