Re: [Flightgear-devel] Problems compiling latest CVS snapshot (2005-10-11)
Hi Andy,
thanks for the hint and "patch". I should have searched in the mail archive.
With the "patch" it compiles fine.
Thanks
Matthias
> This is a known bug when compiling on a 64 bit system. I fix it in my
> tree by double casting:
>
> --- AIBase.cxx 5 Sep 2005 13:25:09 - 1.41
> +++ AIBase.cxx 10 Oct 2005 23:39:47 -
> @@ -398,7 +398,7 @@
> }
>
> int FGAIBase::_getID() const {
> -return (int)(this);
> +return (int)(long)this;
> }
>
> This fix can't be checked in though, because it isn't correct*. The
> generated ID is not guaranteed to be unique. The right solution would
> be to either change the type of the ID to a "long long" or "uint64_t",
> or generate an identifier from something other than the pointer value.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Problems compiling latest CVS snapshot (2005-10-11)
Hi all,
I tried to compile a new CVS snapshot of FlightGear. I got following error
message:
Making all in AIModel
make[2]: Entering directory
`/home/boerner/scr/cvs/FlightGear/FlightGear-0.9/source/src/AIModel'
if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
-I/opt/FlightGear/flightgear-20051011/include -I/usr/X11R6/include
-I/usr/local//include -march=k8 -O3 -pipe -funroll-loops
-fomit-frame-pointer -D_REENTRANT -MT submodel.o -MD -MP -MF
".deps/submodel.Tpo" -c -o submodel.o submodel.cxx; \
then mv -f ".deps/submodel.Tpo" ".deps/submodel.Po"; else rm -f
".deps/submodel.Tpo"; exit 1; fi
if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
-I/opt/FlightGear/flightgear-20051011/include -I/usr/X11R6/include
-I/usr/local//include -march=k8 -O3 -pipe -funroll-loops
-fomit-frame-pointer -D_REENTRANT -MT AIManager.o -MD -MP -MF
".deps/AIManager.Tpo" -c -o AIManager.o AIManager.cxx; \
then mv -f ".deps/AIManager.Tpo" ".deps/AIManager.Po"; else rm -f
".deps/AIManager.Tpo"; exit 1; fi
if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
-I/opt/FlightGear/flightgear-20051011/include -I/usr/X11R6/include
-I/usr/local//include -march=k8 -O3 -pipe -funroll-loops
-fomit-frame-pointer -D_REENTRANT -MT AIBase.o -MD -MP -MF ".deps/AIBase.Tpo"
-c -o AIBase.o AIBase.cxx; \
then mv -f ".deps/AIBase.Tpo" ".deps/AIBase.Po"; else rm -f
".deps/AIBase.Tpo"; exit 1; fi
AIBase.cxx: In member function ‘int FGAIBase::_getID() const’:
AIBase.cxx:401: error: cast from ‘const FGAIBase*’ to ‘int’ loses precision
{standard input}: Assembler messages:
{standard input}:446: Error: Local symbol `.LTHUNK0' can't be equated to
undefined symbol `_ZN9logstreamD1Ev'
{standard input}:446: Error: Local symbol `.LTHUNK1' can't be equated to
undefined symbol `_ZN9logstreamD0Ev'
make[2]: *** [AIBase.o] Error 1
make[2]: Leaving directory
`/home/boerner/scr/cvs/FlightGear/FlightGear-0.9/source/src/AIModel'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/boerner/scr/cvs/FlightGear/FlightGear-0.9/source/src'
make: *** [all-recursive] Error 1
Does anybody has an idea what this could be?
I am working with SuSE 10.0, Kernel 2.6.13, gcc version 4.0.2 20050901.
Greetings
Matthias
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] NVIDIA 1.0-7667 breaks shadows entirely.
Oops, you are quite right. I should have thought about it before I had sent this mail. Matthias On Monday 01 August 2005 23:21, Gerard Robin wrote: > Le lundi 01 août 2005 à 23:08 +0200, Matthias Boerner a écrit : > > Hi, > > > > also NVIDIA is not working with 32bpp: You will get following error > > message if you switch to 32bpp in the section "Screen", SubSection > > "Display",...: > > > > (II) Setting vga for screen 0. > > (EE) NVIDIA(0): Given color depth (32) is not supported > > (EE) NVIDIA(0): *** Aborting *** > > (II) UnloadModule: "nvidia" > > (EE) Screen(s) found, but none have a usable configuration. > > > > > > The man pages of xorg.conf say at "DISPLAY SUBSECTION": > > > > Depth depth > > > > This entry specifies what colour depth the Display subsection is to be > > used for. This entry is usually specified, but it may be omitted to > > create a match-all Display subsection or when wishing to match only > > against the FbBpp parameter. The range of depth values that are allowed > > depends on the driver. Most driver support 8, 15, 16 and 24. Some also > > support 1 and/or 4, and some may support other values (like 30). Note: > > depth means the number of bits in a pixel that are actually used to > > determine the pixel colour. 32 is not a valid depth value. Most hardware > > that uses 32 bits per pixel only uses 24 of them to hold the colour > > information, which means that the colour depth is 24, not 32. > > > > Matthias > > Are you confusing both depth and pixel definition: > > here an extract from NVIDIA readme > > > DEPTH, BITS PER PIXEL, AND PITCH > > While not directly a concern when programming modes, the bits used per > pixel > is an issue when considering the maximum programmable resolution; for > this > reason, it is worthwhile to address the confusion surrounding the terms > "depth" and "bits per pixel". Depth is how many bits of data are stored > per > pixel. Supported depths are 8, 15, 16, and 24. Most video hardware, > however, > stores pixel data in sizes of 8, 16, or 32 bits; this is the amount of > memory > allocated per pixel. When you specify your depth, X selects the bits per > pixel > (bpp) size in which to store the data. Below is a table of what bpp is > used > for each possible depth: > > Depth BPP > ------ > 8 8 > 15 16 > 16 16 > 24 32 ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] NVIDIA 1.0-7667 breaks shadows entirely.
Hi, also NVIDIA is not working with 32bpp: You will get following error message if you switch to 32bpp in the section "Screen", SubSection "Display",...: (II) Setting vga for screen 0. (EE) NVIDIA(0): Given color depth (32) is not supported (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: "nvidia" (EE) Screen(s) found, but none have a usable configuration. The man pages of xorg.conf say at "DISPLAY SUBSECTION": Depth depth This entry specifies what colour depth the Display subsection is to be used for. This entry is usually specified, but it may be omitted to create a match-all Display subsection or when wishing to match only against the FbBpp parameter. The range of depth values that are allowed depends on the driver. Most driver support 8, 15, 16 and 24. Some also support 1 and/or 4, and some may support other values (like 30). Note: depth means the number of bits in a pixel that are actually used to determine the pixel colour. 32 is not a valid depth value. Most hardware that uses 32 bits per pixel only uses 24 of them to hold the colour information, which means that the colour depth is 24, not 32. Matthias ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] new list member and new aircraft model
Hallo, I'm pretty new to this list. I subscribed to this list several days ago after Mathias Froehlich encouraged me to do so. I'm "using and flying" with FlightGear for quite a while. So I have started to work on a new aircraft model (Eurocopter EC145). But before I will work further on I want to ask if anybody else is already working on that kind of helicopter? Best regards, Matthias ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
