Your message dated Tue, 12 Sep 2006 00:06:55 -0700
with message-id <[EMAIL PROTECTED]>
and subject line s390 not supported for scm
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)
--- Begin Message ---
Package: scm
Version: 5d9-5
See
http://buildd.debian.org/fetch.php?&pkg=scm&ver=5d9-5&arch=s390&stamp=1130381833&file=log&as=raw
./build -p linux --compiler-options="" -F cautious -F bignums -F arrays -F
array-for-each -F inexact -F record -F compiled-closure -F
generalized-c-arguments -F tick-interrupts -F i/o-extensions -F edit-line -F
regex -F socket -F posix -F unix -F curses -F dynamic-linking -F turtlegr -F
xlib -F dump -F macro > debian/bld
;While loading "./build.scm", line 770:
;loaded from "./build", line 11:
;ERROR: heap: rogue pointer in [EMAIL PROTECTED]
; in expression: [EMAIL PROTECTED]
; in top level environment.
FATAL ERROR DURING CRITICAL CODE SECTION: gc
75000 out of 75000 cells in use, 63685.B allocated (of 100000)
initial brk = 0x43c000, current = 0x45d000; 132.kiB
65 env stack items, 969 out of 1999 env cells in use.
;; gra: 7 (of 7) ptobs; 9 (of 9) smobs; 0 (of 1) final; 268 (of 268) subrs;
;; stack: 0x7ffff438 - 0x7fffd220; 8840 bytes
--- End Message ---
--- Begin Message ---
Package: scm
Upstream confirms that scm does not support s390. Because of Scheme's
call/cc feature, implementation requires real work and not just small
changes. s390 users who are interested in scm should contact Aubrey
Jaffer, or I can put you in touch.
Thomas
--- End Message ---
