SEO

Hi, guys

I've just upgraded two systems from Slackware 10.1 to Slackware 11.0
(including all outstanding 11.0 patches), and all the standard
Slackware apps seem to run well. My first box has been up and stable
(as Slackware 11.0) for about 3 weeks now, and I converted the second
box over the last weekend. I'm running the 2.4.33.3 kernel that came
with Slackware (the bareacpi kernel), and uname -a reports
Linux merlin 2.4.33.3 #8 Fri Sep 1 04:19:03 CDT 2006 i686 pentium4
i386 GNU/Linux
and the standard Slackware 11.0 glibc libraries
glibc-2.3.6-i486-6
glibc-solibs-2.3.6-i486-6
glibc-zoneinfo-2.3.6-noarch-7_slack11.0

I downloaded and compiled from source the latest Wine release
(0.9.31), and all went well with the compile. Using checkinstall (from
the Slackware 11 install), I installed the completed wine packages.

Now, when I run any wine program (winecfg, for example), I get the
following errors:
lpitcher@merlin:/usr/local/src/wine-0.9.31$ winecfg
wine: glibc >= 2.3 without NPTL or TLS is not a supported combination.
It will most likely crash. Please upgrade to a glibc with NPTL
support.
wine: creating configuration directory '/home/lpitcher/.wine'...
wine: glibc >= 2.3 without NPTL or TLS is not a supported combination.
It will most likely crash. Please upgrade to a glibc with NPTL
support.
wine: Unhandled page fault on write access to 0x003ffd80 at address
0x60928103 (
thread 0009), starting debugger...
wine: glibc >= 2.3 without NPTL or TLS is not a supported combination.
It will most likely crash. Please upgrade to a glibc with NPTL
support.
wine: Unhandled page fault on write access to 0x003ffd80 at address
0x6092a103 (
thread 000b), starting debugger...
wine: glibc >= 2.3 without NPTL or TLS is not a supported combination.
It will most likely crash. Please upgrade to a glibc with NPTL
support.
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr
0x6000c04

I've tried an older version of Wine (a precompiled 10.2 Slackware pkg
from the Wine Sourceforge site), and it has no problem running (no
errors, winecfg runs properly, wine runs windows apps properly).

There doesn't seem to be any special setup instructions wrt Slackware
11, or Slackware in general in either the Wine readmes, the winehq.org
site, or the Slackware 11.0 UPGRADE.TXT or HINTS_AND_TIPS.TXT.
Further, there doesn't seem to be any open problems at winehq.org wrt
this error, with or without Slackware.

A google search on the error message pulls up others having the same
problem with wine under Slackware 11, and the suggested fixes have
been to
a) reinstall glibc (which I have done), and/or
b) download and install a wine package for Slackware 11 (which I have
done)
Neither solution has worked; I still get the glibc w/o TLS or NPTL
error message

So, I'm looking for either some hint on how to get the current Wine to
recognize TLS (which should be the default threading lib under this
Slackware config) or NPTL (and some help on how to get NPTL set up),
or instructions on what configuration I have to do in the wine compile
to have the Slackware threading libraries recognized and used by Wine.

Any suggestions?
--
Lew

On Tue, 20 Feb 2007 06:03:24 -0800, Lew Pitcher wrote:

> Hi, guys
>
> I've just upgraded two systems from Slackware 10.1 to Slackware 11.0
<snip>
> I downloaded and compiled from source the latest Wine release
> (0.9.31), and all went well with the compile. Using checkinstall (from
> the Slackware 11 install), I installed the completed wine packages.
>
<snip>
> Any suggestions?
>
Caveat: I don't run Wine (I prefer VMWare.)

This slack build script is by Eric Hamleers and is for building Wine,
up to the version you are are installing.
http://www.slackware.com/~alien/slac...ine.SlackBuild

Try this script, or compare your configuration using it as a reference
point.

I haven't built Wine using the script, but I have had good luck with the
build scripts in his repository.

--
Douglas Mayne

Lew Pitcher wrote:
> Hi, guys
>
> I've just upgraded two systems from Slackware 10.1 to Slackware 11.0
> (including all outstanding 11.0 patches), and all the standard
> Slackware apps seem to run well. My first box has been up and stable
> (as Slackware 11.0) for about 3 weeks now, and I converted the second
> box over the last weekend. I'm running the 2.4.33.3 kernel that came
> with Slackware (the bareacpi kernel), and uname -a reports
> Linux merlin 2.4.33.3 #8 Fri Sep 1 04:19:03 CDT 2006 i686 pentium4
> i386 GNU/Linux
> and the standard Slackware 11.0 glibc libraries
> glibc-2.3.6-i486-6
> glibc-solibs-2.3.6-i486-6
> glibc-zoneinfo-2.3.6-noarch-7_slack11.0
>
> I downloaded and compiled from source the latest Wine release
> (0.9.31), and all went well with the compile. Using checkinstall (from
> the Slackware 11 install), I installed the completed wine packages.
>
> Now, when I run any wine program (winecfg, for example), I get the
> following errors:
> lpitcher@merlin:/usr/local/src/wine-0.9.31$ winecfg
> wine: glibc >= 2.3 without NPTL or TLS is not a supported combination.
> It will most likely crash. Please upgrade to a glibc with NPTL
> support.

This may be completely unrelated, but I have Wine working on my system,
(Wine version 0.9.30), but I've had to add

Option "UseFastTLS" "2"

Into the video device section of my xorg.conf.

I didn't get the errors you get regarding glibc however. I'll
potentially try upgrading to .31 today and see how it goes.

BTW - was playing Half Life (from Steam) using 1920x1200 widescreen
resolution. I must say for the games it works with, it works very well.

Regards,

Richard


--
Richard Corden

> Option "UseFastTLS" "2"

Thanks :-)

I say thanks because I had a peek on Wine Documentation :

http://wiki.winehq.org/Slackware :
"Later version of Wine does not support glibc 2.3 without kernel+glibc
NPTL support. Slackware has NPTL support in glibc, but not in the 2.4
(default) kernel. To run Wine you'll need to upgrade to a 2.6 kernel."

See also.

http://www.winehq.org/pipermail/wine...t/036730.html:
http://www.winehq.org/pipermail/wine...er/040903.html

I hope the tricks *Option "UseFastTLS" "2"* will be a solution.

Regards,

--
Mounir

Mounir wrote:
>> Option "UseFastTLS" "2"
>
> Thanks :-)
>
> I say thanks because I had a peek on Wine Documentation :
>
> http://wiki.winehq.org/Slackware :
> "Later version of Wine does not support glibc 2.3 without kernel+glibc
> NPTL support. Slackware has NPTL support in glibc, but not in the 2.4
> (default) kernel. To run Wine you'll need to upgrade to a 2.6 kernel."

Ah - this explains why I've not seen this. Switching to a 2.6 kernel
was almost the first thing that I did after installing 11.

Regards,

Richard


--
Richard Corden

On Feb 20, 10:47 am, "Mounir" <downwa...@gmail.com> wrote:
> > Option "UseFastTLS" "2"
>
> Thanks :-)
>
> I say thanks because I had a peek on Wine Documentation :
>
> http://wiki.winehq.org/Slackware:
> "Later version of Wine does not support glibc 2.3 without kernel+glibc
> NPTL support. Slackware has NPTL support in glibc, but not in the 2.4
> (default) kernel. To run Wine you'll need to upgrade to a 2.6 kernel."
>
> See also.
>
> http://www.winehq.org/pipermail/wine...er/040903.html
>
> I hope the tricks *Option "UseFastTLS" "2"* will be a solution.

Darn. I must have missed that winehq page. Thanks for pointing it out.

I tried recompiling wine with --disable-debug --disable-opengl and
while it still kicks out the error message, winecfg seems to be
working (I actually got the window up this time).

I was planning to move to the 2.6 kernel, and this looks like a good
time to do it. P'haps I'll be able to get even better results with
that.

Thanks for the help, everyone
--
Lew

> >> Option "UseFastTLS" "2"

I confirm, it doesn't work with a 2.4 kernel even with this line
(indeed, if the kernel doesn't support, it doesn't support).

We have to recompile the kernel. The generic ones provided on the CDs
isn't a good choice ?

Regards,

--
Mounir