This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Lack of libstdc++ compatibility
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, Markus Trippelsdorf <markus at trippelsdorf dot de>, gcc at gcc dot gnu dot org, Paolo Carlini <paolo dot carlini at oracle dot com>
- Date: Thu, 10 Nov 2011 23:29:36 +0100 (CET)
- Subject: Re: Lack of libstdc++ compatibility
- References: <20110802130803.GA11627@x4.trippels.de> <20110802131341.GB2687@tyan-ft48-01.lab.bos.redhat.com> <alpine.LNX.2.00.1108181129100.2761@gerinyyl.fvgr> <CAH6eHdR-c9bdB5efGEfZRf68E0BZzfP6qUB1oxihrXw5AsOZBQ@mail.gmail.com>
On Thu, 18 Aug 2011, Jonathan Wakely wrote:
> Personally I *like* it when a new release identifies portability
> problems such as missing includes. I consider it an advantage,
> and an improvement in the compiler.
That's a valid approach from a technology perspective. From a
customer/user perspective it's just painful.
These incompatibilities have been costing me days, if not weeks, when
upgrading the versions of GCC in the FreeBSD Ports Collection, for example
-- for no benefit to anyone since it all was about older version of
ports or old pieces of software, abandoned upstream.
(And it's mostly on the C++ front; C and Fortran appear a lot more
stable.)
Gerald