From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Guile Build Errors
Date: Wed, 02 Sep 2009 10:44:10 +0200 [thread overview]
Message-ID: <87k50h20th.fsf@gnu.org> (raw)
In-Reply-To: 25236356.post@talk.nabble.com
Hello,
bornlibra23 <awarikoo@nse.co.in> writes:
>>Can you post the GNU triplet as returned by `./build-aux/config.guess'?
> bash-2.05$ ./build-aux/config.guess
> i786-stratus-vos
I've never seen that.
> +d-aux/compile gcc linker (/system/gnu_library/bin/ld) supports shared
> libraries
> configure:10245: result: no
[...]
> configure:12172: checking whether to build shared libraries
> configure:12193: result: no
That means `load-extension' et al. won't work (we could use Libtool's
preopen magic to make it work with static libraries, but we currently
don't).
I guess your linker supports shared libs but the `configure' somehow
fails to see it. Apparently Libtool's `_LT_LINKER_SHLIBS' M4 macro
hasn't been ported to your platform, leading to this incorrect
diagnostic. Can you report this to bug-libtool@gnu.org?
In the meantime, can you try "./configure --with-gnu-ld" and report the
output of `grep' similarly?
> <unnamed port>: In procedure scm-error in expression (scm-error (quote
> misc-error) #f ...):
> <unnamed port>: Undefined variable: string-ci<?
Hmm, this looks fishy as `string-ci<?' is a primitive procedure defined
in libguile.
> bash-2.05$ ./check-guile
> Testing /users/awarikoo/OpenSource/guile-1.8.7/pre-inst-guile ...
> with GUILE_LOAD_PATH=/users/awarikoo/OpenSource/guile-1.8.7/test-suite
> ERROR: In procedure symbol->string:
> ERROR: Wrong type argument in position 1 (expecting symbol): #<freed cell
> 40087fd0; GC missed a reference>
OK, so it barfs very early.
I don't have access to an "i786" machine, so I'm afraid I won't be able
to help much.
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-09-02 8:44 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
2009-09-01 8:30 ` bornlibra23
2009-09-02 8:44 ` Ludovic Courtès [this message]
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=87k50h20th.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).