[cl-debian] Accepted clisp 1:2.35-4 (source all i386)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Fri, 21 Oct 2005 23:40:24 +0200 Source: clisp Binary: clisp-dev clisp clisp-doc Architecture: source all i386 Version: 1:2.35-4 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde <pvaneynd@debian.org> Changed-By: Peter Van Eynde <pvaneynd@debian.org> Description: clisp - GNU CLISP, a Common Lisp implementation clisp-dev - GNU CLISP, a Common Lisp implementation (development files) clisp-doc - GNU CLISP, a Common Lisp implementation (documentation) Closes: 334234 Changes: clisp (1:2.35-4) unstable; urgency=low . * configure gets rerun gratuitiously (Closes: #334234) * Added build-depends on a new version of dh-lisp, to avoid FTBS. * Again use gcc 4.0 on all platforms. Hint of Thiemo Seufer Files: 31571fe54fdb0ae0972735037292fba5 721 interpreters optional clisp_2.35-4.dsc e4aff5b8ed541d9635bd5118d84df20d 194963 interpreters optional clisp_2.35-4.diff.gz 0dceb129c4628531d9cf1db42da17b2b 2836502 interpreters optional clisp_2.35-4_i386.deb 48c925f185813bcc18c0877538a0b592 1238508 devel optional clisp-dev_2.35-4_i386.deb e5a7604e15f528b888fd8e37a87faa18 970558 doc optional clisp-doc_2.35-4_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDWWfd11ldN0tyliURAkLnAKDDldv6sTUbKG42hZw0o7cYu3PvpQCgg0Eb ti5e8iBQhGr8dfBtA6Q0L+A= =O2zi -----END PGP SIGNATURE----- Accepted: clisp-dev_2.35-4_i386.deb to pool/main/c/clisp/clisp-dev_2.35-4_i386.deb clisp-doc_2.35-4_all.deb to pool/main/c/clisp/clisp-doc_2.35-4_all.deb clisp_2.35-4.diff.gz to pool/main/c/clisp/clisp_2.35-4.diff.gz clisp_2.35-4.dsc to pool/main/c/clisp/clisp_2.35-4.dsc clisp_2.35-4_i386.deb to pool/main/c/clisp/clisp_2.35-4_i386.deb

Hello people, On Saturday 22 October 2005 00:32, Peter Van Eynde wrote:
Source: clisp Architecture: source all i386
The 'all' for clisp is rather optimistic. If you see on http://people.debian.org/~igloo/status.php?packages=clisp that for alpha, hppa, ia64 and sparc the build fails. The problems visible in the build logs seem pretty severe: alpha: ./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -norc -m 1400KW -x "(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) (ext::exit t)" Cannot map memory to address 0x4000000000000 . [spvw_mmap.d:359] errno = ENOMEM: Not enough memory. ./lisp.run: Not enough memory for Lisp. hppa: ./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -norc -m 1400KW -x "(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) (ext::exit t)" make[1]: *** [interpreted.mem] Segmentation fault ia64: ./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -norc -m 1400KW -x "(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) (ext::exit t)" Cannot map memory to address 0x4000000000000 . [spvw_mmap.d:359] errno = EINVAL: Invalid argument. ./lisp.run: Not enough memory for Lisp. Does anybody have an idea what the cause could be? It does not look like a packaging problem, so I'm inclined to say that these architectures are not supported anymore by upstream and just drop them. Comments? Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson|
participants (2)
-
Peter Van Eynde
-
Peter Van Eynde