From: Eli Zaretskii <eliz@gnu.org>
To: Alexander Shukaev <haroogan@gmail.com>
Cc: 18955@debbugs.gnu.org
Subject: bug#18955: Fwd: bug#18955: Makefile:382: recipe for target 'src' failed
Date: Wed, 05 Nov 2014 21:00:05 +0200 [thread overview]
Message-ID: <83zjc5tqve.fsf@gnu.org> (raw)
In-Reply-To: <CAKu-7WyX3bH8zkP+-TKdr9Hngk8DzKs=a3T+vQLXvrUcKsm+Fg@mail.gmail.com>
> Date: Wed, 5 Nov 2014 18:33:44 +0100
> From: Alexander Shukaev <haroogan@gmail.com>
>
> Makefile:39: recipe for target
> '/C/Users/Haroogan/Projects/GitHub/MINGW-packages/mingw-w64-emacs/src/emacs/src/macuvs.h'
> failed
> make[2]: ***
> [/C/Users/Haroogan/Projects/GitHub/MINGW-packages/mingw-w64-emacs/src/emacs/src/macuvs.h]
> Error 127
> make[2]: *** Waiting for unfinished jobs....
>
> This file is empty. I can see in the diff that it contained some byte array,
> but during building it became absolutely empty. Got an idea what's going on?
That file is supposed to be generated by uvs.el.
If you delete it and then re-run "make", do you see this rule in
action:
$(srcdir)/macuvs.h $(lispsource)/international/charprop.el: \
bootstrap-emacs$(EXEEXT)
cd ../admin/unidata && $(MAKE) $(MFLAGS) all EMACS="../$(bootstrap_exe)"
If so, are there any error messages when this rule runs?
prev parent reply other threads:[~2014-11-05 19:00 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 15:52 bug#18955: Makefile:382: recipe for target 'src' failed Alexander Shukaev
2014-11-05 16:55 ` Glenn Morris
2014-11-05 17:03 ` Alexander Shukaev
2014-11-05 17:04 ` Glenn Morris
[not found] ` <CAKu-7WzwmwmqCswS+b32zdY6DLZb7G=uLu-8FZjCQgVUvBwNRQ@mail.gmail.com>
2014-11-05 17:33 ` bug#18955: Fwd: " Alexander Shukaev
2014-11-05 17:39 ` Alexander Shukaev
2014-11-05 18:31 ` Glenn Morris
2014-11-05 22:41 ` Alexander Shukaev
2014-11-06 3:48 ` Eli Zaretskii
2014-11-06 13:17 ` Alexander Shukaev
2014-11-06 16:30 ` Eli Zaretskii
2014-11-06 18:48 ` Alexander Shukaev
2014-11-06 19:21 ` Eli Zaretskii
2014-11-06 20:56 ` Alexander Shukaev
2014-11-07 15:02 ` Alexander Shukaev
2014-11-07 15:21 ` Eli Zaretskii
2014-11-07 15:34 ` Alexander Shukaev
2014-11-07 15:36 ` Alexander Shukaev
2014-11-07 15:50 ` Eli Zaretskii
2014-11-07 15:56 ` Alexander Shukaev
2014-11-07 15:57 ` Alexander Shukaev
2014-11-07 19:53 ` Eli Zaretskii
2014-11-07 19:52 ` Eli Zaretskii
2014-11-09 17:30 ` Eli Zaretskii
2014-11-09 17:42 ` Alexander Shukaev
2014-11-09 19:47 ` Eli Zaretskii
2014-11-09 20:10 ` Dani Moncayo
2014-11-09 20:15 ` Eli Zaretskii
2014-11-09 20:25 ` Alexander Shukaev
2014-11-09 20:33 ` Eli Zaretskii
2014-11-09 20:43 ` Dani Moncayo
2014-11-09 20:46 ` Eli Zaretskii
2014-11-09 20:13 ` Alexander Shukaev
2014-11-09 20:28 ` Eli Zaretskii
2014-11-09 20:38 ` Alexander Shukaev
2014-11-09 20:43 ` Alexander Shukaev
2014-11-09 20:49 ` Eli Zaretskii
2014-11-09 22:43 ` Glenn Morris
2014-11-10 7:17 ` Glenn Morris
2014-11-09 20:47 ` Eli Zaretskii
2014-11-05 19:00 ` Eli Zaretskii [this message]
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=83zjc5tqve.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18955@debbugs.gnu.org \
--cc=haroogan@gmail.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.
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).