From: Mumit Khan <khan@xraylith.wisc.edu>
To: Lee Iverson <leei@ai.sri.com>
Cc: egcs@cygnus.com
Subject: Re: libg++
Date: Tue, 02 Dec 1997 13:14:00 -0000 [thread overview]
Message-ID: <199712022103.PAA02417@eh_pc11.xraylith.wisc.edu> (raw)
In-Reply-To: <199712021549.HAA29620@Canada.AI.SRI.COM>
Lee Iverson <leei@ai.sri.com> writes:
>
> Is anyone working on reconstructing libg++ so that it will work with
> egcs? I realize that it is somewhat officially considered *obsolete*
> but we have a bunch of legacy code that, until we get it converted,
> depends critically on libg++.
>
I use a slightly modified version of libg++-2.8.0b6. The only mods are:
- patch from HJ Lu to fix a bug (shows up only with glibc2? Can't
remember exactly)
- replace gxx_includedir with gxx_include_dir to conform to the new
egcs configure (as of egcs-971127 I believe).
Regards,
Mumit -- khan@xraylith.wisc.edu
http://www.xraylith.wisc.edu/~khan/
next prev parent reply other threads:[~1997-12-02 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-02 9:23 libg++ Lee Iverson
1997-12-02 13:14 ` Mumit Khan [this message]
1997-12-02 18:18 ` libg++ H.J. Lu
[not found] <Pine.SUN.3.95-heb-2.07.980629191358.564A-100000.cygnus.egcs@beitza.jct.ac.il>
1998-06-30 19:49 ` libg++ Nathan Myers
1998-07-01 7:26 ` libg++ H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
1998-06-29 23:55 libg++ Daniel Bernstein
1998-06-30 11:53 ` libg++ H.J. Lu
1998-06-30 14:08 ` libg++ Manfred Hollstein
1998-01-20 14:54 libg++ Oleg Krivosheev
1998-01-23 11:15 ` libg++ H.J. Lu
1997-08-30 22:12 egcs-970828 install Weiwen Liu
1997-08-30 22:12 ` libg++? Joe Buck
1997-08-30 12:00 Incorrect i960 linker config Stephen Williams
1997-08-30 21:24 ` libg++? Jason Merrill
1997-08-30 11:27 libg++? Chip Salzenberg
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=199712022103.PAA02417@eh_pc11.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=egcs@cygnus.com \
--cc=leei@ai.sri.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).