LinuxQuestions.org - Wine build errors in Slackware 11.0

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Wine build errors in Slackware 11.0 (https://www.linuxquestions.org/questions/slackware-14/wine-build-errors-in-slackware-11-0-a-513504/)

Wine build errors in Slackware 11.0

I'm having difficulty installing Wine 0.9.28 from source.
So far I've found this info:

On the slackware site, a quote from Current ChangeLog for Intel:

Quote:

I'd like to put the NPTL version of glibc into /lib and the LinuxThreads
version into /lib/obsolete/linuxthreads (since some old binaries are
going to need them)...
.
.
.
Comments about this issue are welcomed.

A quote from the Wine 0.9.28 loader after a configure and compile:

Quote:

.
.
.
Wine build complete.
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 0x60915103 (thread 0009), starting debugger...
.
.
.

It appears that Pat V. doesn't want to upgrade glibc because
that would end support for 2.4 kernels. I don't mind going to 2.6
kernels, but I'd rather not mess with glibc...does this mean no Wine?
More accurately, no _new_ Wine?
A quick web search indicates that there are segfaults on
some packages as well. Any pointers?

Thanks,
--Lawrence

Have you tried the Wine packages of Alien Bob?
It is 0.9.25, but you might be able to build 0.9.28 from his ./build directory.

I didn't think that this was going to be a problem because we have NPTL and TLS. They just aren't directly in /lib.

Right?

I'm interested to know more about this. I thought that as long as they are properly set up it doesn't really matter where they are. I know we have NPTL and TLS because if you ldd any binary it links to one of them. There must be something else going on?

I didn't get any such output when I just now built it to test... Seems to be happy as a clam.. The only warning I got was with regards to a missing FontForge package after configure. After make, it just said "build complete."

try this to see if it get's rid of that error.

Code:

LDFLAGS="-L/lib/tls" \

./configure --prefix=/usr \

    --mandir=/usr/man

make depend

make

make install DESTDIR=/tmp/package-wine

cd /tmp/package-wine

makepkg ../wine-test.tgz

I also ran it against some random exe from my windows partition. It started just fine. Got a wine dialog box giving an error but it was complaining of a runtime error with that particular exe. It wasn't linux related...

Try using the prefix option and leave out the LDFLAGS. That shouldn't have anything to do with it. Perhaps you were using configure without any arguements and because it was set for /usr/local, it didn't pick up on anything in /lib... Don't know. Just guessing. Builds and runs fine over here tho on Slack 11

Thanks for the wine pkg link. The package runs but with:

err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x6000c04b

I should have looked a bit further...

http://bugs.winehq.org/show_bug.cgi?id=6209

with a comment from 9/15/06 shows this same problem
and lists the solution as a 2.6 kernel and 2.6 headders
to build wine properly.

But doesn't this seems a bit circular? If the wine version
needs a glibc update, and I compile a 2.6 kernel with 2.6
headders insted of the 2.4 as in the distribution, using
the shipped lower version of glibc instead...that sounds
like I'd be right back where I started minus some time, but
plus a 2.6 kernel. Interesting. It's possible the NPTL and TLS
problem listed is local to wine..i.e. wine doesn't find them
_unless_ the are in /lib. The idea of re-doing glibc is what motivated me to post. I'll hunt some more. And study Alien Bob's build script...but
probably not till the day after Christmas...oh, by the way,

Merry Christmas
--Lawrence

{edit} Just saw jong357's post..I'll try that thanks.

I'm building on a 2.6.18.6 kernel with 2.6.18 kernel headers... Didn't think of that... :-) I can tell you it works fine going that route. One more program that needs updated progs to build... I'll be glad when the 2.4 stuff goes for good. For your guy's sake, not mine... :D

Hmmm..

I think it means that your glibc needs to be compiled with a 2.6 kernel. In which case you probably haven't installed the 2.6.17.13 headers from /extra.

Glibc in Slackware 11 is compiled with both the 2.4 and 2.6 headers if you can believe it. So if you're running a 2.6 kernel it will use NPTL when necessary. If you're using the 2.4 kernel it will use TLS.

I'm willing to bet you're having a problem because you don't have those 2.6.17.13 headers installed along with the 2.4 headers.

EDIT: You'll have to be running a 2.6 kernel as well.

EDIT2: I think this post was completely redundant and unnecessary now that I've read the thread a few times over. I won't delete it though just in case... but sorry if I'm just blowing wind... :)

Sorry for the long delay in posting results of the suggestions
I was given. After some thought I decided to go to the 2.6
kernel sources for 2.6.19.1 and ALSA 1.0.14rc1 with Wine 0.9.28

