[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#478000: clisp: FTBFS on sparc: ALLOCATE-METAOBJECT-INSTANCE: length 0 should be of type (INTEGER (0) (0000))



Hi Bernd!

On Sat, 26 Apr 2008 10:58:07 +0200, Bernd Zeimetz wrote:
> after lebrun.d.o timed out while building clisp I gave it a try in the
> sid chroot of sperger, this time it failed to build, too.

I don't really understand why lebrun started to build clisp: while the
debian/rules file contains some checks for sparc, debian/control
explicitly avoid sparc [1]:

  Package: clisp
  Architecture: alpha amd64 arm hppa i386 ia64 mips mipsel powerpc
                s390 kfreebsd-i386 m68k hurd-i386

FWIW, sparc support was present in sarge, but not in etch.

> ;; Loading file /home/bzed/clisp-2.44/src/clos-class2.lisp ...
> ;; Loaded file /home/bzed/clisp-2.44/src/clos-class2.lisp
> ;; Loading file /home/bzed/clisp-2.44/src/clos-class3.lisp ...
> *** - ALLOCATE-METAOBJECT-INSTANCE: length 0 should be of type (INTEGER
> (0) (0000))
> Bye.

This is exactly the same error that cause sparc removal from the
supported architecture, see bug #386075 [2].

Bernd, I'd downgrade the severity at least to normal or wishlist (sparc
is not supported).  I planned to upload version 2.44.1 this evening or
tomorrow: since this is a bugfix upstream version for gcc-4.2/-4.3 [3],
we can give it a try on sparc again.  What do you think?

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://git.debian.org/?p=pkg-common-lisp/clisp.git;a=blob;f=debian/control;h=1163e658a01d4307ce6945c2536c8d7e1b839f16;hb=HEAD
[2] http://bugs.debian.org/386075
[3] http://git.debian.org/?p=pkg-common-lisp/clisp.git;a=commitdiff;h=309d00d9cb2c4f17a6e9151e3863638e1c06a082
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 314 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-common-lisp-devel/attachments/20080618/e41703ba/attachment.pgp 


Reply to: