This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libgcc_s.so.1 exception handling behaviour depending on glibc version
- From: Marcin Dalecki <martin at dalecki dot de>
- To: Mike Hearn <mike at navi dot cx>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 18 May 2005 17:26:30 +0200
- Subject: Re: libgcc_s.so.1 exception handling behaviour depending on glibc version
- References: <428B0C62.4000603@sun.com> <pan.2005.05.18.12.36.08.21252@navi.cx>
On 2005-05-18, at 14:36, Mike Hearn wrote:
On Wed, 18 May 2005 11:35:30 +0200, Stephan Bergmann wrote:
If I build main with C1, and libf.so with C2, and execute the
program so
that it uses C2's libgcc_s.so.1, it works.
Out of interest, what happens if you build main with C2 and libf
with C1?
That would seem to be a more common situation for distributors of
Linux
binaries than the other way around.
This policy of not supporting "build on newer, run on older" is a
massive
pain for developers who distribute Linux binaries even though it's
very
common: developers often use very new distributions but users often
don't.
It requires all kinds of stupid hacks to work around.
Like building on the system you are targeting?
Like cross building for the target system?