This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: __register_frame_info & shared library compatibility


Jeffrey A Law wrote:
>   > Or they can use the latest glibc 2.0 via CVS. I am willing to set up a
>   > ftp site with tar files.
> What am I not being clear about?
> 
> This kind of binary breakage is not acceptable.  It doesn't matter if you
> put a new glibc somewhere.  Breaking binaries like that patch did is not
> acceptable.

The patch does *not break binaries*.

Installing EGCS and using it to compile new applications does
*not break binaries*.

But recompiling some shared libraries using EGCS with the patch breaks some
binaries.  Is it unreasonable to request a user upgrades to the latest
Glibc 2.0, or any Glibc 2.1 before doing this?

-- Jamie


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]