From: Jeffrey A Law <law@cygnus.com>
To: rittle@comm.mot.com
Cc: egcs@cygnus.com
Subject: Re: Implications of tighter integration of libg++
Date: Mon, 09 Feb 1998 02:22:00 -0000 [thread overview]
Message-ID: <5837.887019874@hurl.cygnus.com> (raw)
In-Reply-To: <199711250040.SAA09460@supra.rsch.comm.mot.com>
In message <199711250040.SAA09460@supra.rsch.comm.mot.com>you write:
> Under EGCS, there is now tighter integration between g++ and the
> required standard C++ libraries, in that they are now distributed and
> configured together.
>
> Should we assume that this tighter integration will continue? Or is
> this just a short-term situation to aid current development?
We expect the tighter integration to continue indefinitely.
[ ... ]
> It is desirable to place libraries compiled against and dependent upon
> a given version of g++, and their related header files, into the
> compiler's lib and include directory. Thus, I actually believe that
> something akin to the above should be the default. Someone else
> believed this at one time given the comments in gcc/Makefile.in:
With the stabilizaton of the C++ language and its associated runtime libraries
I wonder if this will be all that useful.
I kinda get the feeling that we'll start seeing releases that are compatable
at both the header file level and at the link level in the near future.
Just my opinions -- the g++ folks might have different ideas about this
whole area.
jeff
next prev parent reply other threads:[~1998-02-09 2:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-24 23:19 Loren J. Rittle
1997-11-25 6:52 ` Manfred.Hollstein
1998-02-09 2:22 ` Jeffrey A Law [this message]
1998-02-09 7:13 ` Martin von Loewis
1998-02-09 14:46 ` Joe Buck
1998-02-09 15:33 ` Martin von Loewis
1998-02-09 21:34 ` H.J. Lu
1998-02-09 21:34 ` Joe Buck
1998-02-10 0:53 ` John A. Tamplin
1998-02-10 10:30 ` Joe Buck
1998-02-09 11:54 ` Joe Buck
1998-02-09 14:46 ` H.J. Lu
[not found] ` <5837.887019874.cygnus.egcs@hurl.cygnus.com>
1998-02-09 11:31 ` Jason Merrill
1998-02-09 11:54 ` Jeffrey A Law
1998-02-09 11:54 ` Jason Merrill
1998-02-09 15:33 ` Fred Fish
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=5837.887019874@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=rittle@comm.mot.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).