X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; q=dns; s=default; b=PAo
	hYupV7xFpX25RaiL6lzbkZD8ww3egKlcYyZl+qrZHoqTNtfSifRN/bWOo+JJ1oi7
	zXa4b9vy+ILz3On9i6AYdKK1BLnJv7X4ZJidYuIVqTx4YoIr3DlKlG9e1H0ErYh9
	nqmK4Q5xqXOsZvvRAWFaP1mQMqEBwUTA1fM6vI7o=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; s=default; bh=pMSkh8wT7
	9JrrgPUwPCFW/fuDS0=; b=AnVScZ5H8hFGPEkVoIYFduhdpTjJvXvyQyPU31FLW
	PsXXp6/DRiYdMk0IzOEV/qQ4HNeQMLxA+gI9t4Q2RvYT3hVdcVYVG7zfK6jVzo6a
	zzIzGmU6zSHIMUWD7e/nqEFtH2s7gpTv9QYDv5BofpN4u24yuOpYK0/zqhnFjfw4
	9Y=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-2.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,TW_YG autolearn=ham version=3.3.1
Message-ID:	<516D768E.5000708@etr-usa.com>
Date:	Tue, 16 Apr 2013 10:04:30 -0600
From:	Warren Young <warren AT etr-usa DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version:	1.0
To:	Cygwin-L <cygwin AT cygwin DOT com>
Subject:	cygport autoreconf --force step stomping on perfectly good config.guess file

In trying to get sqlite3 built for 64-bit Cygwin, I've run into a wall: 
during the cygport compile step, it runs

     autoreconf --force -i --verbose

This overwrites the config.guess shipped with SQLite with the one from 
automake 1.9.  (I know this for a fact based on file sizes.)  That old 
version doesn't understand Cygwin 64, so it gives a verbose error that 
amounts to "upgrade, dude."  If autoreconf were to grab the config.guess 
from automake 1.13 or the one shipped with Cygport itself, all would be 
well.

I'm guessing this happens due to this line in SQLite's configure script:

     am__api_version="1.9"

I can't run autoconf to re-generate this, since the configure.ac file 
has a bunch of old constructs that autoconf 2.69 barfs on.

I don't want to suppress the autoreconf step, since the SQLite tarball 
*also* includes an outdated config.guess script.  So, autoreconf *does* 
need to be run.  It just needs to be made to DTRT.

My subject line refers to the fact that even if I copy a good 
config.guess file in by hand between the prep and compile steps, 
autoreconf overwrites it anyway, probably because of the --force flag.

Ultimately, upstream should upgrade their autotools and fix their .in 
and .ac files, but seeing as how they just applied a trivial patch I 
provided 3 years ago, I'm not going to hold my breath waiting.

Any suggestions on how to fix this without involving upstream, and 
without wholesale replacement of the autotools input files shipped with 
the SQLite tarball?

My guess is that it would be best if I could slip a custom step in 
between the 'autoreconf' step and the 'make' step, hand-copying in an 
up-to-date version of config.guess from somewhere.  Does cygport have 
such a hook?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -