From: Jeffrey A Law <law@cygnus.com>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: egcs@cygnus.com
Subject: Re: Build of egcs-971031 on m68k-next-nextstep3 fails in libstc++
Date: Sun, 02 Nov 1997 21:29:00 -0000 [thread overview]
Message-ID: <16131.878533381@hurl.cygnus.com> (raw)
In-Reply-To: <9711012250.AA08033@moene.indiv.nluug.nl>
In message < 9711012250.AA08033@moene.indiv.nluug.nl >you write:
> In file included from complex:7,
> from std/complext.cc:28,
> from ./cinst.cc:29:
> std/complext.h:314: declaration of C function `double hypot(double,
> double)' conflicts with
> /NextDeveloper/Headers/ansi/math.h:26: previous declaration `const
> double hypot(double, double)' here
Sigh. This is a bug in the nextstep headers.
They're using the old (and incorrect) method for trying to describe
a "pure" function by prefixing the function's return type with a
"const".
This is wrong because the "const" really applies to the return type,
not the function itself.
The right way to describe a "pure" function is to use an attribute,
but that only works with newer versions of gcc.
Anyway, enough background...
This is something we usually address with fixincludes; I'll see
what I can do if you send me a copy of /NextDeveloper/Headers/ansi/math.h
jeff
prev parent reply other threads:[~1997-11-02 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-01 15:16 Toon Moene
1997-11-02 21:29 ` Jeffrey A Law [this message]
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=16131.878533381@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=toon@moene.indiv.nluug.nl \
/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).