[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ldbl128 transition for alpha, powerpc, sparc, s390

On Thu, May 31, 2007 at 11:36:55PM +0200, Matthias Klose wrote:
> With glibc-2.5 and gcc-4.1.2 (and gcc-4.2), the `long double' data
> type did change from a 64bit representation to a 128bit representation
> on alpha, powerpc, sparc, s390. To allow partial upgrades of packages,
> we will need to rename all packages holding libraries with the long
> double data type in their API.  Both libc and libstdc++ do not need to
> be renamed, because they support both representations. Attached you
> can find a list of packages with header files in /usr/include matching
> 'long *double'. If a library package is built from the same source as
> well, it has to be renamed, however the list may have false positives.

> Still unsure about how to handle extension modules in scripting
> languages; looking at python it may be sufficient to add conflicts
> with all extension modules exposing the long double datatype in their
> APIs.

> I plan to submit bug reports with severity `serious' for all source
> packages matching the above description (although if somebody wants to
> handle this transition, please go ahead).


> lsb-build-base2
> lsb-build-base3


Given what the LSB is, I expect that at least these packages need to be
updated to build using the old ABI.  How can this be done?

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Reply to: