libgcc_s, Linux, and PT_GNU_EH_FRAME, and binutils

[Mark Mitchell]

> So, binaries compiled on type A systems have an ABI not supported on
> type B systems. Compatibility in the other direction is supported.
>
> Unfortunately, all Linux distributions shipped today are type B
> systems (with the exception of Debian 3.0). So anybody building gcc
> 3.2 on a current Linux system will get a type B ABI.
>
> All future releases of Linux will be type A systems, as they surely
> use latest binutils and glibc (unless a vendor isn't aware of the
> issues, and fails to use the latest stuff with gcc 3.2).
>
> Users of type B systems will find that binaries abort that work fine
> on other systems, with no indication of an error.
>
> Does this make the problem clear?

Yes.  It was, in fact, I who was unclear: I was looking for a
justification of your claim that this would be a problem. :-)

I understand the technical issue.  However, my thinking is that
people who care about building ABI compliant software will
generally not be doing it on current systems using home-built
compilers; they'll probably get either new systems or new compilers
from distributors.  And I would assume that the distributors will
build the new compilers correctly, even if building packages for
existing systems.

That said, I'll reiterate: if someone wants to tweak configure, fine.

Do it quickly, send me a patch, and we can obviate the debate by having
the change in.  I just can't see holding up the release for that.

I still need to know, though, whether Benjamin's problems have been
solved or not, and what we're doing about Franz's versioning suggestion.

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com