From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: Gmp now working, but number.c:147 isinf declared implicitly.
Date: Fri, 19 Jan 2007 11:37:31 +1100 [thread overview]
Message-ID: <877ivjam2c.fsf@zip.com.au> (raw)
In-Reply-To: <Pine.GSO.4.64.0701161247150.28584@brains.eng.cse.dmu.ac.uk> (Hugh Sasse's message of "Tue, 16 Jan 2007 14:58:48 +0000 (WET)")
Hugh Sasse <hgs@dmu.ac.uk> writes:
>
> ./.libs/libguile.so: undefined reference to `isinf'
>
> At which point I am now stuck. After all, configure found isinf.
You might be able to stick something in to save the conftest.c used.
Or maybe it's no more than
#include <math.h>
int main () { return (isinf(0.0) != 0); }
In any case if you want to advise what should or shouldn't be tested
or done ...
> autoreconf -if
> (with autoconf 2.61) I get a vastly different configure script
> with spurious "-n"s sprinkled throughout:
>
> bash-2.05$ gdiff -u configure{.orig,} | head -20
> --- configure.orig 2006-10-07 04:54:24.000000000 +0100
> +++ configure 2007-01-16 14:41:07.226209000 +0000
> @@ -1,6 +1,8 @@
> #! /bin/sh
> # Guess values for system-dependent variables and create Makefiles.
> -# Generated by GNU Autoconf 2.60a for guile 1.8.1.
> +# Generated by GNU Autoconf 2.61 for -n guile
> + -n 1.8.1
> +.
Ahh, thanks. "echo -n" used in configure.in is not portable :(. In
the AC_INIT you should be able to replace the m4_esyscmd with some
hard coded numbers. I'll try to do something that strips the newline
using m4.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-01-19 0:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 14:52 Gmp now working, but number.c:147 isinf declared implicitly Hugh Sasse
2007-01-12 17:37 ` Hugh Sasse
2007-01-12 22:59 ` Kevin Ryde
2007-01-15 9:46 ` Hugh Sasse
2007-01-15 11:58 ` Hugh Sasse
2007-01-15 20:31 ` Kevin Ryde
2007-01-16 10:21 ` Hugh Sasse
2007-01-16 14:58 ` Hugh Sasse
2007-01-19 0:37 ` Kevin Ryde [this message]
2007-01-19 10:02 ` Hugh Sasse
2007-01-21 23:27 ` Kevin Ryde
2007-01-22 11:53 ` Hugh Sasse
2007-01-22 21:11 ` Kevin Ryde
2007-01-23 10:27 ` Hugh Sasse
2007-01-19 15:43 ` Hugh Sasse
2007-01-21 21:08 ` Kevin Ryde
2007-01-21 23:22 ` Kevin Ryde
2007-01-22 12:08 ` Hugh Sasse
2007-01-22 21:05 ` Kevin Ryde
2007-01-23 11:01 ` Hugh Sasse
2007-01-24 21:23 ` Kevin Ryde
2007-01-25 10:27 ` Hugh Sasse
2007-01-26 22:24 ` Kevin Ryde
2007-01-18 0:43 ` Kevin Ryde
2007-01-18 9:57 ` Hugh Sasse
2007-01-18 12:21 ` Hugh Sasse
2007-01-18 10:43 ` Ludovic Courtès
2007-01-15 20:27 ` Kevin Ryde
2007-01-16 10:11 ` Hugh Sasse
2007-01-18 0:38 ` Kevin Ryde
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=877ivjam2c.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-user@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).