all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
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 21:44:46 +0200	[thread overview]
Message-ID: <83pojtcrf5.fsf@gnu.org> (raw)
In-Reply-To: <20170111185717.GD10374@acm.fritz.box> (message from Alan Mackenzie on Wed, 11 Jan 2017 18:57:17 +0000)

> Date: Wed, 11 Jan 2017 18:57:17 +0000
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> > Did you use "make -jN", with some suitable value of N?
> 
> Yes, I've been using make -j5 for many, many years, ever since I first
> installed Gentoo.
> 
> The build time seems effectively to have doubled in a very small number
> of years.

The worst offender is ucs-normalize.el, which is now byte-compiled
using bootstrap-emacs, i.e with a byte-compiler that's interpreted
from Lisp source.



      reply	other threads:[~2017-01-11 19:44 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
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 [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pojtcrf5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.