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: Trunk r117046 fails on systems with older automake Date: Wed, 07 May 2014 18:14:04 +0300 Message-ID: <83zjitwrib.fsf@gnu.org> References: <868uqh4ust.fsf@gmail.com> <83tx95zffo.fsf@gnu.org> <87y4yh72qk.fsf@igel.home> <87tx956y9c.fsf@igel.home> <864n1459hp.fsf@gmail.com> <86tx92v4zi.fsf@gmail.com> <87eh06jqkl.fsf@uwakimon.sk.tsukuba.ac.jp> <53699719.8030009@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1399475691 28984 80.91.229.3 (7 May 2014 15:14:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 7 May 2014 15:14:51 +0000 (UTC) Cc: emacs-devel@gnu.org To: Andy Moreton Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 07 17:14:44 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Wi3YR-0004sh-IJ for ged-emacs-devel@m.gmane.org; Wed, 07 May 2014 17:14:43 +0200 Original-Received: from localhost ([::1]:41948 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wi3YR-0005fd-1x for ged-emacs-devel@m.gmane.org; Wed, 07 May 2014 11:14:43 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33281) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wi3Xo-0004cu-2d for emacs-devel@gnu.org; Wed, 07 May 2014 11:14:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wi3Xg-00022b-Ih for emacs-devel@gnu.org; Wed, 07 May 2014 11:14:04 -0400 Original-Received: from mtaout29.012.net.il ([80.179.55.185]:41650) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wi3Xg-00021y-4P for emacs-devel@gnu.org; Wed, 07 May 2014 11:13:56 -0400 Original-Received: from conversion-daemon.mtaout29.012.net.il by mtaout29.012.net.il (HyperSendmail v2007.08) id <0N5700800MAEGH00@mtaout29.012.net.il> for emacs-devel@gnu.org; Wed, 07 May 2014 18:15:01 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout29.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N5700PJLMD16080@mtaout29.012.net.il>; Wed, 07 May 2014 18:15:01 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.185 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:171753 Archived-At: > From: Andy Moreton > Date: Wed, 07 May 2014 10:42:31 +0100 > > On Wed 07 May 2014, Paul Eggert wrote: > > > The assumption is that people building from the repository are expert enough > > to use the extra development tools required, and to set up their environments > > so that these extra development tools work. It shouldn't be rocket science, > > and it shouldn't be unreasonable to expect development tools to be installed > > correctly. This particular problem seems isolated to Windows developers and I > > expect they'll work it out among themselves. > > This is exactly the problem - getting a working toolchain is > considerably more difficult on Windows. There are several sets of > incompatible toolchains, and no package manager to install anything. On > other platforms (including Cygwin) this is easy. > > The build requires two distinct sets of tools (msys for autotools and > configure, mingw for building) which live in separate locations and have > different filename translation schemes from posix style naming to the > underlying Windows filesystem. On Windows installing development tools > correctly *is* hard. This is true (although the initial effort of establishing a working build environment is largely a one-time thing). However, you already had such an environment, because AFAIK you were able to build the trunk before. So the only thing that was required by the latest changes on the trunk was to install pkg-config and its macros in pkg.m4, which doesn't sound like a catastrophe, or something too hard to do. Are you saying that there were additional problems, after pkg-config was correctly set up? If so, please describe them. > It would seems from the current issues that Eli is almost the only > developer successfully building for a Windows target from trunk. There's no magic here: my MSYS/MinGW build environment is probably more full than what you have, because I use it a lot, and have built a lot more packages than just Emacs. IOW, I bumped into those problems and solved them long ago. ("ls -l --time=c" tells me that I copied pkg.m4 to the MSYS tree more than a year after installing pkg-config.)