From: "Hrvoje Nikšić" <hrvoje.niksic@avl.com>
Cc: guile-devel@gnu.org
Subject: Re: Building Guile on IA64 HPUX
Date: Thu, 26 Oct 2006 09:13:31 +0200 [thread overview]
Message-ID: <1161846811.23420.31.camel@localhost> (raw)
In-Reply-To: <873b9crpj1.fsf@ossau.uklinux.net>
On Thu, 2006-10-26 at 00:36 +0200, Neil Jerram wrote:
> > +AC_CHECK_LIB(uca, __uc_get_ar_bsp)
>
> Is there any point in this check? As far as I can tell we don't use
> the result of the check anywhere.
We use it for the check's side effect: if libuca exists, it is added to
the LIBS. Without -luca, Guile using __uc_get_ar_bsp would not link on
HPUX. There are other checks that use the same logic, such as check for
connect in -lsocket and for gethostbyname in -lnsl.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-10-26 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 15:31 Building Guile on IA64 HPUX Hrvoje Nikšić
2006-10-25 22:36 ` Neil Jerram
2006-10-26 7:13 ` Hrvoje Nikšić [this message]
2006-10-27 0:06 ` Neil Jerram
2006-10-27 7:16 ` Hrvoje Nikšić
[not found] <200611012157.NAA20914@hpsje.cup.hp.com>
2006-11-02 8:29 ` Hrvoje Nikšić
2006-11-02 21:15 ` Neil Jerram
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1161846811.23420.31.camel@localhost \
--to=hrvoje.niksic@avl.com \
--cc=guile-devel@gnu.org \
/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).