Ubuntu

libgcrypt7: FTBFS (amd64/gcc-4.0): invalid storage class for function 'serpent_test'

Bug #15327 reported by Debian Bug Importer
4
Affects Status Importance Assigned to Milestone
Debian
Fix Released
Unknown
Ubuntu
Fix Released
High
Matthias Klose

Bug Description

Automatically imported from Debian bug report #284885 http://bugs.debian.org/284885

See original description
Revision history for this message
In , Matthias Urlichs (smurf) wrote : Re: Bug#284885: libgcrypt7: FTBFS (amd64/gcc-4.0): invalid storage class for function 'serpent_test'

Hi,

Andreas Jochens:
> When building 'libgcrypt7' on amd64 with gcc-4.0,

This may be a stupid question, but why are you building libgcrypt7 in
the first place? No package actually uses it any more, AFAIK.

--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | <email address hidden>

Revision history for this message
In , Andreas Jochens (aj-andaco) wrote :

On 04-Dec-09 12:17, Matthias Urlichs wrote:
> Hi,
>
> Andreas Jochens:
> > When building 'libgcrypt7' on amd64 with gcc-4.0,
>
> This may be a stupid question, but why are you building libgcrypt7 in
> the first place? No package actually uses it any more, AFAIK.

Thank you for your reply to my bug report.

Of course your question is not stupid at all. Unfortunately 'libgcrypt7'
is still part of the base system which is installed by the 'debootstrap'
scripts. I do not know if anything else still uses it.

Anyway, 'libgcrypt11' has the same problem with gcc-4.0 and
that is certainly more important than this one.

Regards
Andreas Jochens

Revision history for this message
In , Matthias Urlichs (smurf) wrote :

Hi,

> Of course your question is not stupid at all. Unfortunately 'libgcrypt7'
> is still part of the base system which is installed by the 'debootstrap'
> scripts. I do not know if anything else still uses it.
>
I don't think so, and I plan to verify that this weekend.

> Anyway, 'libgcrypt11' has the same problem with gcc-4.0 and
> that is certainly more important than this one.
>
Thanks; that's obviously not OK.

--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | <email address hidden>

Revision history for this message
In , Werner Koch (wk) wrote :

On Thu, 9 Dec 2004 18:45:34 +0100, Matthias Urlichs said:

>> Anyway, 'libgcrypt11' has the same problem with gcc-4.0 and
>> that is certainly more important than this one.
>>
> Thanks; that's obviously not OK.

I have fixed that in the CVS.

Thanks,

  Werner

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #284885 http://bugs.debian.org/284885

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Thu, 09 Dec 2004 11:42:15 +0100
From: Andreas Jochens <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: libgcrypt7: FTBFS (amd64/gcc-4.0): invalid storage class for function 'serpent_test'

Package: libgcrypt7
Severity: normal
Tags: patch

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

 cc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -g -Wall -O2 -Wall -MT serpent.lo -MD -MP -MF .deps/serpent.Tpo -c serpent.c -fPIC -DPIC -o .libs/serpent.o
