From: "Kenneth H. Cox" <kenstir@senteinc.com>
To: gcc-help@gcc.gnu.org
Subject: problems building 2.95.2 on sparc-sun-solaris2.5.1
Date: Tue, 21 Dec 1999 12:14:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.20.9912211509280.16675-100000@cherry.senteinc.com> (raw)
Hello,
'make bootstrap' fails for me with a "redefinition of struct exception"
error. I don't know how to workaround this, as the header in question is
a system header which is conflicting with a GCC header. Any help would be
much appreciated!
% uname -a
SunOS cherry.senteinc.com 5.5.1 Generic sun4u sparc SUNW,Ultra-1
% env CC=cc ./configure --prefix=/system/pkg/gcc/$VERS \
--exec-prefix=/system/pkg/gcc/$VERS/$PLATFORM --enable-languages=c++
% make bootstrap
...
/system/disks/scrap/tmp/kenstir-tmp/gcc-2.95.2/gcc/xgcc -B/system/disks/scrap/tmp/kenstir-tmp/gcc-2.95.2/gcc/ -B/system/pkg/gcc/2.95.2/sparc-sun-solaris2.5.1/sparc-sun-solaris2.5.1/bin/ -c -g -O2 -fno-implicit-templates -I. -I./stl -I../libio -I./../libio -nostdinc++ valarray.cc
In file included from /system/disks/scrap/tmp/kenstir-tmp/gcc-2.95.2/gcc/include/new:9,
from /system/disks/scrap/tmp/kenstir-tmp/gcc-2.95.2/gcc/include/new.h:6,
from stl/stl_algobase.h:52,
from stl/algorithm:30,
from std/std_valarray.h:41,
from valarray.cc:1:
/system/disks/scrap/tmp/kenstir-tmp/gcc-2.95.2/gcc/include/exception:13: redefinition of `struct exception'
/usr/include/math.h:81: previous definition here
--
Kenneth H. Cox
Software Guy
Sente, Inc.
WARNING: multiple messages have this Message-ID
From: "Kenneth H. Cox" <kenstir@senteinc.com>
To: gcc-help@gcc.gnu.org
Subject: problems building 2.95.2 on sparc-sun-solaris2.5.1
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.20.9912211509280.16675-100000@cherry.senteinc.com> (raw)
Message-ID: <19991231222400.iaXVZx9lxlFi0wWeFFtZwwP3CF5aDlLem4yv2_om8hU@z> (raw)
Hello,
'make bootstrap' fails for me with a "redefinition of struct exception"
error. I don't know how to workaround this, as the header in question is
a system header which is conflicting with a GCC header. Any help would be
much appreciated!
% uname -a
SunOS cherry.senteinc.com 5.5.1 Generic sun4u sparc SUNW,Ultra-1
% env CC=cc ./configure --prefix=/system/pkg/gcc/$VERS \
--exec-prefix=/system/pkg/gcc/$VERS/$PLATFORM --enable-languages=c++
% make bootstrap
...
/system/disks/scrap/tmp/kenstir-tmp/gcc-2.95.2/gcc/xgcc -B/system/disks/scrap/tmp/kenstir-tmp/gcc-2.95.2/gcc/ -B/system/pkg/gcc/2.95.2/sparc-sun-solaris2.5.1/sparc-sun-solaris2.5.1/bin/ -c -g -O2 -fno-implicit-templates -I. -I./stl -I../libio -I./../libio -nostdinc++ valarray.cc
In file included from /system/disks/scrap/tmp/kenstir-tmp/gcc-2.95.2/gcc/include/new:9,
from /system/disks/scrap/tmp/kenstir-tmp/gcc-2.95.2/gcc/include/new.h:6,
from stl/stl_algobase.h:52,
from stl/algorithm:30,
from std/std_valarray.h:41,
from valarray.cc:1:
/system/disks/scrap/tmp/kenstir-tmp/gcc-2.95.2/gcc/include/exception:13: redefinition of `struct exception'
/usr/include/math.h:81: previous definition here
--
Kenneth H. Cox
Software Guy
Sente, Inc.
next reply other threads:[~1999-12-21 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-21 12:14 Kenneth H. Cox [this message]
1999-12-21 12:46 ` Jeffrey A Law
1999-12-31 22:24 ` Jeffrey A Law
1999-12-31 22:24 ` Kenneth H. Cox
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=Pine.GSO.4.20.9912211509280.16675-100000@cherry.senteinc.com \
--to=kenstir@senteinc.com \
--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).