public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Benjamin Kosnik <bkoz@redhat.com>
To: Benjamin Scherrey <scherrey@switchco.com>
Cc: gcc@gcc.gnu.org, libstdc++@sources.redhat.com
Subject: Re: Latest snapshot won't build with --enable-libstdcxx-v3
Date: Wed, 20 Sep 2000 10:18:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.10009201014250.17925-100000@decepticon.cygnus.com> (raw)
In-Reply-To: <39C8E09E.9075A490@switchco.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.

This is what I got working last night: 

gcc/ChangeLog
2000-09-19  Jim Wilson  <wilson@cygnus.com>

        * config/ia64/crtbegin.asm (__dso_handle): Delete use of
        HAVE_GAS_HIDDEN macro.
   Working revision:	1.7833

gcc/cp/ChangeLog
2000-09-18  Mark Mitchell  <mark@codesourcery.com>

        * decl.c (start_function): Robustify.
   Working revision:	1.2005


I'm working on a system with corrected glibc headers though, so perhaps
this makes a difference (I doubt it.)


FYI: 

In any case, I find it quite useful to archive away sources to a working
gcc subdirectory. I usually update once a week, and archive the updates
the bootstrap. Then I can fall back onto older gcc versions if current CVS
is unusable.

-benjamin

  parent reply	other threads:[~2000-09-20 10:18 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
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 [this message]
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=Pine.LNX.4.10.10009201014250.17925-100000@decepticon.cygnus.com \
    --to=bkoz@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=libstdc++@sources.redhat.com \
    --cc=scherrey@switchco.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).