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

Bug#204706: Win4lin etc. binary compatibility



Hi all,

It appears the binary incompatibilities arise when an application is
compiled to be compatible with glibc 2.0+. So long as an application is
compiled for glibc 2.1+ it should also be compatible with glibc 2.3:

"It turns out we have discovered a bug in glibc 2.3.2 and the way the
dynamic linker tries to map entry points.  Win4Lin is compiled against
glibc 2.0.x today.  We are creating a test build environment which will
allow us to compile against glibc 2.1.x.  We have run some test
scenarios with small programs compiled against glibc 2.1.x, and they run
fine on glibc 2.3.2."

NeTraverse intends to migrate Win4lin to a glibc 2.1.x build environment
and will also report the glibc bug to the glibc maintainers:

"We will do our best to be very thorough with the testing, but
unfortunately there is not much time until glibc 2.3.2 hits the
mainstream, in Mandrake 9.2. Debian sid was one thing, because it is
completely experimental and we do not officially support Debian anyway. 
However one of the supported distributions going to 2.3.2 (Mandrake 9.2)
is something we have to act upon immediately.  We will not wait for the
glibc maintainers to fix this bug, unless they can do it in hours or
days.  We will of course file a bug report to the maintainers
regardless."

Full reply:
<https://www.netraverse.com:9100/lists/win4lin-users/Message/5099.html>

NeTraverse please note that Debian sid is not "completely experimental"
and in many ways is comparable to a cutting-edge release of a commercial
distribution. Many people use Debian sid quite productively and don't
run the "stable" release. For example Bruce Perens writes:

`I guess I should have mentioned that I almost always run "unstable".
I've always been impressed with its stability! I've had a down day once
in about 10 years due to a bad Debian package.

`I have no information regarding running it on "stable".

`Bruce'
<http://slashdot.org/comments.pl?sid=72629&cid=6547363>

There is also an experimental branch for experimental packages.

With that said, Leonardo E. Reiter's response on behalf of NeTraverse is
excellent and I'm sure the glibc maintainers are looking forward to
finding out the details of the bug in the dynamic linker.

Regards,
Adam




Reply to: