glibc tracker bug

[Mike Hearn]

Hi,

As we've been getting quite a few reports of glibc 2.3.x related
failures in bugzilla lately, it makes sense to mark them as dupes of a
bug, so I've started duping them against bug #1343

http://bugs.winehq.com/show_bug.cgi?id=1343

That way, when these problems are sorted out, we won't have to go
through and resolve them all manually.

thanks -mike

[Kevin DeKorte]

I have some RedHat Notes

RedHat 8.0 out of the box

Wine compiles fine, no extra options are needed

RedHat 8.0 up2date	with glibc-2.3.2-4.80

Wine compiles fine, no extra options are needed. But if wine has been built 
on the RedHat 8.0 OTB, then you should download a clean source tarball or if 
you use CVS, you should delete your working dir and check it out again.

RedHat 9

You need to set the environment variable LD_ASSUME_KERNEL=2.2.5 in the shell 
prior to running configure and prior to running wine.

Kevin

On Tuesday 01 April 2003 03:16 am, Mike Hearn wrote:
> Hi,
>
> As we've been getting quite a few reports of glibc 2.3.x related
> failures in bugzilla lately, it makes sense to mark them as dupes of a
> bug, so I've started duping them against bug #1343
>
> http://bugs.winehq.com/show_bug.cgi?id=1343
>
> That way, when these problems are sorted out, we won't have to go
> through and resolve them all manually.
>
> thanks -mike

[Dmitry Timoshkov]

"Kevin DeKorte"  wrote:
> RedHat 8.0 up2date with glibc-2.3.2-4.80
>
> Wine compiles fine, no extra options are needed. But if wine has been built 
> on the RedHat 8.0 OTB, then you should download a clean source tarball or if 
> you use CVS, you should delete your working dir and check it out again.

That means that binary compatibility between glibc-2.3.2-4.80 and a previous
version is broken. It would be very helpful to try to track it down or at least
report this problem to RedHat.

[Alexandre Julliard]

"Dmitry Timoshkov"  writes:
> That means that binary compatibility between glibc-2.3.2-4.80 and a previous
> version is broken. It would be very helpful to try to track it down or at least
> report this problem to RedHat.

It's the errno_location problem again. Yes it breaks binary
compatibility, but I'm afraid nobody cares.