Bug#373697: [cl-debian] Bug#373697: clisp_1:2.38-5 (ia64/unstable): FTBFS: [interpreted.mem] Aborted

[Peter Van Eynde]

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|