Re: [Flightgear-devel] Startup problem

2010-07-26 Thread Hal V. Engel
On Sunday 25 July 2010 10:29:02 pm fiers...@zonnet.nl wrote: > Op 26-07-10 07:14, fiers...@zonnet.nl schreef: > > Op 25-07-10 19:19, Stefan Seifert schreef: > >> On the other hand, I'm running a system with 100% free software thanks > >> to AMD's releasing of documentation for driver writers for AT

Re: [Flightgear-devel] Startup problem

2010-07-25 Thread fierst42
Op 26-07-10 07:14, fiers...@zonnet.nl schreef: > Op 25-07-10 19:19, Stefan Seifert schreef: > >> On the other hand, I'm running a system with 100% free software thanks to >> AMD's releasing of documentation for driver writers for ATI cards. And my ATI >> card with its free drivers allowed me fo

Re: [Flightgear-devel] Startup problem

2010-07-25 Thread fierst42
Op 25-07-10 19:19, Stefan Seifert schreef: > On the other hand, I'm running a system with 100% free software thanks to > AMD's releasing of documentation for driver writers for ATI cards. And my ATI > card with its free drivers allowed me for the first time in many years not > only > to run Flight

Re: [Flightgear-devel] Startup problem

2010-07-25 Thread Hal V. Engel
On Sunday 25 July 2010 10:19:46 am Stefan Seifert wrote: > On Sunday 25 July 2010 18:38:45 fiers...@zonnet.nl wrote: > > I second that. As the matter of fact I stick to nVidea for all machines > > over the years, because I feel that nVidea should be rewarded for their > > support of Linux and ATI s

Re: [Flightgear-devel] Startup problem

2010-07-25 Thread castle
Yea, that turned out to be the problem. Not sure why, but as a last resort and late at night I reinstalled the Nvidia driver and that cleared the problem. Now I'm looking for a good doc or tutorial on creating AI traffic and "lots of activity" at an airport. Have a couple of talks coming up to li

Re: [Flightgear-devel] Startup problem

2010-07-25 Thread Stefan Seifert
On Sunday 25 July 2010 18:38:45 fiers...@zonnet.nl wrote: > I second that. As the matter of fact I stick to nVidea for all machines > over the years, because I feel that nVidea should be rewarded for their > support of Linux and ATI should be punished for not taking Linux seriously. On the other h

Re: [Flightgear-devel] Startup problem

2010-07-25 Thread fierst42
I second that. As the matter of fact I stick to nVidea for all machines over the years, because I feel that nVidea should be rewarded for their support of Linux and ATI should be punished for not taking Linux seriously. m Op 25-07-10 15:39, Curtis Olson schreef: This definitely looks like a go

Re: [Flightgear-devel] Startup problem

2010-07-25 Thread Curtis Olson
This definitely looks like a good time to check your cows. My first knee jerk reaction if I see this would be to reinstall the nvidia drivers from nvidia.com, and if you don't have nvidia video hardware and you are running linux, then hopefully someone else can lend a hand since I stick to nvidia

Re: [Flightgear-devel] Startup Problem

2009-04-26 Thread Martin Spott
Curtis Olson wrote: > Yes, there was some discussion a while back about adding the boost > dependency. There should be prebuilt boost packages for most linux > distributions. Note that just the Boost header files are required - which makes adding Boost to the setup quite easy, Martin -

Re: [Flightgear-devel] Startup Problem

2009-04-26 Thread John Wojnaroski
[r...@moat FlightGear-1.9.1]# ./configure --help `configure' configures this package to adapt to many kinds of systems. : : Optional Packages: --with-PACKAGE[=ARG]use PACKAGE [ARG=yes] --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) --with-boost[=DIR] : : : Odd, wh

Re: [Flightgear-devel] Startup Problem

2009-04-26 Thread John Wojnaroski
Hmm, running Centos-5.3 and the latest boost version in that distro is 1.33. Do you happen to know the latest version on RH? Debian is 1.35 based on the packages in the stable release. I'm not all that conversant on the benefits of boost. what is gained? Tried compiling a boost library fo

Re: [Flightgear-devel] Startup Problem

2009-04-26 Thread Ron Jensen
> >Curtis Olson wrote: > > > >Yes, there was some discussion a while back about adding the boost > >dependency. There should be prebuilt boost packages for most linux > >distributions. > > > >Regards, > > > >Curt. > > > On Sun, 2009-04-26 at 14:39 -0700, John Wojnaroski wrote: > Hmm, running Ce

Re: [Flightgear-devel] Startup Problem

2009-04-26 Thread Frederic Bouvier
Hi John, I can't find a --without-boost option in configure.ac, either for SimGear or FlightGear. Simgear configure abort when a suitable boost version is not found. Required minimum version of boost is 1.34 -Fred - "John Wojnaroski" a écrit : > I'm asking the same question again. :-( >

Re: [Flightgear-devel] Startup Problem

2009-04-26 Thread Curtis Olson
Yes, there was some discussion a while back about adding the boost dependency. There should be prebuilt boost packages for most linux distributions. Regards, Curt. On Sun, Apr 26, 2009 at 3:51 PM, John Wojnaroski wrote: > I'm asking the same question again. :-( > > Started a build of the CVS

Re: [Flightgear-devel] Startup Problem

2009-04-26 Thread John Wojnaroski
I'm asking the same question again. :-( Started a build of the CVS on an older 32-bit machine and wound up in the same place <<< clude -DPKGLIBDIR=\"/usr/local/share/FlightGear\" -g -O2 -D_REENTRANT -MT fg_os_osgviewer.o -MD -MP -MF ".deps/fg_os_osgviewer.Tpo" -c -o fg_

Re: [Flightgear-devel] Startup Problem

2009-04-18 Thread Ron Jensen
On Sat, 2009-04-18 at 19:16 -0600, Ron Jensen wrote: > The warning message is new. The fgfs binary automatically changes > FGROOT to $FGROOT/data if it doesn't find the data folder in $FGROOT > where it belongs. However many tools break on $FGROOT/data so now the > fgfs binary issues a warning a

Re: [Flightgear-devel] Startup Problem

2009-04-18 Thread Ron Jensen
On Fri, 2009-04-17 at 23:22 -0700, cas...@mminternet.com wrote: > Hi, > > Did an upload of the the latest CVS 1.9.1, build went just fine but when > starting the following happens... > > <<< > [cas...@rampart FlightGear]$ ./run > *** > *** > *** Warning: c