Your message dated Sat, 23 Feb 2008 05:47:03 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#461399: fixed in simgear 1.0.0-2 has caused the Debian Bug report #461399, regarding simgear_1.0.0-1 (alpha/unstable): FTBFS: Unrecognized CPU architecture 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 [EMAIL PROTECTED] immediately.) -- 461399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461399 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: simgear Version: 1.0.0-1 Severity: serious simgear is now failing to build on alpha, hppa, and s390 with the following error: if gcc -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../.. -fPIC -pipe -g -O2 -D_REENTRANT -MT bitslib.o -MD -MP -MF ".deps/bitslib.Tpo" -c -o bitslib.o bitslib.c; \ then mv -f ".deps/bitslib.Tpo" ".deps/bitslib.Po"; else rm -f ".deps/bitslib.Tpo"; exit 1; fi In file included from nasal.h:7, from data.h:4, from bitslib.c:2: naref.h:20:3: error: #error Unrecognized CPU architecture [...] A full build log can be found at <http://buildd.debian.org/fetch.cgi?pkg=simgear&arch=alpha&ver=1.0.0-1&stamp=1198415406&file=log&as=raw>. The reason for this is the following code in naref.h: /* Rather than play elaborate and complicated games with * platform-dependent endianness headers, just detect the platforms we * support. This list is simpler and smaller, yet still quite * complete. */ #if (defined(__x86_64) && defined(__linux__)) || defined(__sparcv9) || \ defined(__powerpc64__) /* Win64 and Irix should work with this too, but have not been * tested */ # define NASAL_NAN64 #elif defined(_M_IX86) || defined(i386) || defined(__x86_64) || \ defined(__ia64__) || defined(_M_IA64) || defined(__ARMEL__) # define NASAL_LE #elif defined(__sparc) || defined(__ppc__) ||defined(__PPC) || \ defined(__mips) || defined(__ARMEB__) # define NASAL_BE #else # error Unrecognized CPU architecture #endif ... which is a cop-out, and a serious regression because the old code built and ran fine on all architectures. The above code should have __alpha__ added to the NASAL_LE list, and __hppa__, __s390__, and __s390x__ added to the NASAL_BE list. BTW, according to data.h, the NASAL_NAN64 option exists to support stupid union tricks: // On 64 bit systems, Nasal non-numeric references are stored with a // bitmask that sets the top 16 bits. As a double, this is a // signalling NaN that cannot itself be produced by normal numerics // code. The pointer value can be reconstructed if (and only if) we // are guaranteed that all memory that can be pointed to by a naRef // (i.e. all memory returned by naAlloc) lives in the bottom 48 bits // of memory. Linux on x86_64, Win64, Solaris and Irix all have such // policies with address spaces: [...] Linux doesn't document this rigorously, but testing // shows that it allows 47 bits of address space (and current x86_64 // implementations are limited to 48 bits of virtual space anyway). So // we choose 48 as the conservative compromise. So this assumes the kernel will never expose more than 48bits of address space to userspace processes -- a short-sighted and groundless assumption, the reason Linux hasn't "documented this rigorously" is because there is no such guarantee. The NASAL_NAN64 option should be thrown out for all Linux variants. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED]
--- End Message ---
--- Begin Message ---Source: simgear Source-Version: 1.0.0-2 We believe that the bug you reported is fixed in the latest version of simgear, which is due to be installed in the Debian FTP archive: simgear-dev_1.0.0-2_i386.deb to pool/main/s/simgear/simgear-dev_1.0.0-2_i386.deb simgear0_1.0.0-2_i386.deb to pool/main/s/simgear/simgear0_1.0.0-2_i386.deb simgear_1.0.0-2.diff.gz to pool/main/s/simgear/simgear_1.0.0-2.diff.gz simgear_1.0.0-2.dsc to pool/main/s/simgear/simgear_1.0.0-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ove Kaaven <[EMAIL PROTECTED]> (supplier of updated simgear package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sat, 23 Feb 2008 05:33:40 +0100 Source: simgear Binary: simgear0 simgear-dev Architecture: source i386 Version: 1.0.0-2 Distribution: unstable Urgency: low Maintainer: Ove Kaaven <[EMAIL PROTECTED]> Changed-By: Ove Kaaven <[EMAIL PROTECTED]> Description: simgear-dev - Simulator Construction Gear -- development files simgear0 - Simulator Construction Gear -- shared libraries Closes: 461399 Changes: simgear (1.0.0-2) unstable; urgency=low . * Add definitions for Alpha, HPPA, and S/390 to nasal/naref.h, thanks to Steve Langasek. This should fix FTBFS on those platforms. (Unfortunately, upstream currently doesn't appear willing to fix their stuff themselves.) Closes: #461399. Files: 0f4cd749018f22bf87edb741df52a29b 885 libs extra simgear_1.0.0-2.dsc 1ae1fab6a1fb07d5a4f16e9d8d3572ac 182697 libs extra simgear_1.0.0-2.diff.gz b1207aac5871c0d329eef2da768fb493 657556 libs extra simgear0_1.0.0-2_i386.deb d984b5591b090d024ec18f605a9bc236 839636 devel extra simgear-dev_1.0.0-2_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHv6+dA+GMa4PlEQ8RAmJNAKCBWxRuh58MDaqWNeZb9W4eLJ6cxQCgj04y h15KDWBn6S3FnkmiAYtiTRA= =GpA9 -----END PGP SIGNATURE-----
--- End Message ---
