From: shookie@email.de
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 13848@debbugs.gnu.org
Subject: bug#13848: Statically linking guile-2.0.
Date: Sun, 10 Mar 2013 22:17:14 +0100 [thread overview]
Message-ID: <E8D489D3-6884-4130-AA1C-624C2B07B1EC@email.de> (raw)
In-Reply-To: <87ehfnvz2d.fsf@pobox.com>
I immediately tried it. And after the time spec fixes it looks good so far. The first few GUILECs came through without a hitch. It takes ages though. So might be a while until you hear from me gain.
Regards
Jan Schukat
On 10.03.2013, at 20:23, Andy Wingo <wingo@pobox.com> wrote:
> On Sun 10 Mar 2013 18:32, Andy Wingo <wingo@pobox.com> writes:
>
>>> The problem is, when I do build bdw-gc with posix threads, the guile
>>> module compiling is all broken, it periodically drops messages like
>>> this:
>>>
>>> GUILEC ice-9/eval.go
>>> Backtrace:
>>> In unknown file:
>>> ?: 3 [apply-smob/1 #<boot-closure 192c100 (_ _ _)> #t ...]
>>> ?: 2 [apply-smob/1 #<catch-closure 1ccee70>]
>>> ?: 1 [primitive-eval ((@ # %) (begin # # #))]
>>> ?: 0 [chmod #<closed: file 0> 438]
>
> I have made what might be a fix for this issue. Can you try this
> tarball:
>
> http://wingolog.org/priv/guile-2.0.7.182-e9381.tar.gz
>
> Thanks,
>
> Andy
> --
> http://wingolog.org/
next prev parent reply other threads:[~2013-03-10 21:17 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 16:19 bug#13848: Statically linking guile-2.0 Jan Schukat
2013-03-02 15:28 ` Ludovic Courtès
2013-03-03 23:20 ` Jan Schukat
2013-03-05 0:54 ` Jan Schukat
2013-03-05 10:22 ` Ludovic Courtès
2013-03-05 15:44 ` Jan Schukat
2013-03-05 17:25 ` Ludovic Courtès
2013-03-05 22:25 ` Jan Schukat
2013-03-06 23:12 ` Ludovic Courtès
2013-03-09 13:44 ` Jan Schukat
2013-03-09 23:06 ` Andy Wingo
2013-03-09 23:57 ` shookie
2013-03-10 4:09 ` shookie
2013-03-10 17:32 ` Andy Wingo
2013-03-10 18:54 ` shookie
2013-03-10 19:23 ` Andy Wingo
2013-03-10 21:17 ` shookie [this message]
2013-03-10 22:03 ` shookie
2013-03-10 22:53 ` Andy Wingo
2013-03-11 0:07 ` shookie
2013-03-11 1:43 ` shookie
2013-03-11 8:26 ` Andy Wingo
2013-03-11 9:30 ` shookie
2013-03-13 9:30 ` Andy Wingo
2013-03-13 19:04 ` bug#13848: Aw: " Jan Schukat
2013-03-16 1:36 ` Jan Schukat
2013-03-29 19:35 ` Ludovic Courtès
2013-03-30 0:20 ` Jan Schukat
2013-03-30 21:27 ` Ludovic Courtès
2013-04-05 23:14 ` Jan Schukat
2013-04-07 10:20 ` Ludovic Courtès
2013-04-07 16:20 ` bug#13848: Aw: " Jan Schukat
2013-04-07 18:22 ` Andy Wingo
2013-04-07 19:18 ` bug#13848: Aw: " Jan Schukat
2013-04-07 20:00 ` Ludovic Courtès
2013-04-07 21:06 ` bug#13848: Aw: " Jan Schukat
2013-04-08 7:48 ` Ludovic Courtès
2013-03-10 17:38 ` shookie
2013-03-10 17:38 ` shookie
2013-03-14 13:54 ` Ludovic Courtès
2013-03-09 9:32 ` Andy Wingo
2013-03-09 15:42 ` Jan Schukat
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=E8D489D3-6884-4130-AA1C-624C2B07B1EC@email.de \
--to=shookie@email.de \
--cc=13848@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.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).