From: "Frank Ch. Eigler" <fche@redhat.com>
To: Marc <marcm@easystreet.com>
Cc: sid@sources.redhat.com
Subject: Re: Build error while compiling SID
Date: Sat, 30 Dec 2000 05:26:00 -0000 [thread overview]
Message-ID: <20001230082633.A21204@redhat.com> (raw)
In-Reply-To: <20001230012937.B6673@mentorg.com>
Hi -
On Sat, Dec 30, 2000 at 01:26:01AM -0800, Marc wrote:
: [...]
: I'm trying to build SID and I'm running into the following error (many times
: for different files):
:
: c++ -DHAVE_CONFIG_H -I. -I. -I.. -I. -I../../include -I./../../include -g -O2 -c -fPIC -DPIC gprof.cxx -o .libs/gprof.lo
: ../../include/sidcomp.h: In method `::sidutil::basic_big_endian_cpu::~basic_big_endian_cpu()':
: ../../include/sidcomp.h:164: `::sid::component::~component()' is protected
: In file included from gprof.cxx:20:
: ../../include/sidcpuutil.h:498: within this context
: [...]
: Output from running "c++ -v":
: #409 [marcm@lunatic] /tmp/SID/src/sid > c++ -v
: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
: gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
:
: This is on a RH6.2 system. The sources are up-to-date as of late 12-29. Any
: thoughts what might be wrong?
We last tried egcs-1.1.2 very long ago. I believe this is just a small
compiler bug, but I'm pretty sure there were others. SID is pretty hard
on g++. Please consider upgrading to gcc-2.95.2 or Red Hat Linux 7's
gcc-2.96.
Putting a "public:" specifier before the sidcpuutil.h destructor
decls may allay this specific message with your compiler, in case
you still want to try to use it. You may need to turn optimization
down or off to get correct code.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6TeKJVZbdDOm/ZT0RAu/0AJ9Yz9DRgqhjNsRcU4u2+94SfJBbggCdHC28
Bzct8pn0H00XlIop55dGUh0=
=drG/
-----END PGP SIGNATURE-----
parent reply other threads:[~2000-12-30 5:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20001230012937.B6673@mentorg.com>]
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=20001230082633.A21204@redhat.com \
--to=fche@redhat.com \
--cc=marcm@easystreet.com \
--cc=sid@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).