From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ape include files
Date: Thu, 13 Sep 2001 09:13:45 -0400 [thread overview]
Message-ID: <20010913131347.AEC56199FA@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 81 bytes --]
Delete the FLT_* definitions from limits.h. They don't belong there.
-rob
[-- Attachment #2: Type: message/rfc822, Size: 2069 bytes --]
From: pac <cej@cejchan.gli.cas.cz>
To: 9fans@cse.psu.edu
Cc: cej@cejchan.gli.cas.cz
Subject: [9fans] ape include files
Date: Thu, 13 Sep 2001 15:12:22 +0200
Message-ID: <cej-1010913151221.A01296@cejchan.gli.cas.cz>
Hi all,
while compiling under APE, I met the following conflict several times, when both
#include <float.h>
#include <limits.h>
were present.
cpp: /386/include/ape/float.h:11 Macro redefinition of FLT_MAX
cpp: /386/include/ape/float.h:14 Macro redefinition of FLT_MIN
cpp: /386/include/ape/float.h:21 Macro redefinition of DBL_MAX
cpp: /386/include/ape/float.h:24 Macro redefinition of DBL_MIN
Obviously, I found e.g.:
/root/sys/include/ape/sys/limits.h:#define FLT_MAX 3.40282347E+38
/root/386/include/ape/float.h:#define FLT_MAX 3.40282347e+38
etc....
Is this an intention, or a bug? If intention, I would be glad for a workaround.
Best regards,
Peter.
--
Peter A Cejchan
biologist
Acad. Sci., Prague, CZ
<cej at cejchan dot gli dot cas dot cz>
next reply other threads:[~2001-09-13 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 13:13 rob pike [this message]
2001-09-13 13:53 ` Boyd Roberts
2001-09-18 9:26 ` pac
-- strict thread matches above, loose matches on Subject: below --
2001-09-13 13:12 pac
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=20010913131347.AEC56199FA@mail.cse.psu.edu \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).