No, this is *not* yet another Mfc ctor post :-)
I was annoyed because I could not run some binaries ('native'
Linux programs, not through Wine) not compatible with my
libc 2.0.7 (comes with my Suse 6.1). For fun (?) I tried to do it
the geeky way and I downloaded the glibc sources from gnu.org.
After a few (!) problems and busy nights I can run Interbase 6.0 and
compile Wine again.
Now, this had some curious followings on Wine behaviour. Since
the only thing changed is the glibc it's a valid test I think (I kept
on my disk the 20000801 binary, compiled with glibc 2.0, for comparison)
- first, I have since a few months a problem with loading of
some 16 bits programs, for example Notepad from Win3.11
At loading the loader was failing to find some symbols in a
builtin Dll (.so). This was not a permanent problem, if I tried
again it would eventually start. I was very curious to see if
my libc upgrade would change that, it did. The problem has
completely vanished. I would love to know why this glibc
bug (?) would impact Wine only for common controls (never seen
this problem for 32 bits programs looking for comctl32).
- second, I had a problem with some 16 & 32 apps (see my
'BadWindow' message a few days ago). I was about to send
a fix for that, but I don't see it anymore with my new shining
2.1.2 glibc...I guess I will have to dump my patch now :-(
If other had similar experiences, it would probably a good thing
to include in the how-to or faq that while Wine will work
correctly for most programs with glibc 2.0, it works best with
glibc 2.1 (apart from the infamous Redhat 2.1.3 problem, of course)
Gerard
