Package: ccrypt
Version: 1.7-8
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of ccrypt_1.7-8 on caballero by sbuild/ia64 85
> Build started at 20060110-2207

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 4.0.0)

[...]

> make[2]: Entering directory `/build/buildd/ccrypt-1.7'
> Making all in src
> make[3]: Entering directory `/build/buildd/ccrypt-1.7/src'
> if ia64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I..     -Wall -g -O3 -MT 
> maketables.o -MD -MP -MF ".deps/maketables.Tpo" -c -o maketables.o 
> maketables.c; \
>       then mv -f ".deps/maketables.Tpo" ".deps/maketables.Po"; else rm -f 
> ".deps/maketables.Tpo"; exit 1; fi
> ia64-linux-gnu-gcc  -Wall -g -O3   -o maketables  maketables.o  -lcrypt 
> ./maketables > tables.c
> /bin/sh: line 1:  2611 Bus error               ./maketables >tables.c
> make[3]: *** [tables.c] Error 135
> make[3]: Leaving directory `/build/buildd/ccrypt-1.7/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/ccrypt-1.7'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/ccrypt-1.7'
> make: *** [build-stamp] Error 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=ia64&pkg=ccrypt&ver=1.7-8

The following patch fixes this bug:

diff -ur t/ccrypt-1.7/src/maketables.c ccrypt-1.7/src/maketables.c
--- t/ccrypt-1.7/src/maketables.c       2004-03-29 04:53:40.000000000 +0000
+++ ccrypt-1.7/src/maketables.c 2006-01-11 02:43:54.000000000 +0000
@@ -84,7 +84,8 @@
 /* ---------------------------------------------------------------------- */
 
 static word32 multrot2113(int rot, word8 m) {
-  word8 r[4];
+  word32 rw[1];
+  word8 *r=(word8*)rw;
 
   r[rot]         = multiply(2,m);
   r[(rot+1) % 4] = m;
@@ -130,7 +131,8 @@
 
 int main() {
   int rot, m, i, rcon;
-  word8 r[4];
+  word32 rw[1];
+  word8 *r=(word8*)rw;
 
   printf("#include \"rijndael.h\"\n\n");
 


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

Reply via email to