public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: "Dan Keating" <dan.keating@preston.net>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: Gcc3.2 build error on Solaris 10
Date: Wed, 05 Jul 2006 16:34:00 -0000	[thread overview]
Message-ID: <m37j2sau43.fsf@dhcp-172-18-108-216.corp.google.com> (raw)
In-Reply-To: <000f01c69fe0$18e72510$310a0eca@1PYBH1S>

"Dan Keating" <dan.keating@preston.net> writes:

> I'm having problems building gcc3.2 on a solaris 10 system. Gcc2.95.3 builds
> fine, but 3.2 and 3.2.3 both fall down with the following error:
> 
> /temp/bsm/gcc-sun10/gcc/xgcc -B/temp/bsm/gcc-sun10/gcc/
> -B/lang/gcc/3.2/sparc-sun-solaris2.10/bin/
> -B/lang/gcc/3.2/sparc-sun-solaris2.10/lib/ -isystem
> /lang/gcc/3.2/sparc-sun-solaris2.10/include -DHAVE_CONFIG_H -I.
> -I../../../../gcc-3.2/libstdc++-v3/libmath -I.. -g -O2 -c
> ../../../../gcc-3.2/libstdc++-v3/libmath/signbit.c -o signbit.o
> In file included from ../../../../gcc-3.2/libstdc++-v3/libmath/signbit.c:32:
> ../../../../gcc-3.2/libstdc++-v3/libmath/mathconf.h:84: conflicting types
> for `nan'
> /usr/include/iso/math_c99.h:145: previous declaration of `nan'
> 
> Configure is being run with parameters "--enable-languages=c++
> --disable-shared".
> 
> Hopefully there's someone who can see a cause for this.

Look at the two files in question:

gcc-3.2/libstdc++-v3/libmath/mathconf.h, line 84
/usr/include/iso/math_c99.h, line 145

Most likely you will see conflicting types for nan.

Since gcc 3.2 is four years old and completely unsupported, your best
bet for fixing this would be to edit mathconf.h to match your system
header file.

Ian

  reply	other threads:[~2006-07-05 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05  3:07 Dan Keating
2006-07-05 16:34 ` Ian Lance Taylor [this message]
2006-07-06 23:53   ` Dan Keating
2006-07-19 17:40 ` Kai Ruottu
2006-07-07  1:44 Bill McEnaney
2006-07-07  1:56 ` Dan Keating
2006-07-07  2:19 Bill McEnaney

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=m37j2sau43.fsf@dhcp-172-18-108-216.corp.google.com \
    --to=iant@google.com \
    --cc=dan.keating@preston.net \
    --cc=gcc-help@gcc.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).