Re: pinfo configure problem - configure.ac (0/1)

[Andrew Schulman <schulman.andrew@epa.gov>]

> > On May 13 07:49, Andrew Schulman wrote:
> > > > 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?
> > > > 
> > > > 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.
> > 
> > autoreconf -f -i?
> 
> Alas, no.
> 
> Here's configure.ac, in case that's helpful.

I seem to have worked around it by setting LIBS=-lncursesw.  Apparently
LIBS is appended to the gcc command line after the list of source files.

Thanks for looking into it.


--
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