From: Benjamin Scherrey <scherrey@switchco.com>
To: Benjamin Kosnik <bkoz@redhat.com>
Cc: Theodore Papadopoulo <Theodore.Papadopoulo@sophia.inria.fr>,
gcc@gcc.gnu.org, libstdc++@sources.redhat.com
Subject: Re: Latest snapshot won't build with --enable-libstdcxx-v3
Date: Wed, 20 Sep 2000 09:14:00 -0000 [thread overview]
Message-ID: <39C8E09E.9075A490@switchco.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10009192236260.17466-100000@decepticon.cygnus.com>
FYI - Latest CVS source still dies in libstdc++-v3/src/local.cc . I'm stuck until I
can get 2.96 going with libstdc++v3. Has anyone been successful doing this? I was
under the impression that this had/has been working.
thanx & later,
Ben Scherrey
Benjamin Kosnik wrote:
> > > I'm having really bad luck getting the last two snapshots to build
> > > (I've not tried the others). Specifically, I'm trying to prepare for
> > > the gcc 3 with the new libstdc++ so my code will be ready for the
> > > release. Unfortunately, I can't complete the 'make bootstrap' with the
> > > new snapshot, 20000918. It looks like it dies trying to build
> > > libstdc++.
>
> FYI, snapshots that I've tried that have worked:
>
> 2000-09-19
> 2000-09-10 (last bootstrap)
> 2000-08-27 (last debuggable)
> <snip>
>
> > ../../../../../Cvs/gcc/libstdc++-v3/src/locale.cc:926: Internal error: Segmentat
> > ion fault.
> > Please submit a full bug report.
> > See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
>
> ....quite obviously a compiler bug. It's fixed now
>
> -benjamin
next prev parent reply other threads:[~2000-09-20 9:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-19 11:44 Benjamin Scherrey
2000-09-19 15:08 ` Theodore Papadopoulo
2000-09-19 23:11 ` Benjamin Kosnik
2000-09-20 1:39 ` Theodore Papadopoulo
2000-09-20 8:32 ` Joe Buck
2000-09-20 8:42 ` Theodore Papadopoulo
2000-09-20 9:48 ` Phil Edwards
2000-09-21 17:44 ` Marc Espie
2000-09-21 17:40 ` Marc Espie
[not found] ` <mailpost.969583213.13372@postal.sibyte.com>
2000-09-21 17:59 ` Chris G. Demetriou
2000-09-21 23:32 ` Magnus Fromreide
2000-09-22 4:51 ` Gabriel Dos Reis
2000-09-25 15:12 ` Joern Rennecke
2000-09-20 5:29 ` Benjamin Scherrey
2000-09-20 9:14 ` Benjamin Scherrey [this message]
2000-09-20 9:33 ` Steven King
2000-09-20 12:29 ` Benjamin Scherrey
2000-09-20 12:52 ` Benjamin Kosnik
2000-09-20 13:16 ` Benjamin Scherrey
2000-09-21 11:59 ` Benjamin Scherrey
2000-09-20 10:18 ` Benjamin Kosnik
2000-09-21 20:54 Brad Lucier
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=39C8E09E.9075A490@switchco.com \
--to=scherrey@switchco.com \
--cc=Theodore.Papadopoulo@sophia.inria.fr \
--cc=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@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).