This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [COMMITTED PATCH] Fix missing __sqrtl_finite symbol in libm on sparc 32-bit.


On Mon, 25 Jan 2016, Florian Weimer wrote:

> * Joseph Myers:
> 
> > On Mon, 25 Jan 2016, David Miller wrote:
> >
> >> >> You cannot change the ABI after the release.
> >> > 
> >> > So do I have to add it to the current GLIBC version?
> >> 
> >> And the reason I am asking this is because this symbol is missing
> >> from previous
> >> GLIBC versions and just as I noticed when running the testsuite, probably
> >> prevents successful linking of some applications.
> >> 
> >> What if I want to add this symbol in a backport?
> >
> > Then your backport needs to add the GLIBC_2.23 symbol version (for older 
> > versions, that includes updating Versions.def, as new versions were less 
> > automatic than they are now).  That works fine, from experience.
> 
> It breaks the RPM dependency generator, unless you add *all*
> GLIBC_2.23 symbols.  Probably not relevant to sparc, but for other
> architectures, it's something to keep in mind.

When I say it works, I mean (a) the glibc with the backport builds OK and 
passes its tests, and (b) binaries linked with that glibc that don't use 
the new symbols work fine with glibc of the same version without the 
backport, while binaries linked with it that do use the new symbols work 
fine with the glibc version (2.23 in this case) that introduced them 
officially.

I don't think such a backport introducing new symbols should go on any 
official glibc release branch, however.

-- 
Joseph S. Myers
joseph@codesourcery.com


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