serpent.c: In function 'serpent_setkey':
serpent.c:690: error: invalid storage class for function 'serpent_test'
make[3]: *** [serpent.lo] Error 1
make[3]: Leaving directory `/libgcrypt7-1.1.90/build-tree/libgcrypt-1.1.90/cipher'

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

Regards
Andreas Jochens

diff -urN ../tmp-orig/libgcrypt7-1.1.90/debian/patches/00list ./debian/patches/00list
--- ../tmp-orig/libgcrypt7-1.1.90/debian/patches/00list 2004-12-09 11:25:55.176527568 +0100
+++ ./debian/patches/00list 2004-12-09 11:25:31.502126624 +0100
@@ -1 +1,3 @@
 build.patch
+gcc4.patch
+
diff -urN ../tmp-orig/libgcrypt7-1.1.90/debian/patches/gcc4.patch ./debian/patches/gcc4.patch
--- ../tmp-orig/libgcrypt7-1.1.90/debian/patches/gcc4.patch 1970-01-01 01:00:00.000000000 +0100
+++ ./debian/patches/gcc4.patch 2004-12-09 11:24:53.787860064 +0100
@@ -0,0 +1,20 @@
+diff -urN tmp/cipher/serpent.c libgcrypt-1.1.90/cipher/serpent.c
+--- tmp/cipher/serpent.c 2003-10-27 14:18:32.000000000 +0100
++++ libgcrypt-1.1.90/cipher/serpent.c 2004-12-09 11:23:08.891806688 +0100
+@@ -674,6 +674,8 @@
+ _gcry_burn_stack (272 * sizeof (u32_t));
+ }
+
++static const char *serpent_test (void);
++
+ /* Initialize CTX with the key KEY of KEY_LENGTH bytes. */
+ static gcry_err_code_t
+ serpent_setkey (void *ctx,
+@@ -687,7 +689,6 @@
+ if (! serpent_init_done)
+ {
+ /* Execute a self-test the first time, Serpent is used. */
+- static const char *serpent_test (void);
+
+ serpent_test_ret = serpent_test ();
+ if (serpent_test_ret)

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20041209111758.GA7940@kiste>
Date: Thu, 9 Dec 2004 12:17:59 +0100
From: "Matthias Urlichs" <email address hidden>
To: Andreas Jochens <email address hidden>, <email address hidden>
Cc: Debian Bug Tracking System <email address hidden>
Subject: Re: Bug#284885: libgcrypt7: FTBFS (amd64/gcc-4.0): invalid storage class for function
 'serpent_test'

Hi,

Andreas Jochens:
> When building 'libgcrypt7' on amd64 with gcc-4.0,

This may be a stupid question, but why are you building libgcrypt7 in
the first place? No package actually uses it any more, AFAIK.

--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 9 Dec 2004 12:43:36 +0100
From: Andreas Jochens <email address hidden>
To: Matthias Urlichs <email address hidden>
Cc: <email address hidden>,
 Debian Bug Tracking System <email address hidden>
Subject: Re: Bug#284885: libgcrypt7: FTBFS (amd64/gcc-4.0): invalid storage class for function
 'serpent_test'

On 04-Dec-09 12:17, Matthias Urlichs wrote:
> Hi,
>
> Andreas Jochens:
> > When building 'libgcrypt7' on amd64 with gcc-4.0,
>
> This may be a stupid question, but why are you building libgcrypt7 in
> the first place? No package actually uses it any more, AFAIK.

Thank you for your reply to my bug report.

Of course your question is not stupid at all. Unfortunately 'libgcrypt7'
is still part of the base system which is installed by the 'debootstrap'
scripts. I do not know if anything else still uses it.

Anyway, 'libgcrypt11' has the same problem with gcc-4.0 and
that is certainly more important than this one.

Regards
Andreas Jochens

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20041209174533.GB18775@kiste>
Date: Thu, 9 Dec 2004 18:45:34 +0100
From: "Matthias Urlichs" <email address hidden>
To: Andreas Jochens <email address hidden>, <email address hidden>
Cc: Debian Bug Tracking System <email address hidden>
Subject: Re: Bug#284885: libgcrypt7: FTBFS (amd64/gcc-4.0): invalid storage class for function
 'serpent_test'

Hi,

> Of course your question is not stupid at all. Unfortunately 'libgcrypt7'
> is still part of the base system which is installed by the 'debootstrap'
> scripts. I do not know if anything else still uses it.
>
I don't think so, and I plan to verify that this weekend.

> Anyway, 'libgcrypt11' has the same problem with gcc-4.0 and
> that is certainly more important than this one.
>
Thanks; that's obviously not OK.

--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Fri, 10 Dec 2004 10:39:42 +0100
From: Werner Koch <email address hidden>
To: "Matthias Urlichs" <email address hidden>
Cc: <email address hidden>, Andreas Jochens <email address hidden>,
 Debian Bug Tracking System <email address hidden>
Subject: Re: Bug#284885: libgcrypt7: FTBFS (amd64/gcc-4.0): invalid storage
 class for function 'serpent_test'

On Thu, 9 Dec 2004 18:45:34 +0100, Matthias Urlichs said:

>> Anyway, 'libgcrypt11' has the same problem with gcc-4.0 and
>> that is certainly more important than this one.
>>
> Thanks; that's obviously not OK.

I have fixed that in the CVS.

Thanks,

  Werner

Revision history for this message
Matthias Urlichs (smurf) wrote :

to be deleted from breezy

Revision history for this message
Matthias Klose (doko) wrote :

fixed in ubuntu uploads

Revision history for this message
In , Aurelien Jarno (aurelien-aurel32) wrote : Upgrading gcc-4.0 bugs to RC
Download full text (8.3 KiB)

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...

Read more...

Revision history for this message
In , Martin Michlmayr (tbm) wrote : Removed

These packages have been removed since they are obsoleted by newer
versions.
--
Martin Michlmayr
http://www.cyrius.com/

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (8.5 KiB)

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...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 7 Aug 2005 14:50:00 +0100
From: Martin Michlmayr <email address hidden>
To: <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Subject: Removed

These packages have been removed since they are obsoleted by newer
versions.
--
Martin Michlmayr
http://www.cyrius.com/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.