[Bug libstdc++/27878] GCC 4.1.1 build fails on mips-sgi-irix6.5 (libstdc++)/GCC 4.1.0 worked.

["ro at techfak dot uni-bielefeld dot de" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #30 from ro at techfak dot uni-bielefeld dot de  2006-07-12 16:11 -------
Subject: Re:  GCC 4.1.1 build fails on mips-sgi-irix6.5 (libstdc++)/GCC 4.1.0
worked.

multix at gmail dot com writes:

> I'm available for testing on my box. I Think I have access to a 6.5.4 box
> too... but am not sure.

That would be fine, in case I get around to investigating this further.
On many other platforms (like Tru64 UNIX), it used to be possible to fix or
work around problems like this, provided the number of different
cases/releases don't get out of hand.

Before I start this, I'll probably have to invest some work to get mainline
to fully bootstrap on 6.5.2x, though.

> SGI says that binaries compiled on different minor releases should be
> compatible each other, I wonder if a binary packager can safely build on >=
> 6.5.18 and expect it to work on older boxes too or not...

Certainly not: this only works the other way round: you can build on 6.5.x
and run on 6.5.y, y > x.  There are new symbols introduced e.g. in libc,
which are marked as OPTIONAL in nm output.  It is possible (though I don't
remember how this is done) to check for those functions as runtime and use
them only if available.  This is certainly far too much trouble in the GCC
case, though.

        Rainer


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27878