From: Eli Zaretskii <eliz@gnu.org>
To: Andy Wingo <wingo@pobox.com>
Cc: 10474@debbugs.gnu.org, commander.sirow@googlemail.com
Subject: bug#10474: Building guile 2.x under mingw + msys
Date: Tue, 17 Jan 2012 10:09:21 +0200 [thread overview]
Message-ID: <83ehuy698u.fsf@gnu.org> (raw)
In-Reply-To: <87pqerdxq4.fsf@pobox.com>
[I removed guile-user@gnu.org from the CC list; let me know if that is
not TRT.]
> Date: Tue, 10 Jan 2012 23:00:35 +0100
> Cc: guile-user@gnu.org, 10474@debbugs.gnu.org
>
> > so I've been trying to build guile 2.0.3 from source with mingw (gcc 4.6.2) + msys.
>
> Thanks for the report!
I have a similar, although slightly different in details, experience.
(I will post the details as soon as the saga is finished for me and I
have all it figured out ;-)
> > make[3]: Entering directory `/home/Commander/guile-2.0.3/libguile'
> > GEN guile-procedures.texi
> > Throw without catch before boot:
> > Throw to key system-error with args ("canonicalize-path" "~A" ("No such file or
> > directory") (2))Aborting.
>
> AIUI the canonicalize_path binding that gnulib provides for mingw ends
> up shelling out to `rm' and other commands.
I don't think this is true; at least I don't see any such shelling out
in lib/canonicalize-lgpl.c, which I believe is the module you allude
to.
The problem, AFAIK, is entirely different and quite mundane:
canonicalize_file_name simply does not support Windows-style
D:/foo/bar file names, nor does it support backslashes as separators
in file names.
My evidence is that I added an fprintf to canonicalize-path where it
calls canonicalize_file_name, and the file name passed to it was
entirely reasonable, something like
D:\path\to\guile-2.03/module/ice-9/boot-9.scm
(or some such, I'm writing this from my faulty memory).
I think I know how to fix canonicalize_file_name, and I will send a
tentative patch later, perhaps even today, when I have it working and
get past this abort.
next prev parent reply other threads:[~2012-01-17 8:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL+StqnixLW+QwOP2BpZrjnz1wAQjnio9H6P=VM=9Cnn-B2-ng@mail.gmail.com>
2012-01-10 22:00 ` bug#10474: Building guile 2.x under mingw + msys Andy Wingo
[not found] ` <87pqerdxq4.fsf@pobox.com>
2012-01-17 8:09 ` Eli Zaretskii [this message]
2012-01-17 18:14 ` Eli Zaretskii
2012-01-18 23:55 ` Ludovic Courtès
2012-01-19 4:04 ` Eli Zaretskii
2012-02-02 0:59 ` Andy Wingo
2012-02-02 3:53 ` Eli Zaretskii
2012-02-02 16:39 ` Ludovic Courtès
2012-02-02 17:14 ` Eli Zaretskii
2012-02-02 17:34 ` Eli Zaretskii
2013-02-18 18:10 ` Andy Wingo
2013-02-18 19:56 ` Eli Zaretskii
2013-02-19 10:44 ` Andy Wingo
2013-02-19 12:55 ` Ludovic Courtès
2013-02-19 13:39 ` Andy Wingo
2013-02-19 17:53 ` Eli Zaretskii
2013-02-19 21:44 ` Andy Wingo
2013-02-20 19:16 ` Eli Zaretskii
2013-02-24 12:08 ` Andy Wingo
2013-02-19 15:47 ` Andy Wingo
2013-02-19 18:00 ` Eli Zaretskii
2013-02-24 13:25 ` Andy Wingo
2013-02-24 15:43 ` Eli Zaretskii
2013-05-07 17:18 ` bug#14361: Building guile 2.0.9 " Eli Zaretskii
2016-06-20 21:19 ` Andy Wingo
2016-06-21 12:46 ` Eli Zaretskii
2016-06-21 15:06 ` Andy Wingo
2016-06-21 15:42 ` Eli Zaretskii
2016-06-21 20:52 ` Andy Wingo
2016-06-24 9:51 ` Eli Zaretskii
2013-02-19 21:39 ` bug#10474: Building guile 2.x " Andy Wingo
2013-02-20 19:14 ` Eli Zaretskii
2013-02-20 21:57 ` Andy Wingo
2013-02-21 3:49 ` Eli Zaretskii
2013-02-21 8:18 ` Andy Wingo
2012-01-19 17:35 ` Eli Zaretskii
2012-01-21 11:09 ` Eli Zaretskii
2012-01-24 12:27 ` Eli Zaretskii
2012-01-25 21:12 ` Ludovic Courtès
2012-01-26 5:37 ` Eli Zaretskii
2012-01-29 18:30 ` Ludovic Courtès
2012-01-29 19:17 ` Eli Zaretskii
2012-01-29 22:56 ` Ludovic Courtès
2012-01-10 21:58 Andy Wingo
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=83ehuy698u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10474@debbugs.gnu.org \
--cc=commander.sirow@googlemail.com \
--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).