Your message dated Sun, 07 Aug 2005 01:32:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#288697: fixed in xastir 1.6.0-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 5 Jan 2005 08:21:25 +0000
>From [EMAIL PROTECTED] Wed Jan 05 00:21:25 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c196149.adsl.hansenet.de (localhost.localdomain) 
[213.39.196.149] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1Cm6Q1-0001hR-00; Wed, 05 Jan 2005 00:21:25 -0800
Received: from aj by localhost.localdomain with local (Exim 4.34)
        id 1Cm6Vb-0007Tq-KU; Wed, 05 Jan 2005 09:27:11 +0100
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
From: Andreas Jochens <[EMAIL PROTECTED]>
Subject: xastir: FTBFS (amd64/gcc-4.0): invalid storage class for function 
'landmark_hash_from_key'
Message-Id: <[EMAIL PROTECTED]>
Date: Wed, 05 Jan 2005 09:27:11 +0100
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: xastir
Severity: normal
Tags: patch

When building 'xastir' on amd64 with gcc-4.0,
I get the following error:

map_gdal.c: In function 'draw_ogr_map':
map_gdal.c:3414: error: invalid storage class for function 
'landmark_hash_from_key'
map_gdal.c:3424: error: invalid storage class for function 'landmark_keys_equal'
map_gdal.c:3439: error: invalid storage class for function 
'polyid_hash_from_key'
map_gdal.c:3449: error: invalid storage class for function 'polyid_keys_equal'
map_gdal.c:3464: error: invalid storage class for function 'tlid_hash_from_key'
map_gdal.c:3474: error: invalid storage class for function 'tlid_keys_equal'
make[4]: *** [map_gdal.o] Error 1
make[4]: Leaving directory `/xastir-1.4.1/src'

With the attached patch 'xastir' can be compiled
on amd64 using gcc-4.0.

Regards
Andreas Jochens

diff -urN ../tmp-orig/xastir-1.4.1/src/map_gdal.c ./src/map_gdal.c
--- ../tmp-orig/xastir-1.4.1/src/map_gdal.c     2004-11-04 19:53:23.000000000 
+0100
+++ ./src/map_gdal.c    2005-01-04 23:24:13.808390104 +0100
@@ -3411,7 +3411,7 @@
         // We perform the modulus function on it with the size of
         // our hash to derive the hash key.
         //
-        static unsigned int landmark_hash_from_key(void *key) {
+        unsigned int landmark_hash_from_key(void *key) {
             landmarkinfo *temp = key;
 
             return(temp->LAND % LAND_HASH_SIZE);
@@ -3421,7 +3421,7 @@
         // Test equality of hash keys.  In this case LAND is the key
         // we care about.
         //
-        static int landmark_keys_equal(void *key1, void *key2) {
+        int landmark_keys_equal(void *key1, void *key2) {
             landmarkinfo *temp1 = key1;
             landmarkinfo *temp2 = key2;
 
@@ -3436,7 +3436,7 @@
         // CENID.  We perform the modulus function on it with the
         // size of our hash to derive the hash key.
         //
-        static unsigned int polyid_hash_from_key(void *key) {
+        unsigned int polyid_hash_from_key(void *key) {
             polyinfo *temp = key;
 
             return(temp->POLYID % POLYID_HASH_SIZE);
@@ -3446,7 +3446,7 @@
         // Test equality of hash keys.  In this case POLYID (and
         // CENID?) are the keys we care about.
         //
-        static int polyid_keys_equal(void *key1, void *key2) {
+        int polyid_keys_equal(void *key1, void *key2) {
             polyinfo *temp1 = key1;
             polyinfo *temp2 = key2;
 
@@ -3461,7 +3461,7 @@
         // perform the modulus function on it with the size of our
         // hash to derive the hash key.
         //
-        static unsigned int tlid_hash_from_key(void *key) {
+        unsigned int tlid_hash_from_key(void *key) {
             tlidinfo *temp = key;
 
             return(temp->TLID % TLID_HASH_SIZE);
@@ -3471,7 +3471,7 @@
         // Test equality of hash keys.  In this case TLID is the
         // absolute key that we care about.
         //
-        static int tlid_keys_equal(void *key1, void *key2) {
+        int tlid_keys_equal(void *key1, void *key2) {
             tlidinfo *temp1 = key1;
             tlidinfo *temp2 = key2;
 

---------------------------------------
Received: (at 288697-close) by bugs.debian.org; 7 Aug 2005 08:38:40 +0000
>From [EMAIL PROTECTED] Sun Aug 07 01:38:40 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1E1gZk-0006nZ-00; Sun, 07 Aug 2005 01:32:08 -0700
From: Hamish Moffatt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#288697: fixed in xastir 1.6.0-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 07 Aug 2005 01:32:08 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2

Source: xastir
Source-Version: 1.6.0-1

We believe that the bug you reported is fixed in the latest version of
xastir, which is due to be installed in the Debian FTP archive:

xastir_1.6.0-1.diff.gz
  to pool/main/x/xastir/xastir_1.6.0-1.diff.gz
xastir_1.6.0-1.dsc
  to pool/main/x/xastir/xastir_1.6.0-1.dsc
xastir_1.6.0-1_i386.deb
  to pool/main/x/xastir/xastir_1.6.0-1_i386.deb
xastir_1.6.0.orig.tar.gz
  to pool/main/x/xastir/xastir_1.6.0.orig.tar.gz



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.
Hamish Moffatt <[EMAIL PROTECTED]> (supplier of updated xastir 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: Sun,  7 Aug 2005 18:08:09 +1000
Source: xastir
Binary: xastir
Architecture: source i386
Version: 1.6.0-1
Distribution: unstable
Urgency: low
Maintainer: Hamish Moffatt <[EMAIL PROTECTED]>
Changed-By: Hamish Moffatt <[EMAIL PROTECTED]>
Description: 
 xastir     - X Amateur Station Tracking and Information Reporting
Closes: 134452 288697 317837
Changes: 
 xastir (1.6.0-1) unstable; urgency=low
 .
   * New upstream release (closes: #317837)
   * Fix FTBFS with gcc-4.0 (closes: #288697); thanks to Andreas Jochens
     for the patch
   * Added additional README files to the binary package (closes: #134452)
   * Temporarily removed build-dep on libgdal1-dev, which is stuck waiting
     on Qt to be migrated to the new C++ ABI
Files: 
 08b79ea066dc197dc576d8f5655ba546 860 hamradio optional xastir_1.6.0-1.dsc
 d619b6b2983ffee12e19a0a5185c395f 1507098 hamradio optional 
xastir_1.6.0.orig.tar.gz
 8b1fb5d4bb11ebbc179652003c7209b7 4463 hamradio optional xastir_1.6.0-1.diff.gz
 563c84c5b2cbf409dce8259aa464a655 822542 hamradio optional 
xastir_1.6.0-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iQCVAwUBQvXDlNiYIdPvprnVAQIsWwQAkVJ9C7JVknBQeVZXU7aMeE5uzIpB4LPk
eOdQvD6D+/F2a2UchAeSM0/24acvBq6u86FaQr6R4C+JmG923pi8vapH0yE22YTx
0ds7OQY0AmGgGFihmmewOywWm+WD9mvqdzi5QgZVaAnJwRzJ1Ldb5KshE2RpgFCM
bWiCuKUTob0=
=o8ew
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to