From: Andy Wingo <wingo@pobox.com>
To: "Ludovic Courtès" <ludo@gnu.org>, bug-guile@gnu.org
Subject: Re: [bug #30170] Auto-compilation erroneously recompiles dependencies [1.9.11]
Date: Fri, 18 Jun 2010 19:05:31 +0200 [thread overview]
Message-ID: <m3hbl0e0f8.fsf@pobox.com> (raw)
In-Reply-To: <20100618-145453.sv15145.14315@savannah.gnu.org> ("Ludovic Courtès"'s message of "Fri, 18 Jun 2010 14:54:53 +0000")
On Fri 18 Jun 2010 16:54, Ludovic Courtès <INVALID.NOREPLY@gnu.org> writes:
> Andy> Is it because of "."? What if you replaced "." with `pwd` ?
>
> Indeed, that solves the problem:
[...]
> Missing a `canonicalize-path'?
It would seem so. Would you like to fix this? :-) Look in load.c:763.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-06-18 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 13:20 [bug #30170] Auto-compilation erroneously recompiles dependencies [1.9.11] Ludovic Courtès
2010-06-18 8:33 ` Andy Wingo
2010-06-18 14:54 ` Ludovic Courtès
2010-06-18 17:05 ` Andy Wingo [this message]
2010-06-20 14:55 ` Ludovic Courtès
2010-06-20 16:13 ` Ludovic Courtès
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=m3hbl0e0f8.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=bug-guile@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).