From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: 18359@debbugs.gnu.org
Subject: bug#18359: Macro expansion failure [MSYS2-MinGW64]
Date: Sun, 31 Aug 2014 23:40:21 +0200 [thread overview]
Message-ID: <54039645.9010405@alice.it> (raw)
In-Reply-To: <jwvtx4sh1a6.fsf-monnier+emacsbugs@gnu.org>
Il 31/08/2014 22:07, Stefan Monnier ha scritto:
>>> FWIW, the presence of a `bzr' executable should not be needed. And it
>>> should work regardless of the use of lightweight checkouts (which I use
>>> systematically, BTW)
>> With MSYS on MS-Windows?
>
> Same difference. No matter how broken/weird the bzr/git/myfavoritevcs
> setup might be, Emacs should build just fine.
>
> Here "should" means "if it doesn't, I'd consider it as a bug".
I have used the lightweight tree since there was the transition CVS -->
BZR, and it worked just fine on Cygwin and GNU/Linux. It is only on
MSYS2-MinGW64 that there were these issues..
BTW, recent trunk from GIT fails with the Eager macro expansion
failure... (on emacs-devel, others have flagged similar issues)
Ciao,
Angelo.
next prev parent reply other threads:[~2014-08-31 21:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 20:49 bug#18359: Macro expansion failure [MSYS2-MinGW64] Angelo Graziosi
2014-08-30 7:21 ` Eli Zaretskii
2014-08-30 10:20 ` Angelo Graziosi
2014-08-30 14:46 ` Angelo Graziosi
2014-08-30 16:15 ` Angelo Graziosi
2014-08-30 16:37 ` Eli Zaretskii
2014-08-30 16:42 ` Eli Zaretskii
2014-08-30 17:16 ` Angelo Graziosi
2014-08-30 17:55 ` Eli Zaretskii
2014-08-30 20:01 ` Angelo Graziosi
2014-08-31 12:45 ` Stefan Monnier
2014-08-31 15:21 ` Eli Zaretskii
2014-08-31 20:07 ` Stefan Monnier
2014-08-31 21:40 ` Angelo Graziosi [this message]
2014-09-01 0:58 ` Stefan Monnier
2014-09-01 2:40 ` Eli Zaretskii
2016-08-09 1:48 ` npostavs
2014-08-31 21:51 ` Angelo Graziosi
2014-09-01 2:45 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54039645.9010405@alice.it \
--to=angelo.graziosi@alice.it \
--cc=18359@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.