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:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=KoAhIJjnBKqcNXtY8+/RnyVkJIY2RxMzKIJ17ZCJ2PQs7rKoBeNK5 iHsMKn5Q6XRajWtNrG4QO74OrXqtE0hR4Osjpvy+AVZgIhPUBKqtiHqOWOj+Ewhq aVc3/MBUzeUYeIpM4PEvsIvbzKDWKihZet+dGLUZuLUjneEu7vG31s= 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:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=GY2FGuR/U+ZoRl/fjGUFH1Op43Q=; b=lOCBpJb4E2e2YjX5DBSKqz2yVOSE i5g2VqAshDZpRRDBu2TiMak3vRES+z8RVuJ0TM69EPstZsL7D9NELTK0Outlm1mj Ld9H1UTCdR0pjn0KHpJdcifEVocHnkbvRY3MBrGUg9b5NFOvcfDrTHN9B+hL/MRY e1stU3moCekmFdg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: plane.gmane.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: pinfo configure problem Date: Tue, 13 May 2014 07:49:12 -0400 Lines: 27 Message-ID: References: <05u3n9l6l8pgdeuidskcplb1930mmjtu05 AT 4ax DOT com> <20140513110518 DOT GN2436 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes > On May 13 06:55, Andrew Schulman wrote: > > I'm trying to build pinfo 0.6.10 in 64-bit. The configure script halts, > > claiming "curses is not usable". The command that fails is: > > > > gcc -o conftest.exe -g -O2 -I/usr/include -L/usr/lib -lncursesw > > conftest.c > > > > and this fails because the order of the arguments is wrong. The command > > should be > > > > gcc -o conftest.exe -g -O2 -I/usr/include conftest.c -L/usr/lib > > -lncursesw > > > > and that succeeds. So my question is really an autoconf question: How > > can I tell autoconf to fix the order of the compiler arguments? > > > > My autoconf knowledge is pretty thin I'm afraid. I can provide the > > configure.ac script if that would be helpful. The source is old - I > > think the last real update was in 2007, with a small update posted in > > 2010. > > Doesn't calling `autoreconf' fix this problem? If so, if you use > cygport, the default build strategy contains the autoreconf step. > If you defin your own build function, call cygautoreconf as first > step after `cd ${B}'. No, unfortunately it doesn't. I ran 'autoreconf -i' first. -- 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