[cl-debian] Bug#373697: clisp_1:2.38-5 (ia64/unstable): FTBFS: [interpreted.mem] Aborted
Package: clisp Version: 1:2.38-5 Severity: serious Hi Peter, The latest clisp package is failing to build on arm, ia64, and sparc, each with a different error. Of these, arm and ia64 are currently release-critical architectures, which means the failures are preventing the fix for 346164 from propagating to testing. The failure on ia64 is: [...] echo '(setq *clhs-root-default* "http://www.lisp.org/HyperSpec/")' >> config.lisp ./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -Emisc 1:1 -norc -m 1400KW -x "(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) (ext::exit t)" make[1]: *** [interpreted.mem] Aborted [...] A full build log can be found at <http://buildd.debian.org/fetch.php?pkg=clisp&arch=ia64&ver=1%3A2.38-5&stamp=1149744021&file=log>. The arm failure looks like it may have been a temporarily broken header file on arm, or it may be a bad #define in clisp. The sparc one is completely different from the other two; it's not currently a release-critical issue, but should be treated with a high priority since sparc may be re-added as a release candidate soon. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Hello Steve, Alle Thursday 15 June 2006 07:26, Steve Langasek ha scritto:
The failure on ia64 is:
[...] echo '(setq *clhs-root-default* "http://www.lisp.org/HyperSpec/")'
config.lisp ./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -Emisc 1:1 -norc -m 1400KW -x "(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) (ext::exit t)" make[1]: *** [interpreted.mem] Aborted
For this I could experiment a little and found a workaround: use -O0 to compile :-(. I opened a bug in the clisp bts: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1506857&group_id=1355
The arm failure looks like it may have been a temporarily broken header file on arm, or it may be a bad #define in clisp.
I'm trying to build clisp on leisner.debian.org at the moment, but progress seems slow.
The sparc one is completely different from the other two; it's not currently a release-critical issue, but should be treated with a high priority since sparc may be re-added as a release candidate soon.
I fear that without access to a sid chroot on sparc it will be impossible for me to go and fix this bug. A similar bug was opened for powerpc (#364688) and that I can not reproduce on any powerpc machine I have access to. My gut feeling is that with -O0 they too would disappear, so I'll wait for the results of the mips compile and then upload a package that forces -O0 on ia64, sparc and powerpc.
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|
Hi Peter, Thanks for the upload. On Fri, Jun 16, 2006 at 08:15:53AM +0200, Peter Van Eynde wrote:
[...] echo '(setq *clhs-root-default* "http://www.lisp.org/HyperSpec/")'
config.lisp ./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -Emisc 1:1 -norc -m 1400KW -x "(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) (ext::exit t)" make[1]: *** [interpreted.mem] Aborted
For this I could experiment a little and found a workaround: use -O0 to compile :-(. I opened a bug in the clisp bts: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1506857&group_id=1355
Hmm, the latest ia64 upload seems to be failing with a different error: [...] *** - UNIX error while GETWD: " [...] http://buildd.debian.org/fetch.php?pkg=clisp&arch=ia64&ver=1%3A2.38-6&stamp=1150624217&file=log I have no idea what that means, hopefully you do.
The sparc one is completely different from the other two; it's not currently a release-critical issue, but should be treated with a high priority since sparc may be re-added as a release candidate soon.
I fear that without access to a sid chroot on sparc it will be impossible for me to go and fix this bug.
You should have access to the sid chroot on vore for this, except that vore doesn't seem to be responsive right now. :/ -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Hello Steve, Alle Sunday 18 June 2006 20:46, Steve Langasek ha scritto:
Hmm, the latest ia64 upload seems to be failing with a different error:
[...] *** - UNIX error while GETWD: " [...]
http://buildd.debian.org/fetch.php?pkg=clisp&arch=ia64&ver=1%3A2.38-6&stamp=1150624217&file=log
I have no idea what that means, hopefully you do.
This is strange as the build-by-hand on merulo worked. I've asked to install the build-depends on clisp on that machine so I can a 'real' debuild.
You should have access to the sid chroot on vore for this, except that vore doesn't seem to be responsive right now. :/
This has been the case for quite some time already :-(. 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|
Your message dated Sun, 18 Jun 2006 02:32:10 -0700 with message-id <E1Frtda-0006MV-O6@spohr.debian.org> and subject line Bug#373697: fixed in clisp 1:2.38-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
participants (4)
-
owner＠bugs.debian.org -
Peter Van Eynde -
Peter Van Eynde -
Steve Langasek