gcc version mismatches

[Ryan Schmidt]

On Nov 16, 2011, at 21:33, Kyle Husmann wrote:

>> But of course many of the science ports are not islands
>> -- they have dependencies on other "regular" software
>> like graphics libraries, which we don't put compiler variants in.
> 
> Right. Does this mean that any science library that depends on other
> libraries that don't have the compiler variants is in danger of
> undefined behavior? This seems like a rather critical problem,
> _especially_ for scientific programs that are trusted to provide
> reliable answers.
> 
> To check, I just ran octave with the DYLD_PRINT_LIBRARIES flag and
> confirmed that it is loading both the macports and osx version of
> libstdc++. Even though I haven't had any crashes running it (yet),
> this seems dangerous!

That sounds like a possibility. But my understand was that *usually* the mismatched stdc library versions aren't a problem, but that in some rare cases it is.