unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Cc: rlb@defaultvalue.org
Subject: Re: guile 1.8.3 fails to build on sparc
Date: Thu, 07 Feb 2008 22:53:13 +0100	[thread overview]
Message-ID: <87lk5wa0xi.fsf@dellish.bordeaux.inria.fr> (raw)
In-Reply-To: 874pcwqmct.fsf@ossau.uklinux.net

Hi,

Neil Jerram <neil@ossau.uklinux.net> writes:

> Kamaraju S Kusumanchi <kamaraju@bluebottle.com> writes:
>
>> I don't have access to sparc machine to probe into this problem. Can someone
>> look at
>> http://buildd.debian.org/fetch.cgi?pkg=guile-1.8;ver=1.8.3%2B1-1;arch=sparc;stamp=1195798674
>> and see why guile-1.8-libs fails to build on a sparc machine?
>
> Sorry this response is so delayed.  Seems to be a GC issue:
>
> FAIL: gc.test: gc: Unused modules are removed

This indeed looks like a reference to a single module is kept somewhere,
e.g., in an area of the stack that was not overwritten by subsequent
calls, leading to the wrong object count.

Adding a function call right before the first `(gc)' sometimes fixes the
problem, sometimes not.  The attached snippet reliably fixes the problem
on my GNU/Linux sparc64 box, though.

Rob: Would it be possible for you to try out this patch on one of the
Debian SPARC machines?

Thanks in advance,
Ludovic.





  parent reply	other threads:[~2008-02-07 21:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 16:35 guile 1.8.3 fails to build on sparc Kamaraju S Kusumanchi
2007-12-01 17:20 ` Kamaraju S Kusumanchi
2008-01-29 22:52   ` Neil Jerram
2008-02-02  5:33     ` Kamaraju S Kusumanchi
2008-01-29 22:48 ` Neil Jerram
2008-01-31 21:17   ` Greg Troxel
2008-02-01  9:42   ` Ludovic Courtès
2008-02-07 21:53   ` Ludovic Courtès [this message]
2008-02-07 22:01     ` Ludovic Courtès
2012-01-21 19:25       ` Rob Browning
2012-01-27 21:47         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lk5wa0xi.fsf@dellish.bordeaux.inria.fr \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=rlb@defaultvalue.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).