bluez-hcidump: FTBFS (amd64/gcc-4.0): static declaration of 'sdp_siz_idx_lookup_table' follows non-static declaration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Debian |
Fix Released
|
Unknown
|
|||
Ubuntu |
Fix Released
|
High
|
Matthias Klose |
Bug Description
Automatically imported from Debian bug report #285533 http://
In Debian Bug tracker #285533, Edd Dumbill (ejad) wrote : Re: Bug#285533: bluez-hcidump: FTBFS (amd64/gcc-4.0): static declaration of 'sdp_siz_idx_lookup_table' follows non-static declaration | #1 |
Debian Bug Importer (debzilla) wrote : | #2 |
Automatically imported from Debian bug report #285533 http://
Debian Bug Importer (debzilla) wrote : | #3 |
Message-Id: <email address hidden>
Date: Mon, 13 Dec 2004 22:56:16 +0100
From: Andreas Jochens <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: bluez-hcidump: FTBFS (amd64/gcc-4.0): static declaration of 'sdp_siz_
follows non-static declaration
Package: bluez-hcidump
Severity: normal
Tags: patch
When building 'bluez-hcidump' on amd64 with gcc-4.0,
I get the following error:
cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -g -Wall -O2 -c `test -f 'sdp.c' || echo './'`sdp.c
sdp.c:39: error: static declaration of 'sdp_siz_
sdp.h:160: error: previous declaration of 'sdp_siz_
sdp.c:50: error: static declaration of 'sdp_uuid_
sdp.h:167: error: previous declaration of 'sdp_uuid_
sdp.c:104: error: static declaration of 'sdp_attr_
sdp.h:176: error: previous declaration of 'sdp_attr_
sdp.c: In function 'print_int':
sdp.c:219: warning: format '%llx' expects type 'long long unsigned int', but argument 2 has type 'uint64_t'
sdp.c:222: warning: format '%llx' expects type 'long long unsigned int', but argument 2 has type 'uint64_t'
sdp.c:231: warning: format '%llx' expects type 'long long unsigned int', but argument 2 has type 'uint64_t'
make[3]: *** [sdp.o] Error 1
make[3]: Leaving directory `/bluez-
With the attached patch 'bluez-hcidump' can be compiled
on amd64 using gcc-4.0.
Regards
Andreas Jochens
diff -urN ../tmp-
--- ../tmp-
+++ ./parser/sdp.c 2004-12-13 22:51:27.150890248 +0100
@@ -36,7 +36,7 @@
#include "parser.h"
#include "sdp.h"
-static sdp_siz_
+sdp_siz_
{ 0, 1 }, /* Size index = 0 */
{ 0, 2 }, /* 1 */
{ 0, 4 }, /* 2 */
@@ -47,7 +47,7 @@
{ 1, 4 }, /* 7 */
};
-static sdp_uuid_
+sdp_uuid_
{ SDP_UUID_SDP, "SDP" },
{ SDP_UUID_UDP, "UDP" },
{ SDP_UUID_RFCOMM, "RFCOMM" },
@@ -101,7 +101,7 @@
{ SDP_UUID_
};
-static sdp_attr_
+sdp_attr_
{ SDP_ATTR_
{ SDP_ATTR_
{ SDP_ATTR_
Debian Bug Importer (debzilla) wrote : | #4 |
Message-Id: <email address hidden>
Date: Sun, 06 Feb 2005 15:00:23 +0000
From: Edd Dumbill <email address hidden>
To: Andreas Jochens <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#285533: bluez-hcidump: FTBFS (amd64/gcc-4.0): static
declaration of 'sdp_siz_
--=-+xeesR2dR7U
Content-Type: text/plain
Content-
tags 285533 fixed-upstream
thanks
This has been fixed in upstream's CVS and will be in the next release.
The upstream maintainer didn't use your patch, I'm afraid, but did other
changes.
Thanks for your contribution.
Edd.
On Mon, 2004-12-13 at 22:56 +0100, Andreas Jochens wrote:
> Package: bluez-hcidump
> Severity: normal
> Tags: patch
>=20
> When building 'bluez-hcidump' on amd64 with gcc-4.0,
> I get the following error:
--=-+xeesR2dR7U
Content-Type: application/
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQBCBjEGrxb
rxSKmjDVzgP/
=PlXA
-----END PGP SIGNATURE-----
--=-+xeesR2dR7U
Matthias Klose (doko) wrote : | #5 |
fixed in bluez-hcidump_
In Debian Bug tracker #285533, Aurelien Jarno (aurelien-aurel32) wrote : Upgrading gcc-4.0 bugs to RC | #6 |
severity 284166 serious
severity 284201 serious
severity 284741 serious
severity 284770 serious
severity 284865 serious
severity 284872 serious
severity 284885 serious
severity 285080 serious
severity 285086 serious
severity 285090 serious
severity 285095 serious
severity 285100 serious
severity 285469 serious
severity 285473 serious
severity 285475 serious
severity 285481 serious
severity 285484 serious
severity 285528 serious
severity 285533 serious
severity 285539 serious
severity 285542 serious
severity 285546 serious
severity 285577 serious
severity 285593 serious
severity 285605 serious
severity 285613 serious
severity 285624 serious
severity 285626 serious
severity 285628 serious
severity 285635 serious
severity 285646 serious
severity 285693 serious
severity 285697 serious
severity 285813 serious
severity 285918 serious
severity 285935 serious
severity 285936 serious
severity 286146 serious
severity 286428 serious
severity 286446 serious
severity 286470 serious
severity 286471 serious
severity 286474 serious
severity 286475 serious
severity 286478 serious
severity 286483 serious
severity 286487 serious
severity 286492 serious
severity 286495 serious
severity 286496 serious
severity 286503 serious
severity 286732 serious
severity 286734 serious
severity 286783 serious
severity 286784 serious
severity 286822 serious
severity 286836 serious
severity 286867 serious
severity 286872 serious
severity 286876 serious
severity 286911 serious
severity 286919 serious
severity 286925 serious
severity 286927 serious
severity 286929 serious
severity 286959 serious
severity 286964 serious
severity 287066 serious
severity 287244 serious
severity 287374 serious
severity 287376 serious
severity 287383 serious
severity 287394 serious
severity 287422 serious
severity 287449 serious
severity 287451 serious
severity 287463 serious
severity 287493 serious
severity 287494 serious
severity 287628 serious
severity 287629 serious
severity 287630 serious
severity 287633 serious
severity 287635 serious
severity 287639 serious
severity 287648 serious
severity 287660 serious
severity 287677 serious
severity 287679 serious
severity 287749 serious
severity 287843 serious
severity 287846 serious
severity 287850 serious
severity 287853 serious
severity 287854 serious
severity 287882 serious
severity 287884 serious
severity 287885 serious
severity 287886 serious
severity 287891 serious
severity 287901 serious
severity 287902 serious
severity 287907 serious
severity 287918 serious
severity 287922 serious
severity 287923 serious
severity 287924 serious
severity 287960 serious
severity 288178 serious
severity 288190 serious
severity 288305 serious
severity 288361 serious
severity 288437 serious
severity 288439 serious
severity 288441 serious
severity 288459 serious
severity 288536 serious
severity 288578 serious
severity 288586 serious
severity 288599 serious
severity 288648 serious
severity 288660 serious
severity 288697 serious
severity 288702 serious
severity 288726 serious
severity 288794 serious
severity 288832 serious
severity 288834 serious
severity 288925 serious
severity 288933 serious
severity 288966 serious
severity 288981 serious
severity 288989 serious
severity...
In Debian Bug tracker #285533, Steve Langasek (vorlon) wrote : | #7 |
Hi Edd,
> This has been fixed in upstream's CVS and will be in the next release.
That was five months ago, and gcc-4.0 is now the default compiler in etch.
When could we expect this new upstream release to be uploaded to Debian?
Thanks,
--
Steve Langasek
postmodern programmer
In Debian Bug tracker #285533, Edd Dumbill (ejad) wrote : Re: Bug#285533: bluez-hcidump: FTBFS (amd64/gcc-4.0): static declaration of 'sdp_siz_idx_lookup_table' follows non-static declaration | #8 |
On Sun, 2005-07-17 at 00:47 -0700, Steve Langasek wrote:
> Hi Edd,
>
> > This has been fixed in upstream's CVS and will be in the next release.
>
> That was five months ago, and gcc-4.0 is now the default compiler in etch.
> When could we expect this new upstream release to be uploaded to Debian?
I uploaded it yesterday. I've not tried to compile it on amd64 though
myself. There doesn't seem to be amd64 autobuilder yet.
-- Edd
In Debian Bug tracker #285533, Steve Langasek (vorlon) wrote : Re: Bug#285533: bluez-hcidump: FTBFS (amd64/gcc-4.0): static declaration of 'sdp_siz_idx_lookup_table' follows non-static declaration | #9 |
On Sun, Jul 17, 2005 at 11:02:10AM +0100, Edd Dumbill wrote:
> On Sun, 2005-07-17 at 00:47 -0700, Steve Langasek wrote:
> > > This has been fixed in upstream's CVS and will be in the next release.
> > That was five months ago, and gcc-4.0 is now the default compiler in etch.
> > When could we expect this new upstream release to be uploaded to Debian?
> I uploaded it yesterday. I've not tried to compile it on amd64 though
> myself. There doesn't seem to be amd64 autobuilder yet.
Bugs of this class are reproducible on all architectures, hence the recent
bump in severity. :)
In that case, you can probably close this bug.
Thanks,
--
Steve Langasek
postmodern programmer
Debian Bug Importer (debzilla) wrote : | #11 |
Message-ID: <email address hidden>
Date: Fri, 15 Jul 2005 11:15:32 +0200
From: Aurelien Jarno <email address hidden>
To: <email address hidden>
Subject: Upgrading gcc-4.0 bugs to RC
severity 284166 serious
severity 284201 serious
severity 284741 serious
severity 284770 serious
severity 284865 serious
severity 284872 serious
severity 284885 serious
severity 285080 serious
severity 285086 serious
severity 285090 serious
severity 285095 serious
severity 285100 serious
severity 285469 serious
severity 285473 serious
severity 285475 serious
severity 285481 serious
severity 285484 serious
severity 285528 serious
severity 285533 serious
severity 285539 serious
severity 285542 serious
severity 285546 serious
severity 285577 serious
severity 285593 serious
severity 285605 serious
severity 285613 serious
severity 285624 serious
severity 285626 serious
severity 285628 serious
severity 285635 serious
severity 285646 serious
severity 285693 serious
severity 285697 serious
severity 285813 serious
severity 285918 serious
severity 285935 serious
severity 285936 serious
severity 286146 serious
severity 286428 serious
severity 286446 serious
severity 286470 serious
severity 286471 serious
severity 286474 serious
severity 286475 serious
severity 286478 serious
severity 286483 serious
severity 286487 serious
severity 286492 serious
severity 286495 serious
severity 286496 serious
severity 286503 serious
severity 286732 serious
severity 286734 serious
severity 286783 serious
severity 286784 serious
severity 286822 serious
severity 286836 serious
severity 286867 serious
severity 286872 serious
severity 286876 serious
severity 286911 serious
severity 286919 serious
severity 286925 serious
severity 286927 serious
severity 286929 serious
severity 286959 serious
severity 286964 serious
severity 287066 serious
severity 287244 serious
severity 287374 serious
severity 287376 serious
severity 287383 serious
severity 287394 serious
severity 287422 serious
severity 287449 serious
severity 287451 serious
severity 287463 serious
severity 287493 serious
severity 287494 serious
severity 287628 serious
severity 287629 serious
severity 287630 serious
severity 287633 serious
severity 287635 serious
severity 287639 serious
severity 287648 serious
severity 287660 serious
severity 287677 serious
severity 287679 serious
severity 287749 serious
severity 287843 serious
severity 287846 serious
severity 287850 serious
severity 287853 serious
severity 287854 serious
severity 287882 serious
severity 287884 serious
severity 287885 serious
severity 287886 serious
severity 287891 serious
severity 287901 serious
severity 287902 serious
severity 287907 serious
severity 287918 serious
severity 287922 serious
severity 287923 serious
severity 287924 serious
severity 287960 serious
severity 288178 serious
severity 288190 serious
severity 288305 serious
severity 288361 serious
severity 288437 serious
severity 288439 serious
severity 288441 serious
severity 288459 serious
severity 288536 serious
severity 288578 serious
severity 288586 serious
severity 288599 serious
severity 288648 serious
severity 288660 serious
severity 288697 serious
severity 288702 serious
severity 288726 serio...
Debian Bug Importer (debzilla) wrote : | #12 |
Message-ID: <email address hidden>
Date: Sun, 17 Jul 2005 00:47:13 -0700
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: Re: bluez-hcidump: FTBFS (amd64/gcc-4.0): static declaration of 'sdp_siz_
follows non-static declaration
--EVF5PPMfhYS0aIcm
Content-Type: text/plain; charset=us-ascii
Content-
Content-
Hi Edd,
> This has been fixed in upstream's CVS and will be in the next release.
That was five months ago, and gcc-4.0 is now the default compiler in etch.
When could we expect this new upstream release to be uploaded to Debian?
Thanks,
--=20
Steve Langasek
postmodern programmer
--EVF5PPMfhYS0aIcm
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC2g0AKN6
Zkx5nqTxuDJG3It
=sD0S
-----END PGP SIGNATURE-----
--EVF5PPMfhYS0a
Debian Bug Importer (debzilla) wrote : | #13 |
Message-Id: <email address hidden>
Date: Sun, 17 Jul 2005 11:02:10 +0100
From: Edd Dumbill <email address hidden>
To: <email address hidden>, Steve Langasek <email address hidden>
Subject: Re: Bug#285533: bluez-hcidump: FTBFS (amd64/gcc-4.0): static
declaration of 'sdp_siz_
On Sun, 2005-07-17 at 00:47 -0700, Steve Langasek wrote:
> Hi Edd,
>
> > This has been fixed in upstream's CVS and will be in the next release.
>
> That was five months ago, and gcc-4.0 is now the default compiler in etch.
> When could we expect this new upstream release to be uploaded to Debian?
I uploaded it yesterday. I've not tried to compile it on amd64 though
myself. There doesn't seem to be amd64 autobuilder yet.
-- Edd
Debian Bug Importer (debzilla) wrote : | #14 |
Message-ID: <email address hidden>
Date: Sun, 17 Jul 2005 04:54:58 -0700
From: Steve Langasek <email address hidden>
To: Edd Dumbill <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#285533: bluez-hcidump: FTBFS (amd64/gcc-4.0): static declaration of
'sdp_siz_
On Sun, Jul 17, 2005 at 11:02:10AM +0100, Edd Dumbill wrote:
> On Sun, 2005-07-17 at 00:47 -0700, Steve Langasek wrote:
> > > This has been fixed in upstream's CVS and will be in the next release.
> > That was five months ago, and gcc-4.0 is now the default compiler in etch.
> > When could we expect this new upstream release to be uploaded to Debian?
> I uploaded it yesterday. I've not tried to compile it on amd64 though
> myself. There doesn't seem to be amd64 autobuilder yet.
Bugs of this class are reproducible on all architectures, hence the recent
bump in severity. :)
In that case, you can probably close this bug.
Thanks,
--
Steve Langasek
postmodern programmer
Debian Bug Importer (debzilla) wrote : | #15 |
Message-Id: <email address hidden>
Date: Sat, 23 Jul 2005 10:08:20 +0100
From: Edd Dumbill <email address hidden>
To: <email address hidden>
Subject: Closing
tags 285533 fixed-upstream
thanks
This has been fixed in upstream's CVS and will be in the next release.
The upstream maintainer didn't use your patch, I'm afraid, but did other
changes.
Thanks for your contribution.
Edd.
On Mon, 2004-12-13 at 22:56 +0100, Andreas Jochens wrote:
> Package: bluez-hcidump
> Severity: normal
> Tags: patch
>
> When building 'bluez-hcidump' on amd64 with gcc-4.0,
> I get the following error: