[bug #2180] (grass) Re: [GRASS5] C and C++ compiler changes?

Markus Neteler neteler at itc.it
Thu Oct 23 05:21:15 EDT 2003

On Wed, Oct 22, 2003 at 03:59:14PM +0200, Request Tracker wrote:
> this bug's URL: http://intevation.de/rt/webrt?serial_num=2180
> -------------------------------------------------------------------------
> On Wed, Oct 22, 2003 at 10:36:00AM +0200, Bernhard Reiter wrote:
> > On Tue, Oct 21, 2003 at 08:05:32PM +0200, Thierry Laronde wrote:
> > > 
> > > Great. All I wanted to emphasize ---since I have spent some times trying
> > > to convince GNU libc (latest) and GNU cc (latest) to compile smoothly
> > > together...--- is that we are going to have some hard time with mixes
> > > of different versions of gcc and glibc... And the C++ support has deeply
> > > changed too!
> > 
> > Well it is _only_ about the C++ support as far as I always understood this.
> > Mixing most of the plain C libraries have never been a major problem.
> > Am I missing something?
> No, in the sense that the "user apparent" changes are with the C++ part.
> But unfortunately, GCC 3.3.1 for example has some bugs in optimization
> and inlining meaning that we will have some rough times with compilation
> failures reports that may be caused by bugs in the compiler and not in
> the code (for example some version(s) of glibc doesn't compile with it
> and one can compile a Linux kernel with it that will cause bugs (in my
> case this was reboot) : but compilation succeeds...; so imagine the 
> hell if a glibc compiles but is buggy!).

Naive question:
Should/can add we a test in the (G)makefile and disable certain gcc versions
to avoid too many "bug" reports?

More information about the grass-dev mailing list