From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Bootstrap failure using 'make -j4' [Cygwin] Date: Sat, 22 May 2010 17:10:16 +0300 Message-ID: <831vd4owmv.fsf@gnu.org> References: <4BF69E5B.7040006@alice.it> <83vdahz0v0.fsf@gnu.org> <4BF6BB85.3010504@alice.it> <83r5l5yw33.fsf@gnu.org> <4BF70D0B.9050106@alice.it> <83d3wozamt.fsf@gnu.org> <4BF7B965.9040203@swipnet.se> <838w7cp0hx.fsf@gnu.org> <4BF7D551.1020204@swipnet.se> <834oi0oyw6.fsf@gnu.org> <4BF7E215.3060005@swipnet.se> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: dough.gmane.org 1274537430 22729 80.91.229.12 (22 May 2010 14:10:30 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 22 May 2010 14:10:30 +0000 (UTC) Cc: emacs-devel@gnu.org, angelo.graziosi@alice.it To: =?ISO-8859-1?Q?Jan_Dj=E4rv?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 22 16:10:29 2010 connect(): No such file or directory Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OFpPI-0007O5-Dm for ged-emacs-devel@m.gmane.org; Sat, 22 May 2010 16:10:28 +0200 Original-Received: from localhost ([127.0.0.1]:46321 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OFpPH-0004YQ-Gy for ged-emacs-devel@m.gmane.org; Sat, 22 May 2010 10:10:27 -0400 Original-Received: from [140.186.70.92] (port=37417 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OFpPA-0004XC-Aj for emacs-devel@gnu.org; Sat, 22 May 2010 10:10:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OFpP8-0001e9-HK for emacs-devel@gnu.org; Sat, 22 May 2010 10:10:20 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:39053) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OFpP8-0001du-A1 for emacs-devel@gnu.org; Sat, 22 May 2010 10:10:18 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0L2T00H00RAIYI00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Sat, 22 May 2010 17:10:16 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([77.127.33.125]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0L2T009VURD3VZI0@a-mtaout22.012.net.il>; Sat, 22 May 2010 17:10:16 +0300 (IDT) In-reply-to: <4BF7E215.3060005@swipnet.se> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:125074 Archived-At: > Date: Sat, 22 May 2010 15:54:29 +0200 > From: Jan Dj=E4rv > CC: angelo.graziosi@alice.it, emacs-devel@gnu.org >=20 > > Generally, stick to the widely-supported (usually POSIX-s= pecified) > > options and features of these programs. For example, don't = use `mkdir > > -p', convenient as it may be, because a few systems don't su= pport it at > > all and with others, it is not safe for parallel execution. > > > > If this is no longer a consideration, perhaps we should ask Richa= rd to > > amend standards.texi. > > >=20 > Well, -p is in POSIX now, so I guess the standards needs to be upda= ted on that=20 > 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 somethin= g the GNU=20 > coding standards says not to do. So I really don't know how releva= nt the GNU=20 > 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.