Wine built without errors, and has run the apps I've tried on it.
It appears glibc is not an issue with the two 2.6 kernels I tried.
The Slack Distro package for 2.6.18 built Wine well, but I have an
ALSA problem with my hardware that bumped me up to 2.6.19.1 and
ALSA 1.0.14rc1:confused:

Oh well, I'd have posted sooner but there was learning the 2.6 config
and chasing an ethernet problem to get back online, and
Christmas and New Year and a biological bug that put me in bed for
a time---I think if I'd have had a dog he'd have chewed my keyboard
like a leather bone.:)

It's OT, but the app I wanted wine for is a musical notation
editor called Mozart...and it runs fine but can't quite connect
to ALSA yet...But even so, I'm really happy with the 2.6.19.1
Kernel, and my ethernet card's not throwing errors, and with the
preempt kernel, jack X-runs are gone. All in all, for me, a
useful exercise. Thanks again for the help.

--Lawrence

Hi!

Lawrence,

I've just got the same thing. The same wine message...
I'm quite 'newbie' with kernel. I've configured kernel many times but I'm afraid of the update from 2.4x to 2.6x.
Please help me with detailed instructions, or a web page address where it is detailed.

Thanks,
Oliver

Hi schrodingerscat,

The build requirements for Wine 0.9.28 from http://www.winehq.com/
include 2.6 kernel and headers. Note that jong357 had success with
2.6.18.6 kernel with 2.6.18 kernel headers. Ambition got the better of
me. I downloaded the 2.6.19.1 sources from kernel.org. But to get
sound, I had to enable sound in the kernel but *not* configure in alsa,
Then after installing the new kernel, build alsa 1.0.14rc1 and install
it. I needed a couple of build iterations and trips to the web to figure
it out, but this combination worked for me. I think the module + other
problems I had were because of my particular hardware and my
personality...you should have a better time even with the 2.6.19.1
kernel. But presently, in this version you will need to do those alsa gyrations.

If you can, keep it simple. Check out the stickies on the Slackware forum
http://www.linuxquestions.org/questi...d.php?t=174447
and http://www.linuxquestions.org/questi...d.php?t=402003
and http://www.linuxquestions.org/questi...d.php?t=127095

Consider that the easiest way to get to 2.6.xx is to use the 2.6.17.13
kernel and headers pkgs in /extra that come with the distribution.
These may work fine for you. I also note that The LAU list opinion
seems to be that 2.6.18.xx is a good stable choice. If you decide
against the pkgs, download a full source tree from kernel.org and pay
attention to the issues in the links above. If you use the Slackware
packages remember you must load the modules manually and that the
install though simpler should be preceded by re-naming your /boot files
and editing /sbin/lilo so you have a backup kernel, and possibly making
an initrd(see the slack 11 release notes)

Going much further on kernel building should be another thread..my real
concern in posting here was glibc compatibility between the kernel
versions, but I hope this helps.

Frankly glibc is still on my mind, but the change logs say that the
toolchain is being upgraded...so i'll wait and see...

--Lawrence

Just for the sake of clarity, this is what I am running:

Code:

mingdao@silas:~/kernel/linux-2.6.19$ cat .config

# Sound

#

CONFIG_SOUND=m



#

# Advanced Linux Sound Architecture

#

CONFIG_SND=m

CONFIG_SND_TIMER=m

CONFIG_SND_PCM=m

CONFIG_SND_HWDEP=m

CONFIG_SND_RAWMIDI=m

# CONFIG_SND_SEQUENCER is not set

CONFIG_SND_OSSEMUL=y

CONFIG_SND_MIXER_OSS=m

CONFIG_SND_PCM_OSS=m

CONFIG_SND_PCM_OSS_PLUGINS=y

# CONFIG_SND_DYNAMIC_MINORS is not set

# CONFIG_SND_SUPPORT_OLD_API is not set

# CONFIG_SND_VERBOSE_PROCFS is not set

# CONFIG_SND_VERBOSE_PRINTK is not set

# CONFIG_SND_DEBUG is not set



#

# Generic devices

#

CONFIG_SND_AC97_CODEC=m

CONFIG_SND_AC97_BUS=m

# CONFIG_SND_DUMMY is not set

# CONFIG_SND_MTPAV is not set

# CONFIG_SND_SERIAL_U16550 is not set

# CONFIG_SND_MPU401 is not set



#

# PCI devices

#

# CONFIG_SND_AD1889 is not set

# CONFIG_SND_ALS300 is not set

# CONFIG_SND_ALS4000 is not set

# CONFIG_SND_ALI5451 is not set

# CONFIG_SND_ATIIXP is not set

# CONFIG_SND_ATIIXP_MODEM is not set

# CONFIG_SND_AU8810 is not set

# CONFIG_SND_AU8820 is not set

# CONFIG_SND_AU8830 is not set

# CONFIG_SND_AZT3328 is not set

# CONFIG_SND_BT87X is not set

# CONFIG_SND_CA0106 is not set

# CONFIG_SND_CMIPCI is not set

# CONFIG_SND_CS4281 is not set

# CONFIG_SND_CS46XX is not set

# CONFIG_SND_CS5535AUDIO is not set

# CONFIG_SND_DARLA20 is not set

# CONFIG_SND_GINA20 is not set

# CONFIG_SND_LAYLA20 is not set

# CONFIG_SND_DARLA24 is not set

# CONFIG_SND_GINA24 is not set

# CONFIG_SND_LAYLA24 is not set

# CONFIG_SND_MONA is not set

# CONFIG_SND_MIA is not set

# CONFIG_SND_ECHO3G is not set

# CONFIG_SND_INDIGO is not set

# CONFIG_SND_INDIGOIO is not set

# CONFIG_SND_INDIGODJ is not set

CONFIG_SND_EMU10K1=m

# CONFIG_SND_EMU10K1X is not set

# CONFIG_SND_ENS1370 is not set

# CONFIG_SND_ENS1371 is not set

# CONFIG_SND_ES1938 is not set

# CONFIG_SND_ES1968 is not set

# CONFIG_SND_FM801 is not set

# CONFIG_SND_HDA_INTEL is not set

# CONFIG_SND_HDSP is not set

# CONFIG_SND_HDSPM is not set

# CONFIG_SND_ICE1712 is not set

# CONFIG_SND_ICE1724 is not set

# CONFIG_SND_INTEL8X0 is not set

# CONFIG_SND_INTEL8X0M is not set

# CONFIG_SND_KORG1212 is not set

# CONFIG_SND_MAESTRO3 is not set

# CONFIG_SND_MIXART is not set

# CONFIG_SND_NM256 is not set

# CONFIG_SND_PCXHR is not set

# CONFIG_SND_RIPTIDE is not set

# CONFIG_SND_RME32 is not set

# CONFIG_SND_RME96 is not set

# CONFIG_SND_RME9652 is not set

# CONFIG_SND_SONICVIBES is not set

# CONFIG_SND_TRIDENT is not set

# CONFIG_SND_VIA82XX is not set

# CONFIG_SND_VIA82XX_MODEM is not set

# CONFIG_SND_VX222 is not set

# CONFIG_SND_YMFPCI is not set

# CONFIG_SND_AC97_POWER_SAVE is not set



#

# USB devices

#

# CONFIG_SND_USB_AUDIO is not set

# CONFIG_SND_USB_USX2Y is not set



#

# Open Sound System

#

# CONFIG_SOUND_PRIME is not set

And which ALSA packages?

Code:

mingdao@silas:~/kernel/linux-2.6.19$ ls -l /var/log/packages/alsa*

-rw-r--r-- 1 root root 17364 2006-11-04 20:57 /var/log/packages/alsa-driver-1.0.11_2.4.33.3-i486-1

-rw-r--r-- 1 root root  4938 2006-11-04 20:57 /var/log/packages/alsa-lib-1.0.11-i486-1

-rw-r--r-- 1 root root  1093 2006-11-04 20:57 /var/log/packages/alsa-oss-1.0.11-i486-1

-rw-r--r-- 1 root root  2645 2006-11-04 20:54 /var/log/packages/alsa-utils-1.0.11-i486-2

Which Slackware version?

Code:

mingdao@silas:~/kernel/linux-2.6.19$ cat /etc/slackware-version

Slackware 11.0.0

Which kernel?

Code:

mingdao@silas:~/kernel/linux-2.6.19$ uname -a

Linux silas 2.6.19 #4 PREEMPT Sun Dec 3 09:29:12 CST 2006 i686 athlon-4 i386 GNU/Linux

Is ALSA broken in 2.6.19.1? I'll compile it and find out ...

Might be your configurations.

This alsa troubleshooting page describes my problem in the last entry at the bottom of the page.
http://alsa2.opensrc.org/TroubleShooting&redirect=noyep
After configuring with the alsa module in the 2.6.19.1 source. Alsa throws this:
alsamixer: function snd_ctl_open failed for default: No such device
And, of course, no sound.

What is your motherboard?

Soundchip?

Code:

mingdao@silas:~$ /sbin/lspci | grep -i multimedia

00:0c.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)

For mine, Asus K8v-X, and I use the Audigy LS.

I found this shell script useful for gathering
data on my the sound setup
http://alsa.opensrc.org/Aadebug
As an example of its output here's my working configuration

Quote:

root@ark:/home/let01# ./aadebug
ALSA Audio Debug v0.1.0 - Wed Jan 3 14:43:12 CST 2007
http://alsa.opensrc.org/index.php?page=aadebug
http://www.gnu.org/licenses/gpl.txt

Kernel ----------------------------------------------------
Linux ark 2.6.19.1 #1 PREEMPT Mon Jan 1 13:28:02 CST 2007 i686 pentium4 i386 GNU/Linux

Loaded Modules --------------------------------------------
snd_seq_midi 6432 0
snd_seq_oss 31360 0
snd_seq_midi_event 6016 2 snd_seq_midi,snd_seq_oss
snd_seq 45264 5 snd_seq_midi,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss 40864 0
snd_mixer_oss 14848 1 snd_pcm_oss
snd_ens1371 21280 1
snd_rawmidi 19488 2 snd_seq_midi,snd_ens1371
snd_seq_device 6668 4 snd_seq_midi,snd_seq_oss,snd_seq,snd_rawmidi
snd_ac97_codec 90404 1 snd_ens1371
snd_ac97_bus 2048 1 snd_ac97_codec
snd_pcm 70664 3 snd_pcm_oss,snd_ens1371,snd_ac97_codec
snd_timer 20100 2 snd_seq,snd_pcm
snd 45412 12 snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_ens1371,snd_rawmidi,snd_seq_device,snd_ac97_codec, snd_pcm,snd_timer
snd_page_alloc 7816 1 snd_pcm

Proc Config -----------------------------------------------
CONFIG_SOUND=y
# CONFIG_SND is not set
CONFIG_SOUND_PRIME=m
# CONFIG_SOUND_BT878 is not set
CONFIG_SOUND_ES1371=m
CONFIG_SOUND_ICH=m
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
# CONFIG_SOUND_OSS is not set

Modprobe Conf ---------------------------------------------

Proc Asound -----------------------------------------------
Advanced Linux Sound Architecture Driver Version 1.0.14rc1.
Compiled on Jan 3 2007 for kernel 2.6.19.1.
0 [AudioPCI ]: ENS1371 - Ensoniq AudioPCI
Ensoniq AudioPCI ENS1371 at 0xd480, irq 3
0: [ 0] : control
1: : sequencer
8: [ 0- 0]: raw midi
16: [ 0- 0]: digital audio playback
17: [ 0- 1]: digital audio playback
24: [ 0- 0]: digital audio capture
33: : timer
cat: /proc/asound/hwdep: No such file or directory
00-01: ES1371/2 : ES1371 DAC1 : playback 1
00-00: ES1371/1 : ES1371 DAC2/ADC : playback 1 : capture 1
Client info
cur clients : 3
peak clients : 3
max clients : 192

Client 0 : "System" [Kernel]
Port 0 : "Timer" (Rwe-)
Port 1 : "Announce" (R-e-)
Connecting To: 15:0
Client 15 : "OSS sequencer" [Kernel]
Port 0 : "Receiver" (-we-)
Connected From: 0:1
Client 16 : "Ensoniq AudioPCI" [Kernel]
Port 0 : "ES1371" (RWeX)

Dev Snd ---------------------------------------------------
controlC0 midiC0D0 pcmC0D0c pcmC0D0p pcmC0D1p seq timer

CPU -------------------------------------------------------
model name : Intel(R) Pentium(R) 4 CPU 2.00GHz
cpu MHz : 1993.613

RAM -------------------------------------------------------
MemTotal: 515452 kB
SwapTotal: 996012 kB

Hardware --------------------------------------------------
00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset Host Bridge (rev 11)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
02:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 04)

[edit] The motherboard is what Dell put in this 4500...I've never got a good name for it...
I have invented some :) The chipsets are listed above.

[edit2] Sorry, I forgot this:

Quote:

let01@ark:~$ cat /etc/slackware-version
Slackware 11.0.0

The Alsa is 1.0.14rc1 developement releases from alsa-progect.org/
built and installed manually from my software test directory not pkgs.
/var/log/packages/alsa dosen't show them it shows the original set from
2.4.33.3 kernel & alsa 1.0.11 that I started with :

Quote:

let01@ark:~$ ls -l /var/log/packages/alsa*
-rw-r--r-- 1 root root 17364 2006-10-31 16:54 /var/log/packages/alsa-driver-1.0.11_2.4.33.3-i486-1
-rw-r--r-- 1 root root 4938 2006-10-31 16:54 /var/log/packages/alsa-lib-1.0.11-i486-1
-rw-r--r-- 1 root root 1093 2006-10-31 16:54 /var/log/packages/alsa-oss-1.0.11-i486-1
-rw-r--r-- 1 root root 2645 2006-10-31 16:51 /var/log/packages/alsa-utils-1.0.11-i486-2

BTW sound worked fine with that combo. Going to 2.6 the way I did it broke sound.

Edit in: 14:15, 22 February 2007.
Problem solved. Please delete this message.
Thank you.