From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bootstrap failure using 'make -j4' [Cygwin]
Date: Sun, 23 May 2010 13:51:22 +0200 [thread overview]
Message-ID: <4BF916BA.2090000@alice.it> (raw)
In-Reply-To: <83d3wozamt.fsf@gnu.org>
Il 22/05/2010 8.57, Eli Zaretskii ha scritto:
> If you have only 2 cores, then -j4 is not really useful, is it? You
> will never have more than 2 jobs running at the same time. I think
> the usual rule of thumb is to use 1.5 times the number of cores as the
> argument to -j. In your case, that would be -j3.
Just for completeness, whenever I use -j2, -j3, -j4, I find always this
warning:
[...]
if [ -x ./config.status ]; then \
./config.status; \
else \
./configure --enable-maintainer-mode; \
fi
config.status: creating Makefile
config.status: creating lib-src/Makefile
config.status: creating oldXMenu/Makefile
config.status: creating doc/emacs/Makefile
config.status: creating doc/misc/Makefile
config.status: creating doc/lispintro/Makefile
config.status: creating doc/lispref/Makefile
config.status: creating src/Makefile.c
config.status: creating lwlib/Makefile
config.status: creating lisp/Makefile
config.status: creating leim/Makefile
config.status: creating src/config.h
config.status: executing default commands
creating src/epaths.h
make[1]: Entering directory `/tmp/emacs/build'
make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent
make rule.
make[1]: Leaving directory `/tmp/emacs/build'
[...]
=======================
Ciao,
Angelo.
next prev parent reply other threads:[~2010-05-23 11:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 14:53 Bootstrap failure using 'make -j4' [Cygwin] Angelo Graziosi
2010-05-21 16:16 ` Eli Zaretskii
2010-05-21 16:57 ` Angelo Graziosi
2010-05-21 17:43 ` Eli Zaretskii
2010-05-21 17:59 ` Eli Zaretskii
2010-05-21 18:45 ` Eli Zaretskii
2010-05-21 22:45 ` Angelo Graziosi
2010-05-22 6:57 ` Eli Zaretskii
2010-05-22 7:16 ` Glenn Morris
2010-05-22 7:29 ` Glenn Morris
2010-05-22 8:19 ` Eli Zaretskii
2010-05-22 11:20 ` Andreas Schwab
2010-05-22 12:53 ` Eli Zaretskii
2010-05-22 11:00 ` Jan Djärv
2010-05-22 12:46 ` Eli Zaretskii
2010-05-22 13:00 ` Jan Djärv
2010-05-22 13:06 ` David Engster
2010-05-22 13:45 ` Jan Djärv
2010-05-22 13:21 ` Eli Zaretskii
2010-05-22 13:41 ` David Engster
2010-05-22 14:00 ` Jan Djärv
2010-05-22 13:54 ` Jan Djärv
2010-05-22 14:10 ` Eli Zaretskii
2010-05-22 13:35 ` Angelo Graziosi
2010-05-22 14:08 ` Eli Zaretskii
2010-05-23 11:51 ` Angelo Graziosi [this message]
2010-05-23 17:12 ` 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=4BF916BA.2090000@alice.it \
--to=angelo.graziosi@alice.it \
--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 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).