public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>
To: Oyvind Yrke <oyvind@stavanger.geoquest.slb.com>
Cc: egcs@cygnus.com
Subject: Re: egcs 1.0.2
Date: Fri, 03 Apr 1998 21:52:00 -0000	[thread overview]
Message-ID: <vyzogyjl1rj.fsf@issan.informatik.uni-dortmund.de> (raw)
In-Reply-To: <351FD0C9.21BD7E3E@stavanger.geoquest.slb.com>

Oyvind Yrke <oyvind@stavanger.geoquest.slb.com> writes:

|>      * rtti - is there any reason why typeinfo.h is not shipped with egcs?
|>        I noticed that typeinfo.h was part of libg++2.7.2, but not in 2.8.x!!

Use <typeinfo>, not <typeinfo.h>.

-- 
Andreas Schwab                                      "And now for something
schwab@issan.informatik.uni-dortmund.de              completely different"
schwab@gnu.org

  parent reply	other threads:[~1998-04-03 21:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-30 16:18 Oyvind Yrke
1998-04-01 13:41 ` Jeffrey A Law
1998-04-01 19:44 ` Jim Wilson
1998-04-03 21:52   ` Joe Buck
1998-04-03 21:52 ` Andreas Schwab [this message]
     [not found] <3525297C.4A20D761@stavanger.geoquest.slb.com>
1998-04-03 21:52 ` Jim Wilson
  -- strict thread matches above, loose matches on Subject: below --
1998-03-19 20:46 Felix Morley Finch
1998-02-16 13:34 Daniel Egger
1998-02-16 14:21 ` H.J. Lu
1998-02-15  8:24 egcs cvs'd between 980214 8:00 and 9:13 UTC on m68k-next-nextstep3: Success Jeffrey A Law
1998-02-15  8:32 ` egcs 1.0.2 H.J. Lu
1998-02-15  8:33   ` Jeffrey A Law
1998-02-15  8:42     ` H.J. Lu
1998-02-15  8:46       ` Jeffrey A Law
1998-02-15  8:50         ` H.J. Lu
1998-02-15 12:18   ` Joe Buck
1998-02-15 14:04     ` H.J. Lu
1998-02-16  4:49       ` Bernd Schmidt
1998-02-16 10:34         ` H.J. Lu
1998-02-16 18:19           ` Bruno Haible

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=vyzogyjl1rj.fsf@issan.informatik.uni-dortmund.de \
    --to=schwab@issan.informatik.uni-dortmund.de \
    --cc=egcs@cygnus.com \
    --cc=oyvind@stavanger.geoquest.slb.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).