Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by krbdev.mit.edu (8.9.3p2) with ESMTP id TAA11720; Mon, 19 Jun 2006 19:30:13 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by biscayne-one-station.mit.edu (8.13.6/8.9.2) with ESMTP id k5JNUCSr017771; Mon, 19 Jun 2006 19:30:12 -0400 (EDT) Received: from [18.18.1.160] (NOME-KING.MIT.EDU [18.18.1.160]) (authenticated bits=0) (User authenticated as raeburn@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id k5JNU4SU000818 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Mon, 19 Jun 2006 19:30:05 -0400 (EDT) In-Reply-To: References: MIME-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Ken Raeburn Subject: Re: [krbdev.mit.edu #3901] build fails using Autoconf 2.59e (2.60 to be) Date: Mon, 19 Jun 2006 19:29:39 -0400 To: MIT Kerberos RT X-Mailer: Apple Mail (2.750) X-Spam-Score: 3.548 X-Spam-Level: *** (3.548) X-Spam-Flag: NO X-Scanned-BY: MIMEDefang 2.42 RT-Send-Cc: X-RT-Original-Encoding: us-ascii Content-Length: 1149 On Jun 19, 2006, at 19:21, Russ Allbery via RT wrote: > If util/reconf is run with Autoconf 2.59e (using the snapshot version > shipped with Debian at the time of this report), the build then fails. > One obvious problem is that some Autoconf variables are now > relative to > datarootdir and therefore datarootdir has to be set in Makefiles > (mandir > in particular is subject to this) or installation locations are wrong. Okay, that'd go in config/pre.in... > making all in util/support... > make[2]: Entering directory `/home/eagle/dvl/krb5/src/util/support' > make[2]: *** No rule to make target `all-liblinks', needed by > `all-unix'. Stop. Does "all-liblinks:" show up in that makefile? There should be a line coming from post.in that makes it depend on $(LIBLINKS), which should be set to whatever the top-level configure script substituted for @LIBLINKS@, which shouldn't be empty.... We can use earlier versions of autoconf to build our release, but if it's an autoconf bug it'd be good to catch it before they make a final release.... If I get a chance, perhaps I'll look into it later.... Ken