public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: pinfo configure problem
Date: Tue, 13 May 2014 10:58:00 -0000	[thread overview]
Message-ID: <05u3n9l6l8pgdeuidskcplb1930mmjtu05@4ax.com> (raw)

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.

Thanks,
Andrew


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

             reply	other threads:[~2014-05-13 10:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 10:58 Andrew Schulman [this message]
2014-05-13 11:25 ` Corinna Vinschen
2014-05-13 11:52   ` Andrew Schulman
2014-05-13 11:57     ` Corinna Vinschen
2014-05-13 15:35       ` pinfo configure problem - configure.ac (1/1) Andrew Schulman
2014-05-13 16:54         ` Corinna Vinschen
2014-05-13 16:16       ` pinfo configure problem - configure.ac (0/1) Andrew Schulman
2014-05-13 17:29         ` Andrew Schulman
2014-05-13 18:54         ` Eric Blake
2014-05-13 19:25           ` Andrew Schulman
2014-05-13 19:54             ` Eric Blake
2014-05-13 21:15               ` Andrew Schulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=05u3n9l6l8pgdeuidskcplb1930mmjtu05@4ax.com \
    --to=schulman.andrew@epa.gov \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).