From: Eric Christopher <echristo@redhat.com>
To: sashan <sashang@ihug.co.nz>
Cc: gcc@gcc.gnu.org
Subject: Re: [Newb] Building 3.4
Date: Sat, 20 Mar 2004 00:51:00 -0000 [thread overview]
Message-ID: <1079735890.3396.3.camel@dzur.sfbay.redhat.com> (raw)
In-Reply-To: <405B6FA9.2040700@ihug.co.nz>
On Fri, 2004-03-19 at 14:09, sashan wrote:
> I built gcc-3.4 about a week ago. Then I did a cvs update and tried to
> rebuild again but it spat out this error.
>
> In file included from /home/darkwing/Code/gcc_3.4_build/i686-pc-linux-gnu/libstdc++-v3/include/memory:55,
> from ../../../../gcc_3.4/libstdc++-v3/src/allocator.cc:35:
> /home/darkwing/Code/gcc_3.4_build/i686-pc-linux-gnu/libstdc++-v3/include/bits/allocator.h:52:31: bits/c++allocator.h: No such file or directory
> In file included from /home/darkwing/Code/gcc_3.4_build/i686-pc-linux-gnu/libstdc++-v3/include/memory:55,
>
> What am I doing wrong?
Use gcc/contrib/gcc_update to update your tree instead.
-eric
--
Eric Christopher <echristo@redhat.com>
prev parent reply other threads:[~2004-03-19 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 22:57 sashan
2004-03-20 0:51 ` Eric Christopher [this message]
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=1079735890.3396.3.camel@dzur.sfbay.redhat.com \
--to=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=sashang@ihug.co.nz \
/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).