From: Andy Wingo <wingo@pobox.com>
To: primus <rprimus@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: [1.9.12][OpenBSD] run time failure ...
Date: Fri, 10 Sep 2010 16:35:27 +0200 [thread overview]
Message-ID: <m38w39fyz4.fsf@unquote.localdomain> (raw)
In-Reply-To: <20100910134726.GF18170@x.lence.net> (primus's message of "Fri, 10 Sep 2010 14:47:26 +0100")
On Fri 10 Sep 2010 15:47, primus <rprimus@gmail.com> writes:
> On Fri, Sep 10, 2010 at 10:39:01AM +0200, Andy Wingo wrote:
>> On Thu 09 Sep 2010 00:12, primus <rprimus@gmail.com> writes:
>>
>> > backtrace with new cvs libgc.
>>
>> Thanks. At this point the problems appears to be related to an
>> dynamically-loaded extension, like srfi-1. This looks like you are
>> building a static-only Guile, and we don't usually test that.
>
> Fri Sep 10 14:45:17 BST 2010
>
> Hi Andy,
>
> Nowhere do I specify that it should be a
> static-only build.
It's statically linking libguile to guile. You sure you didn't pass
--disable-shared on the configure line? Surely libtool can make shared
libraries on openbsd?
> # ldd ./libguile/guile
> ./libguile/guile:
> Start End Type Open Ref GrpRef Name
> 1c000000 3c042000 exe 1 0 0 ./libguile/guile
[...]
Here guile should probably be a libtool helper script, and
libguile/.libs/lt-guile should link to libguile-2.0.so.
>>
>> So... If you type meta/guile -c '(format #t "hello world\n")' that
>> should display hello world. Now we need to figure out what's going on
>> with --disable-shared builds.
>
> # meta/guile -c '(format #t "hello world\n")'
> ;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;; or pass the --no-autocompile argument to disable.
Ah yes. But meta/guile --no-autocompile -c '(format #t "hello world\n")'
works?
A
--
http://wingolog.org/
next prev parent reply other threads:[~2010-09-10 14:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 19:21 [1.9.12][OpenBSD] run time failure primus
2010-09-08 19:46 ` Andy Wingo
2010-09-08 20:07 ` primus
2010-09-08 21:58 ` Ludovic Courtès
2010-09-08 22:12 ` primus
2010-09-10 8:39 ` Andy Wingo
2010-09-10 13:47 ` primus
2010-09-10 14:35 ` Andy Wingo [this message]
2010-09-10 15:44 ` primus
2010-09-10 21:37 ` Ludovic Courtès
2010-09-10 16:44 ` [1.9.12][OpenBSD] [SOLUTION] " primus
2010-09-10 21:29 ` [1.9.12][OpenBSD] " Ludovic Courtès
2010-09-12 11:32 ` Andy Wingo
2010-09-12 17:41 ` Ludovic Courtès
2010-09-12 20:26 ` Andy Wingo
2010-09-12 20:38 ` Ludovic Courtès
2010-09-12 21:41 ` Andy Wingo
2010-09-08 23:06 ` [1.9.12][OpenBSD] CFLAGS="-g -O0" " primus
2010-09-10 8:41 ` Andy Wingo
2010-09-10 13:53 ` primus
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=m38w39fyz4.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=rprimus@gmail.com \
/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).