From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] (hppa/tui) Fix build failure due to missing wborder
Date: Tue, 24 Feb 2004 23:34:00 -0000 [thread overview]
Message-ID: <403BDFA0.5000504@gnu.org> (raw)
In-Reply-To: <20040223220334.GH1273@gnat.com>
> Hello,
>
> Re: http://sources.redhat.com/ml/gdb-patches/2004-02/msg00654.html
>
> On HP/UX, the GDB build fails during the link due to a missing wborder.
> I found the symbol in libcur_colr.sl. To fix the build, I suggest the
> following change, although I could conceive that this is not the best
> way of handling this. Comments and suggestions warmly welcome.
[ditto ...]
> 2004-02-23 J. Brobecker <brobecker@gnat.com>
>
> * configure.in (LIBS): Add -lcur_colr when TUI is enabled and
> when using the HP curses library.
> * configure: Regenerate.
>
> Tested on HP/UX 11.00, and x86-linux.
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"?
Andrew
next prev parent reply other threads:[~2004-02-24 23:34 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 [this message]
2004-02-25 1:18 ` Joel Brobecker
2004-02-25 2:09 ` Daniel Jacobowitz
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=403BDFA0.5000504@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--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