This is the mail archive of the
mailing list for the Cygwin project.
Re: pinfo configure problem - configure.ac (0/1)
- From: Andrew Schulman <schulman dot andrew at epa dot gov>
- To: cygwin at cygwin dot com
- Date: Tue, 13 May 2014 15:19:52 -0400
- Subject: Re: pinfo configure problem - configure.ac (0/1)
- Authentication-results: sourceware.org; auth=none
- References: <05u3n9l6l8pgdeuidskcplb1930mmjtu05 at 4ax dot com> <20140513110518 dot GN2436 at calimero dot vinschen dot de> <ui14n9t5gv0sepatqtpocqqlodgcve9gi3 at 4ax dot com> <20140513115410 dot GP2436 at calimero dot vinschen dot de> <sfe4n955rf2f5571oepq2l0tffi4hr1l4b at 4ax dot com> <537269E3 dot 5080509 at redhat dot com>
> 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
> if ! test "x$USE_CURSES" = "xtrue"; then
> AC_MSG_ERROR([Curses not found. You need curses to compile pinfo])
> But without a definition for AC_CHECK_CURSES, I still don't know enough.
> I hate packages that assume they can use the AC_ namespace for their
> third-party macros. Can you find the definition of that macro in a .m4
> file that gets included? That's probably the place that's creating the
> bogus command line.
Thanks. Note that I did find a workaround, which is to set
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.
dnl check if the curses header we found, works
dnl save CFLAGS and LDFLAGS and set new ones
dnl do the compile test
AC_MSG_CHECKING([if curses is usable])
printw("Hello World !!!");
dnl restore variables
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple