From: "Ludovic Courtès" <ludo@gnu.org>
To: "Tomasz Kłoczko" <kloczko.tomasz@gmail.com>
Cc: 39193@debbugs.gnu.org
Subject: bug#39193: guile 3.0.0 does not build
Date: Mon, 20 Jan 2020 10:26:38 +0100 [thread overview]
Message-ID: <87zheih41d.fsf@gnu.org> (raw)
In-Reply-To: <CABB28Cyd7X=LH13iVhfHs+M_Ey_3TUqNcQSqn86nocgjZ9mahg@mail.gmail.com> ("Tomasz \=\?utf-8\?Q\?K\=C5\=82oczko\=22's\?\= message of "Sun, 19 Jan 2020 11:48:31 +0100")
Hi Tomasz,
Tomasz Kłoczko <kloczko.tomasz@gmail.com> skribis:
> checking for BDW_GC... yes
> checking for GC_pthread_exit... no
> checking for GC_pthread_cancel... no
> checking for GC_pthread_sigmask... no
> checking for GC_move_disappearing_link... no
> checking for GC_is_heap_ptr... no
Could you send ‘config.log’, or at least the subset that corresponds to
the checks above?
Thanks for your report,
Ludo’.
prev parent reply other threads:[~2020-01-20 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 10:48 bug#39193: guile 3.0.0 does not build Tomasz Kłoczko
2020-01-20 9:26 ` Ludovic Courtès [this message]
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=87zheih41d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39193@debbugs.gnu.org \
--cc=kloczko.tomasz@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).