unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Guile Build Errors
Date: Mon, 31 Aug 2009 14:38:50 +0200	[thread overview]
Message-ID: <87ljl040px.fsf@gnu.org> (raw)
In-Reply-To: 25167250.post@talk.nabble.com

Hello,

bornlibra23 <awarikoo@nse.co.in> writes:

> I am trying to compile guile-1.8.7 on Stratus Open VOS.

Woow, I had never seen this one, thanks for trying out.  ;-)

Can you post the GNU triplet as returned by `./build-aux/config.guess'?

> I am able to build it successfully but the following errors while testing
> have left me perplexed. I am totally new to guile. Please suggest.
> PASS: test-system-cmds
> ERROR: In procedure dynamic-link:
> ERROR: file: "libguile-srfi-srfi-1-v-3", message: "file not found"

Can you show the output of
"grep -A2 -E '(libtool supports|shared lib)' config.log" (assuming
GNU grep here)?

It may be that Libtool decided not to build shared libraries, in which
case module loading may not work.

> ERROR: In procedure string-append:
> ERROR: Wrong type (expecting string): #<freed cell 400876c0; GC missed a
> reference>
> FAIL: test-bad-identifiers

It shows that there's something wrong GC-wise.  It could be that the
stack is not correctly scanned on this platform.

Could you try to reproduce the problem with a simple test case, e.g., by
running `./pre-inst-guile' and trying

  (begin
    (string-append (make-string 123) (make-string 123))
    (gc))

and variants thereof to try to trigger the problem?

You may want to look at `libguile/gc_os_dep.c' to see how it determines
the stack and whether it makes sense?

You might need to add a new series of #ifdefs, possibly borrowed from
upstream libgc
(http://bdwgc.cvs.sourceforge.net/viewvc/bdwgc/bdwgc/os_dep.c?revision=1.42&view=markup).

> ==================================
> 6 of 16 tests failed
> Please report to bug-guile@gnu.org
> ==================================

Can you also try `./check-guile' and report back?

Thanks,
Ludo'.





  reply	other threads:[~2009-08-31 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27  8:19 Guile Build Errors bornlibra23
2009-08-31 12:38 ` Ludovic Courtès [this message]
2009-09-01  8:30   ` bornlibra23
2009-09-02  8:44     ` Ludovic Courtès
2009-09-02  9:29       ` bornlibra23
2009-09-02 11:49         ` Ludovic Courtès
2009-10-04 22:25           ` Neil Jerram
2009-10-05  9:02             ` 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=87ljl040px.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-user@gnu.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).