Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: brobecker@gnat.com
Cc: 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 20:30:00 -0000	[thread overview]
Message-ID: <200402252030.i1PKUEav041255@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20040225185946.GI1105@gnat.com> (message from Joel Brobecker on Wed, 25 Feb 2004 10:59:46 -0800)

   Date: Wed, 25 Feb 2004 10:59:46 -0800
   From: Joel Brobecker <brobecker@gnat.com>

   --7iMSBzlTiPOCCT2k
   Content-Type: text/plain; charset=us-ascii
   Content-Disposition: inline

   On Tue, Feb 24, 2004 at 09:09:42PM -0500, Daniel Jacobowitz wrote:
   > Try this instead:
   >   AC_CHECK_FUNC(wborder, [],
   > 	[AC_SEARCH_LIBS(wborder, [cur_colr], [],
   > 		[AC_MSG_WARN([...])])])

   Very clever! I didn't know that AC_CHECK_FUNC was using $LIBS to
   link its test program...

Except that AC_SEARCH_LIBS is clever enough itself.  It first tries to
find the function in the libraries already present.

AC_SEARCH_LIBS (initscr, [ncurses ...]), [], [AC_MSG_WARN...])
AC_SEARCH_LIBS (wborder, cur_clr, [], [AC_MSG_WARN...])

Should do exactly what you want.

Mark


  parent reply	other threads:[~2004-02-25 20:30 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
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 [this message]
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=200402252030.i1PKUEav041255@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --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