From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jim Meyering Newsgroups: gmane.emacs.devel Subject: Re: Still unable to build trunk Date: Sun, 23 Jan 2011 16:33:00 +0100 Message-ID: <877hdvd49f.fsf@meyering.net> References: <87y66fv2d3.fsf@stupidchicken.com> <4D388F7F.20708@swipnet.se> <87r5c7jk5m.fsf@stupidchicken.com> <4D39EF9C.1050804@cs.ucla.edu> <4D3A8666.4070609@cs.ucla.edu> 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 1295796801 16970 80.91.229.12 (23 Jan 2011 15:33:21 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 23 Jan 2011 15:33:21 +0000 (UTC) Cc: cyd@stupidchicken.com, Paul Eggert , jan.h.d@swipnet.se, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 23 16:33:15 2011 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 1Ph1wI-0003wE-6Z for ged-emacs-devel@m.gmane.org; Sun, 23 Jan 2011 16:33:14 +0100 Original-Received: from localhost ([127.0.0.1]:34978 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ph1wH-0007pW-Oe for ged-emacs-devel@m.gmane.org; Sun, 23 Jan 2011 10:33:13 -0500 Original-Received: from [140.186.70.92] (port=47969 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ph1wC-0007p9-FK for emacs-devel@gnu.org; Sun, 23 Jan 2011 10:33:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ph1wB-0003lG-Bd for emacs-devel@gnu.org; Sun, 23 Jan 2011 10:33:08 -0500 Original-Received: from mx.meyering.net ([82.230.74.64]:52371) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ph1w9-0003il-Me; Sun, 23 Jan 2011 10:33:05 -0500 Original-Received: by rho.meyering.net (Acme Bit-Twister, from userid 1000) id 45BE56016F; Sun, 23 Jan 2011 16:33:00 +0100 (CET) In-Reply-To: (Eli Zaretskii's message of "Sat, 22 Jan 2011 10:03:12 -0500") Original-Lines: 70 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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:134863 Archived-At: Eli Zaretskii wrote: >> Date: Fri, 21 Jan 2011 23:25:26 -0800 >> From: Paul Eggert >> Cc: Jan Dj=E4rv , emacs-devel@gnu.org >> >> One way to address this issue is to say that maintainers should >> have automake installed. That's normal for other packages, but >> I'd rather minimize changes to the assumptions for Emacs. > > What is the meaning of "maintainers" in this context? Does that mean > anyone who builds the development trunk? If so, that's a very large > population, most of them not really "maintain" Emacs, and I'm not sure > we want to request that all of them have automake installed. > > In any case, if we do, there should be clear information about the > version(s) of all the auto-tools that are required to build Emacs > correctly and seamlessly. The file INSTALL.BZR in the top-level > directory sounds like the right place. It currently says nothing > about these requirements, AFICS. Hi Eli, By "maintainers", he meant "anyone who builds from VC-cloned sources." In many gnulib-using projects, we address two types of users who build from source: - those who build from a distribution tarball - those who build from upstream clone/checkout Obviously, when building from a tarball, there are only the usual, minimal requirements specified in the GCS. E.g., use of autoconf, automake, makein= fo, etc. are not required. However, those who build from the latest sources, as checked out from version control must have tools that meet certain standards. In coreutils, for example, we address that with the combination of documentation via two README files: README-hacking README-prereq http://git.sv.gnu.org/cgit/coreutils.git/tree/README-hacking http://git.sv.gnu.org/cgit/coreutils.git/tree/README-prereq # We also have HACKING, but it targets those contributing patches: http://git.sv.gnu.org/cgit/coreutils.git/tree/HACKING and an automated check for the presence and minimal-acceptable versions of build-related tools (this is from bootstrap.conf): # Build prerequisites buildreq=3D"\ autoconf 2.62 automake 1.11.1 autopoint - bison - gettext 0.17 git 1.4.4 gperf - gzip - makeinfo - patch - perl 5.5 rsync - tar - xz - " Since anyone building coreutils from VC'd sources must run our ./bootstrap script, they will learn very quickly if they lack one of the required build tools.