unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Sat, 22 May 2010 15:35:34 +0200	[thread overview]
Message-ID: <4BF7DDA6.6060009@alice.it> (raw)
In-Reply-To: <83d3wozamt.fsf@gnu.org>

The problem seems fixed in rev 100412, 'make -j4' works just fine 
(thanks for having clarified the cores usage of CPU)

And...

Il 22/05/2010 8.57, Eli Zaretskii ha scritto:
> Thanks.  I think your problem begins with this error message I see in
> the log:
>
>     mkdir: impossibile creare la directory "deps": File exists

for completeness, I noticed this error on GNU/Linux because it caused 
the build to be stopped... But there I thought this was caused by some 
garbage from a previous build and, really, after deleting the build 
tree, I was able to bootstrap...

Ciao,
Angelo.

PS. Should I test what follow in any case?

> This comes from the following fragment in src/Makefile.in:
>
>      .c.o:
> 	    @$(MKDEPDIR)
> 	    $(CC) -c $(CPPFLAGS) $(ALL_CFLAGS) $<
>
> where MKDEPDIR expands to this:
>
>      test -d ${DEPDIR} || mkdir ${DEPDIR}
>
> Now, if more than one .c.o rule tries to create the `deps'
> subdirectory at the same time, one of them might lose due to a race
> condition, and fail the entire compilation.
>
> Could you please try changing this line:
>
> 	    @$(MKDEPDIR)
> into
> 	    -@$(MKDEPDIR)
>
> and see if that makes the problem go away?




  parent reply	other threads:[~2010-05-22 13:35 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 [this message]
2010-05-22 14:08             ` Eli Zaretskii
2010-05-23 11:51           ` Angelo Graziosi
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=4BF7DDA6.6060009@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).