From: northern snowfall <dbailey27@ameritech.net>
To: Russ Cox <rsc@plan9.bell-labs.com>
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] plan 9 software for unix
Date: Wed, 12 Feb 2003 15:46:44 -0500 [thread overview]
Message-ID: <3E4AB2B4.4030002@ameritech.net> (raw)
In-Reply-To: <d1073f7492521fd20e9276602429ba3f@plan9.bell-labs.com>
libbio compiles a.o.k. on SunOS-sun4u with the Linux makefile (using
GCC. I dont have a spro licence).
libregexp9-10 compiles fine.
With libfmt I get a warning:
gcc -Wall -Wno-missing-braces -Wno-parentheses -Wno-switch -O2 -g -c
fltfmt.c
fltfmt.c: In function `xdodtoa':
fltfmt.c:180: warning: implicit declaration of function `isinf'
which manifests later when linking:
blueberry.north_ % make test
gcc -o test test.c libfmt.a
Undefined first referenced
symbol in file
isinf libfmt.a(fltfmt.o)
ld: fatal: Symbol referencing errors. No output written to test
collect2: ld returned 1 exit status
make: *** [test] Error 1
blueberry.north_ %
Apparently Solaris 2.9 doesn't have isinf in its libc. It does, however,
have
isnan() and finite(). finite() returns TRUE(1) if the argument is
neither infinity nor
NaN. isnan() returns TRUE if the argument is NaN. Therefore,
if(finite(x) == FALSE && isnan(x) == FALSE) {
// infinite found
}
I guess you could ifdef a macro in based on underlying architecture in
the source and
-Dx in the Makefile, but, it seems very non-plan9 to be so crude for
just one function.
Then again, creating an external dependency file seems crude for one
function as well...
Don
next prev parent reply other threads:[~2003-02-12 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 20:13 Russ Cox
2003-02-12 20:46 ` northern snowfall [this message]
2003-02-12 22:58 ` Dan Cross
2003-02-13 2:33 ` Russ Cox
2003-02-13 0:26 ` Glenn McGuire
2003-02-13 12:28 ` Eric Grosse
2003-02-13 17:47 ` Jeff Sickel
2003-02-13 17:57 ` Russ Cox
2003-02-13 18:37 ` Russ Cox
2003-02-13 13:19 Eric Grosse
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=3E4AB2B4.4030002@ameritech.net \
--to=dbailey27@ameritech.net \
--cc=9fans@cse.psu.edu \
--cc=rsc@plan9.bell-labs.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;
as well as URLs for NNTP newsgroup(s).