From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Build failure in master for GNU: "error: cannot open < lib/../nt/gnulib.mk: No such file or directory"
Date: Wed, 11 Jan 2017 18:22:51 +0000 [thread overview]
Message-ID: <20170111182251.GB10374@acm.fritz.box> (raw)
In-Reply-To: <83y3yhcwij.fsf@gnu.org>
Hello, Eli. Also Lars and Kaushal.
On Wed, Jan 11, 2017 at 07:54:44PM +0200, Eli Zaretskii wrote:
> > Date: Wed, 11 Jan 2017 17:22:20 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > I'm getting this error while trying to build under GNU/Linux:
> > automake-1.15: error: cannot open < lib/../nt/gnulib.mk: No such file or directory
> > Makefile:456: recipe for target 'lib/Makefile.in' failed
> Re-run autogen.sh.
Thanks. I've done that, and my build now builds. But it's _very_ noisy
(in terms of warning messages), and very slow: almost 11 minutes. It
seems only a couple of years ago since a make bootstrap was taking me
between 4 and 5 minutes.
> > . Doesn't *.mk belong to w32 builds?
> No, it belongs to gnulib.
OK, I'll need to learn about that.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-01-11 18:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 17:22 Build failure in master for GNU: "error: cannot open < lib/../nt/gnulib.mk: No such file or directory" Alan Mackenzie
2017-01-11 17:30 ` Lars Ingebrigtsen
2017-01-11 18:49 ` Eli Zaretskii
2017-01-11 19:35 ` Lars Ingebrigtsen
2017-01-11 19:52 ` Eli Zaretskii
2017-01-11 20:36 ` Lars Ingebrigtsen
2017-01-11 21:20 ` Andreas Schwab
2017-01-11 20:08 ` Glenn Morris
2017-01-11 20:34 ` Lars Ingebrigtsen
2017-01-11 17:39 ` Kaushal Modi
2017-01-11 17:41 ` Eric Abrahamsen
2017-01-11 17:54 ` Eli Zaretskii
2017-01-11 18:22 ` Alan Mackenzie [this message]
2017-01-11 18:43 ` Noam Postavsky
2017-01-11 18:50 ` Eli Zaretskii
2017-01-11 18:57 ` Alan Mackenzie
2017-01-11 19:44 ` 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=20170111182251.GB10374@acm.fritz.box \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
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.