From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] (hppa/tui) Fix build failure due to missing wborder
Date: Wed, 25 Feb 2004 02:09:00 -0000 [thread overview]
Message-ID: <20040225020942.GA23098@nevyn.them.org> (raw)
In-Reply-To: <20040225011811.GG542@gnat.com>
On Tue, Feb 24, 2004 at 05:18:11PM -0800, Joel Brobecker wrote:
> > I wonder, should configure be checking that wborder can be found with
> > something like:
> >
> > AC_SEARCH_LIBS(wborder, [ncurses Hcurses cur_colr curses pdcurses], [],
> > [AC_MSG_WARN([no library containing wborder found])])
> >
> > and then just test that both ac_cv_search_initscr and
> > ac_cv_search_wborder are not "no"?
>
> That's something I thought about, but then what happens if we found
> both initscr and wborder in the same library, for instance "ncurses".
> We would probably end up linking with the same -l<...> switch twice.
> Not very elegant. Would you prefer this approach, though? I figured
> that, since Hcurses is already HPUX-specific AFAIK, we might as well
> take advantage of that knowledge and add -lcur_colr as I did. On the
> other hand, mutter something about HP eventually finding their way to
> the bright side of the force and putting wborder back inside Hcurses...
>
> I prefer your suggestion too, shall I go ahead? Any objection?
Try this instead:
AC_CHECK_FUNC(wborder, [],
[AC_SEARCH_LIBS(wborder, [cur_colr], [],
[AC_MSG_WARN([...])])])
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-25 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 22:03 Joel Brobecker
2004-02-24 23:34 ` Andrew Cagney
2004-02-25 1:18 ` Joel Brobecker
2004-02-25 2:09 ` Daniel Jacobowitz [this message]
2004-02-25 18:59 ` Joel Brobecker
2004-02-25 19:55 ` Andrew Cagney
2004-02-25 20:11 ` Joel Brobecker
2004-02-25 20:30 ` Mark Kettenis
2004-02-26 0:43 ` Joel Brobecker
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=20040225020942.GA23098@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.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