From: Hugh Sasse <hgs@dmu.ac.uk>
Subject: Gmp now working, but number.c:147 isinf declared implicitly.
Date: Fri, 5 Jan 2007 14:52:11 +0000 (WET) [thread overview]
Message-ID: <Pine.GSO.4.64.0701051447500.3023@brains.eng.cse.dmu.ac.uk> (raw)
I am now getting :
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -D_REENTRANT -pthreads -g -O2 -Wall -Wmissing-prototypes -Werror -MT libguile_la-numbers.lo -MD -MP -MF .deps/libguile_la-numbers.Tpo -c numbers.c -fPIC -DPIC -o .libs/libguile_la-numbers.o
cc1: warnings being treated as errors
numbers.c: In function 'xisinf':
numbers.c:147: warning: implicit declaration of function 'isinf'
gmake[3]: *** [libguile_la-numbers.lo] Error 1
gmake[3]: Leaving directory `/export/home/Scratch/hgs/guile-1.8.1/libguile'
gmake[2]: *** [all] Error 2
$ ggrep -C 8 isinf config.log
| int
| main ()
| {
| return trunc ();
| ;
| return 0;
| }
configure:43674: result: no
configure:43694: checking for isinf
configure:43706: gcc -o conftest -g -O2 conftest.c -lgmp -lsocket -lnsl -lm -lltdl >&5
configure:43712: $? = 0
configure:43719: test -z "$ac_c_werror_flag" || test ! -s conftest.err
configure:43722: $? = 0
configure:43729: test -s conftest
configure:43732: $? = 0
configure:43734: result: yes
configure:43751: checking for isnan
$
So configure knwo what it is, but I can't see how to get at this info
to modify number.c. Maybe I need to do something different?
Thank you,
Hugh
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2007-01-05 14:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 14:52 Hugh Sasse [this message]
2007-01-12 17:37 ` Gmp now working, but number.c:147 isinf declared implicitly 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
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=Pine.GSO.4.64.0701051447500.3023@brains.eng.cse.dmu.ac.uk \
--to=hgs@dmu.ac.uk \
/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).