Your message dated Mon, 01 Aug 2011 19:01:35 +0200
with message-id <4e36dbef.8000...@thykier.net>
and subject line Re: [pkg-fgfs-crew] Bug#636210: flightgear: FTBFS:
hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or
directory
has caused the Debian Bug report #636210,
regarding flightgear: FTBFS: hud_rwy.cxx:36:36: fatal error:
simgear/math/project.hxx: No such file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
636210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flightgear
Version: 2.0.0-4
Severity: serious
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
flightgear appears to be FTBFS on several architectures with the following:
"""
[...]
mv -f .deps/hud_labl.Tpo .deps/hud_labl.Po
g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I../.. -I../../src
-I/usr/local/include -MT hud_ladr.o -MD -MP -MF .deps/hud_ladr.Tpo -c -o
hud_ladr.o hud_ladr.cxx
mv -f .deps/hud_ladr.Tpo .deps/hud_ladr.Po
g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I../.. -I../../src
-I/usr/local/include -MT hud_rwy.o -MD -MP -MF .deps/hud_rwy.Tpo -c -o
hud_rwy.o hud_rwy.cxx
hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or
directory
compilation terminated.
make[4]: *** [hud_rwy.o] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
make[4]: Leaving directory
`/build/buildd-flightgear_2.0.0-4-armel-M6Aue6/flightgear-2.0.0/src/Cockpit'
make[3]: Leaving directory
`/build/buildd-flightgear_2.0.0-4-armel-M6Aue6/flightgear-2.0.0/src/Cockpit'
make[2]: Leaving directory
`/build/buildd-flightgear_2.0.0-4-armel-M6Aue6/flightgear-2.0.0/src'
"""
See https://buildd.debian.org/status/package.php?p=flightgear
~Niels
- -- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCAAGBQJONp5JAAoJEAVLu599gGRC1eAP/3/hH46eGwuNywNhbmDgLzhY
5xQqjtfJQ76gCK64HlVbRa/3Ytej57FB8MDvfedDEseLsCMHR1vjKEMxjf1ozKBv
NmTHR6aml6aRxAFK/WV3x+ZyWgUhheaXGAGOd4e9wErnFTD2FapTDwl+qzzjac1+
+cvG4HWsk2QtBXtveoY2IP0wRBtU2vG27Y2ISejyuzTbEugjm2eKbM2PEDJPfExO
tlJ5jEpT0tOglT0rrg18dmR30LffTRJ3a4GmGPNZ8cJffHVAxQPvZfhCiM0JD1YE
MU5AVTPHYzT2gprWUtSiQmbMytVJKvMiHsadqfNww+iHVbRnReUorU85E5gopdg6
hkf0DyQtT8MvNAJ1SLMTndyeOMQBZ6bb35V1pooq2mjEXNBZAm48qA51Mkakv3Ji
Ffk1wvt8U3zKdoU5piKCIfB0uYEHy3wYqctMC5povh7+sLcHXDkx2rP2Em1c3S5t
2rRl6ba29iw7VWpvjRmytESzlAnPlzNlfP6cGpZ1P9J2P5VqiQK4u6VG8K2xjTBz
386ZwTdWCPxgZnQAki3DjAsBnJjpMoMdgsGQMul0hH4nY2UUFf8dPRNAdj3oyZEU
qGGiqWuUP9HxePR6CD+1lNPpnVmupVfXbNHFr/Fykq0RpcDqJnOApY0NGJ93SvbP
Xd2ZxZSZ811XQQ2y9K3y
=7Mk0
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 2011-08-01 15:09, Ove Kåven wrote:
> On 08/01/2011 02:38 PM, Niels Thykier wrote:
>> Hi,
>>
>> flightgear appears to be FTBFS on several architectures with the
>> following:
>
> I suppose they need to be built against simgear-dev >= 2.0.0-3, not
> simgear-dev 2.0.0-2. Will it be necessary to upload new flightgear just
> to force the build-dep version, or is it enough to just wait for the
> buildds to build the newest simgear and flightgear after that?
Worked, thanks for the hint. :)
~Niels
--- End Message ---
