Package: as31
Version: 2.3.1-4
Severity: important
Hi,
as31 2.3.1-4 fails to work on 64-bit systems:
$ as31 paulmon1.asm
Begin Pass #1
Begin Pass #2
Error, line 22, Location counter overlaps.
Error, line 22, Location counter overlaps.
Error, line 22, Location counter overlaps.
...
The sole difference between upstream version 2.3.0 and 2.3.1 was to
fix this bug:
$ tail -3 as31-2.3.1/ChangeLog
Sep 05, 2005 Alexander 'E-Razor' Krause
<[email protected]>:
(Version 2.3.1) - 'Location counter overlaps' on 64bit systems solved
$ diff -urN as31-2.3.0/as31 as31-2.3.1/as31
diff -urN as31-2.3.0/as31/parser.y as31-2.3.1/as31/parser.y
--- as31-2.3.0/as31/parser.y 2005-03-08 13:33:39.000000000 -0500
+++ as31-2.3.1/as31/parser.y 2005-09-05 12:32:47.000000000 -0400
@@ -1016,13 +1016,13 @@
*
*/
-#define indx(a) ( (a)/(sizeof(long)*8) )
-#define bit(a) ( 1 << ((a)%(sizeof(long)*8)) )
+#define indx(a) ( (a)/(32) )
+#define bit(a) ( 1 << ((a)%(32)) )
#define getloc(a) (regions[indx(a)] & bit(a))
#define setloc(a) (regions[indx(a)] |= bit(a))
-static unsigned long regions[ 0x10000/(sizeof(long)*8) ];
+static unsigned long regions[ 0x10000/(32) ];
void inclc(int i)
{
However, the Debian package doesn't regenerate parser.c from parser.y
and so these changes are not being incorporated. The Debian package
ships a bad parser.c corresponding to upstream 2.3.0. I was able to
build a working version of as31 with:
$ apt-get source as31
$ cd as31-2.3.1
$ make -f debian/rules configure
$ rm as31/parser.c
$ make -f debian/rules build
-jim
-- System Information:
Debian Release: 6.0.3
APT prefers stable
APT policy: (200, 'stable'), (150, 'oldstable'), (80, 'testing'), (50,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.37-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages as31 depends on:
ii libc6 2.11.2-10
as31 recommends no packages.
as31 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
