From: Ian Lance Taylor <iant@google.com>
To: Chris Angelico <rosuav@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Difficulty compiling with g++ after system change
Date: Tue, 02 Feb 2010 16:01:00 -0000 [thread overview]
Message-ID: <mcriqaf4ol1.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <268c26c51002012137m6cffda9k6c068a37c01dfb2d@mail.gmail.com> (Chris Angelico's message of "Tue\, 2 Feb 2010 16\:37\:54 +1100")
Chris Angelico <rosuav@gmail.com> writes:
> The working system is:
> $ g++ --version
> g++ (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4)
>
> The nonworking:
> g++ (Ubuntu 4.4.104ubuntu9) 4.4.1
> lcmini.cpp:10:21: error: fstream.h: No such file or directory
My apologies. I looked in the wrong place. gcc 4.2.4 does provide
<backward/fstream.h>. However, that deprecated file was removed for
the gcc 4.3 release.
Ian
next prev parent reply other threads:[~2010-02-02 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 7:11 Chris Angelico
2010-02-02 15:58 ` Ian Lance Taylor
2010-02-02 16:01 ` Ian Lance Taylor [this message]
2010-02-02 20:41 ` Chris Angelico
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=mcriqaf4ol1.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rosuav@gmail.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).