This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Lack of libstdc++ compatibility (was: Revision 176335)
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Markus Trippelsdorf <markus at trippelsdorf dot de>, gcc at gcc dot gnu dot org, Paolo Carlini <paolo dot carlini at oracle dot com>, Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Date: Thu, 18 Aug 2011 11:34:18 +0200 (CEST)
- Subject: Lack of libstdc++ compatibility (was: Revision 176335)
- References: <20110802130803.GA11627@x4.trippels.de> <20110802131341.GB2687@tyan-ft48-01.lab.bos.redhat.com>
On Tue, 2 Aug 2011, Jakub Jelinek wrote:
>> Revisions 176335 removed the traditional "#include <unistd.h>" from
>> gthr-posix.h. This breaks the build of many programs (Firefox, Chromium,
>> etc.) that implicitly rely on it.
> This isn't the first time the libstdc++ headers were cleaned up, and
> each time there are dozens of programs that need to be fixed up. Each
> time they just were fixed.
I think that is a bit too much of a cavalier approach.
For example, right now I am in the process of changing the compiler
FreeBSD uses for Fortran packages from GCC 4.5 to 4.6 and 100% of
the issues we run into are not related to Fortran but...C++.
Breaking source code compatbility with a step like GCC 3 to GCC 4
is one thing, but constantly doing so with every release is just
painful and makes as look bad. And it hinders the adoption of
newer releases.
Gerald