lør, 23.06.2007 kl. 15.48 +0200, skrev Matthias Klose: > Package: libwine-dev > Severity: serious > User: [EMAIL PROTECTED] > Usertags: goal-ldbl128 > > Discussed in http://lists.debian.org/debian-devel/2007/05/msg01173.html > > 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. We rename the library > packages on all architectures to avoid name mismatches between > architectures (you can avoid the renaming by supporting both > datatype representations in the library as done in glibc and > libstdc++, but unless a library is prepared for that, it does not > seem to be worth the effort). > > It is suggested to rename a package libfoo1 to libfoo1ldbl; > please wait with the renaming if the package depends on > another library package which needs renaming. > > This package has been indentified as one with header files in > /usr/include matching 'long *double'. Please close this bug report > if it is a false positive, or rename the package accordingly.
I've found two occurrences of "long double" in the Winelib public headers. They're in include/msvcrt/stdlib.h, as return values of two "Microsoft-extended" library calls. Nevertheless, I'd like to believe that there's no reason for the Wine package to go through such a transition. No other package in Debian depends on libwine, save Wine itself. And if some non-i386 Winelib user (if they currently exist) depends on libwine for some project of their own, and for some masochistic reason isn't compiling and hacking Wine themselves (almost a necessity since Wine still have lots of flaws), and also actually depend on these special Microsoft runtime library calls, then they're probably able to recompile their project with their new compiler. Anyone think otherwise?
