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

2014-05-13 Thread Andrew Schulman
> On 05/13/2014 01:19 PM, Andrew Schulman wrote: > > > > > AC_CHECK_CURSES calls AC_CHECK_CURSES_COMPILE, which is the step that > > fails. I've included it below. The key step seems to be that it calls > > AC_LINK_IFELSE, with the curses libs (-lncursesw) appended to LDFLAGS. > > That's a bug

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

2014-05-13 Thread Eric Blake
On 05/13/2014 01:19 PM, Andrew Schulman wrote: > > AC_CHECK_CURSES calls AC_CHECK_CURSES_COMPILE, which is the step that > fails. I've included it below. The key step seems to be that it calls > AC_LINK_IFELSE, with the curses libs (-lncursesw) appended to LDFLAGS. That's a bug in AC_CHECK_CUR

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

2014-05-13 Thread Andrew Schulman
> On 05/13/2014 09:32 AM, Andrew Schulman wrote: > > >> autoreconf -f -i? > > > > Alas, no. > > > > Here's configure.ac, in case that's helpful. > > which contains: > > # curses > AC_CHECK_CURSES > if ! test "x$USE_CURSES" = "xtrue"; then > AC_MSG_ERROR([Curses not found. You need curses

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

2014-05-13 Thread Eric Blake
On 05/13/2014 09:32 AM, Andrew Schulman wrote: >> autoreconf -f -i? > > Alas, no. > > Here's configure.ac, in case that's helpful. which contains: # curses AC_CHECK_CURSES if ! test "x$USE_CURSES" = "xtrue"; then AC_MSG_ERROR([Curses not found. You need curses to compile pinfo]) fi Bu

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

2014-05-13 Thread Andrew Schulman
> > 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

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

2014-05-13 Thread Corinna Vinschen
On May 13 11:32, Andrew Schulman wrote: [autoconf.ac] Hmm, I'm not seeing anything fishy in this file. But I'm not the exactly the autoconf expert either. Any autoconf guru available? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer

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

2014-05-13 Thread Andrew Schulman
> 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

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

2014-05-13 Thread Andrew Schulman
configure.ac Description: Binary data

Re: pinfo configure problem

2014-05-13 Thread Corinna Vinschen
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 -

Re: pinfo configure problem

2014-05-13 Thread Andrew Schulman
> 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

Re: pinfo configure problem

2014-05-13 Thread Corinna Vinschen
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 orde

pinfo configure problem

2014-05-13 Thread Andrew Schulman
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