From: David Pirotte <david@altosw.be>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Guile build failure
Date: Thu, 19 Jul 2012 13:45:34 -0300 [thread overview]
Message-ID: <20120719134534.2d07fc8b@rascar> (raw)
In-Reply-To: <87629j68nv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 127 bytes --]
> strace -f -o log ./check-guile
> and then send the part of the log surrounding the failing rmdir(2) call.
sure, attached
[-- Attachment #2: log.bz2 --]
[-- Type: application/x-bzip, Size: 3062 bytes --]
next prev parent reply other threads:[~2012-07-19 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 17:02 GNU Guile 2.0.6 released David Pirotte
2012-07-10 8:18 ` Guile build failure Ludovic Courtès
2012-07-10 15:50 ` David Pirotte
2012-07-11 9:43 ` Ludovic Courtès
2012-07-19 13:59 ` David Pirotte
2012-07-19 16:02 ` Ludovic Courtès
2012-07-19 16:45 ` David Pirotte [this message]
2012-07-21 11:15 ` Ludovic Courtès
2012-07-28 15:55 ` David Pirotte
2012-08-09 13:57 ` Ludovic Courtès
2013-01-21 9:26 ` Andy Wingo
2013-01-21 10:47 ` Ludovic Courtès
2013-01-21 11:39 ` Andy Wingo
2013-01-22 16:43 ` David Pirotte
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=20120719134534.2d07fc8b@rascar \
--to=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=ludo@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).