From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: configure doesn't check for clog and csqrt
Date: Thu, 12 Oct 2006 06:16:42 +1000 [thread overview]
Message-ID: <87bqoippzp.fsf@zip.com.au> (raw)
In-Reply-To: <87ac447fe4.fsf@laas.fr> (Ludovic Courtès's message of "Tue, 10 Oct 2006 10:18:27 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
>> Apparently, in GUILE-1.8.1 configure doesn't check for clog and csqrt().
>> This leads to problems on Freebsd 4.1, as the libc there doesn't
>> support both functions.
>
> Does it provide them in some other library, like `-lm'?
(There's a test, it assumes there presence of "complex double" means
the complex funcs exist ...)
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-10-11 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 19:40 configure doesn't check for clog and csqrt Han-Wen Nienhuys
2006-10-10 8:18 ` Ludovic Courtès
2006-10-11 20:16 ` Kevin Ryde [this message]
2006-10-12 12:34 ` Ludovic Courtès
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=87bqoippzp.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@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).