From: Kaushal Modi <kaushal.modi@gmail.com>
To: Alan Mackenzie <acm@muc.de>, 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 17:39:57 +0000 [thread overview]
Message-ID: <CAFyQvY3vbiVXZv1PjYWxRJqRxDzuG842axCnc8OiELFAyPowTQ@mail.gmail.com> (raw)
In-Reply-To: <20170111172220.GA10374@acm.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
I faced the same; got fixed after re-running autogen.sh.
On Wed, Jan 11, 2017 at 12:26 PM Alan Mackenzie <acm@muc.de> wrote:
> Hello, Emacs.
>
> 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
>
> . Doesn't *.mk belong to w32 builds?
>
> I updated master at ~ 17:00 +0000 today.
>
> --
> Alan Mackenzie (Nuremberg, Germany).
>
> --
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1239 bytes --]
next prev parent reply other threads:[~2017-01-11 17:39 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 [this message]
2017-01-11 17:41 ` Eric Abrahamsen
2017-01-11 17:54 ` Eli Zaretskii
2017-01-11 18:22 ` Alan Mackenzie
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=CAFyQvY3vbiVXZv1PjYWxRJqRxDzuG842axCnc8OiELFAyPowTQ@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=acm@muc.de \
--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.