2007/8/17, Marc-Jano Knopp <[EMAIL PROTECTED]>: > Package: jedstate > Version: 0.5.4.transitional.1-5 > Severity: important > > jedstate doesn't work at all on AMD64. With the same recent_db, jedstate > on a i386 Lenny box works perfectly, while on an AMD64 Lenny box, it > does not.
GDBM files are not portable - see also http://lists.debian.org/debian-amd64/2006/05/msg00023.html If you start with a new gdbm file, do you still have problems? > Using strace, I noticed that (with the recent_db that worked flawlessly > on i386) jedstate on AMD64 at least sometimes uses absurdly high file > offsets: > > lseek(3, 70368744194048, SEEK_SET) = -1 EINVAL (Invalid argument) The jedstate package has two perl scripts. What did you strace? Does the gdbmrecent s-lang script work? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
