From: ludo@gnu.org (Ludovic Courtès)
To: Ed Green <eug2@psu.edu>
Cc: 17399@debbugs.gnu.org
Subject: bug#17399: compilation bugs when making guile-2.0.11
Date: Wed, 28 May 2014 19:35:40 +0200 [thread overview]
Message-ID: <87tx89dcwj.fsf@gnu.org> (raw)
In-Reply-To: <536580BD.5030205@psu.edu> (Ed Green's message of "Sat, 03 May 2014 19:50:21 -0400")
Hello,
Could you send your config.log file as an attachment, for further
investigation?
Thanks in advance,
Ludo’.
prev parent reply other threads:[~2014-05-28 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 23:50 bug#17399: compilation bugs when making guile-2.0.11 Ed Green
2014-05-28 17:35 ` 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=87tx89dcwj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=17399@debbugs.gnu.org \
--cc=eug2@psu.edu \
/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).