From: Jack Howarth <howarth@bromo.msbb.uc.edu>
To: gcc@gcc.gnu.org
Subject: 3.2.2 c++ compile problems
Date: Mon, 23 Dec 2002 09:53:00 -0000 [thread overview]
Message-ID: <200212231718.MAA29417@bromo.msbb.uc.edu> (raw)
Hello,
Can anyone shed some light on which abi change in the g++ 3.2.x
compiler is causing the following compile error. I am trying to build
the sparky package from...
http://www.cgl.ucsf.edu/home/sparky/
and I get the following compile time errors under gcc 3.2.2...
g++ -O2 -fPIC -fpermissive -c brukerfile.cc
In file included from /usr/include/c++/3.2.1/backward/fstream.h:31,
from brukerfile.cc:33:
/usr/include/c++/3.2.1/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substit
brukerfile.cc: In constructor `Bruker_Params::Bruker_Params(const Stringy&)':
brukerfile.cc:223: could not convert `bp' to `istream&'
brukerfile.cc:101: in passing argument 1 of `bool
read_parameter_entry(istream&, Stringy*, Stringy*)'
make[1]: *** [brukerfile.o] Error 1
make[1]: Leaving directory `/usr/local/src/sparky/c++'
make: *** [all] Error 2
I find that brukerfile.cc at line 101 has...
static bool read_parameter_entry(istream &strm, Stringy *tag, Stringy *value);
and at line 223 has the section...
Bruker_Params::Bruker_Params(const Stringy &path)
{
ifstream bp(path.cstring());
Stringy tag, value;
while (read_parameter_entry(bp, &tag, &value))
{
tags.append(new Stringy(tag));
values.append(new Stringy(value));
}
}
Thanks in advance for any hints on how to solve this.
Jack
next reply other threads:[~2002-12-23 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 9:53 Jack Howarth [this message]
2002-12-23 10:11 ` Craig Rodrigues
2002-12-23 10:50 ` Jack Howarth
2002-12-23 11:24 ` Gabriel Dos Reis
2002-12-23 11:56 ` Craig Rodrigues
2002-12-23 13:02 ` Joe Buck
2002-12-23 13:02 ` Craig Rodrigues
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=200212231718.MAA29417@bromo.msbb.uc.edu \
--to=howarth@bromo.msbb.uc.edu \
--cc=gcc@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).