From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: 18359@debbugs.gnu.org
Subject: bug#18359: Macro expansion failure [MSYS2-MinGW64]
Date: Sat, 30 Aug 2014 19:37:02 +0300 [thread overview]
Message-ID: <83oav2gci9.fsf@gnu.org> (raw)
In-Reply-To: <5401F8A1.9030102@alice.it>
> Date: Sat, 30 Aug 2014 18:15:29 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> CC: 18359@debbugs.gnu.org
>
> If I build in a source tree created with,
>
> $ bzr checkout --lightweight http://bzr.savannah.gnu.org/r/emacs/trunk emacs
>
> the build fails :
>
> [...]
> Making generated-autoload-file local to *autoload-file* while let-bound!
> Generating autoloads for dired-aux.el...
> Loading macroexp.elc...
> make[2]: ingresso nella directory "/tmp/emacs/lisp"
> make[2]: ingresso nella directory "/tmp/emacs/lisp"
> Compiling ../lisp/button.el
> Compiling ../lisp/startup.el
>
> Searching for program: no such file or directory, bzr
> ????? ^^^^^^^^^^^^^^^^ ?????
Probably because visiting files in a bzr repository invokes
"bzr status", and perhaps a few other bzr commands.
Why are you using lightweight checkouts? Just use a normal branch,
and all these weird problems will go away.
next prev parent reply other threads:[~2014-08-30 16:37 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83oav2gci9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18359@debbugs.gnu.org \
--cc=angelo.graziosi@alice.it \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).