From: Eli Zaretskii <eliz@gnu.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org, angelo.graziosi@alice.it
Subject: Re: Bootstrap failure using 'make -j4' [Cygwin]
Date: Sat, 22 May 2010 17:10:16 +0300 [thread overview]
Message-ID: <831vd4owmv.fsf@gnu.org> (raw)
In-Reply-To: <4BF7E215.3060005@swipnet.se>
> Date: Sat, 22 May 2010 15:54:29 +0200
> From: Jan Djärv <jan.h.d@swipnet.se>
> CC: angelo.graziosi@alice.it, emacs-devel@gnu.org
>
> > Generally, stick to the widely-supported (usually POSIX-specified)
> > options and features of these programs. For example, don't use `mkdir
> > -p', convenient as it may be, because a few systems don't support it at
> > all and with others, it is not safe for parallel execution.
> >
> > If this is no longer a consideration, perhaps we should ask Richard to
> > amend standards.texi.
> >
>
> Well, -p is in POSIX now, so I guess the standards needs to be updated on that
> point. But it is still not parallel safe.
If it's not parallel safe, it might be a problem in this case, since
multiple .c.o rules could invoke it in parallel under "make -j".
> Emacs uses prototypes in C without macros now, and that is something the GNU
> coding standards says not to do. So I really don't know how relevant the GNU
> Coding standards are for Emacs developemnt.
They are relevant, and the document is actively maintained. Any
anachronisms you find there I suggest to report to Richard.
next prev parent reply other threads:[~2010-05-22 14:10 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 [this message]
2010-05-22 13:35 ` Angelo Graziosi
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=831vd4owmv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=angelo.graziosi@alice.it \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
/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).