From: Tomas Carnecky <tom@dbservice.com>
To: alsa-devel@lists.sourceforge.net
Subject: internal structures and 32/64bit compatibility
Date: Sun, 04 Dec 2005 00:25:11 +0000 [thread overview]
Message-ID: <43923767.2090704@dbservice.com> (raw)
I'm running gentoo on amd64 with the compat libs installes
(emul-linux-x86-soundlibs). I'm seeing some strange things that make me
think that either the internal structures have changed during the last
few versions or that they aren't 32/64bit compatible.
I have a 64bit mplayer and 32bit wine which I use to play World of
Warcraft. When I start mplayer to play a sound file, it works fine, I
even can start a second mplayer and I can hear both sounds. Now when I
start wine, I get this:
ALSA lib pcm_dmix.c:788:(snd_pcm_dmix_open) unable to create IPC shm
instance
The other way around, when I start wine first, the in-game sound works
fine. When I start mplayer later I get this:
mplayer: pcm_params.c:187: snd_pcm_hw_param_get_min: Assertion
`!snd_interval_empty(i)' failed.
Looks like they (the 32 and 64bit libraries) don't understand each
other. As I can't compile the 32bit libs on my own, they are precompiled
by the gentoo staff, I don't know which version they are, but the 64bit
alsa-lib has version 1.0.10.
Can someone explain whet is going on here?
I've tried to compile my own 32bit alsa-oss to test why teamspeak fails,
but libtool keeps using absolute paths (/usr/lib/libasound.so) but the
32bit libs are located in /usr/lib32, and I have no clue how to convince
libtool to use "-lasound" instead of the absolete path. And I guess
alsa-lib will be equally hard to compile for 32bit so I didn't even try it.
How can I compile alsa-lib for 32bit ?
thanks
tom
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-12-04 0:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 0:25 Tomas Carnecky [this message]
2005-12-04 1:12 ` internal structures and 32/64bit compatibility Tomas Carnecky
2005-12-05 15:05 ` Takashi Iwai
2005-12-05 19:59 ` Tomas Carnecky
2005-12-05 19:02 ` Takashi Iwai
2005-12-05 20:30 ` Tomas Carnecky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43923767.2090704@dbservice.com \
--to=tom@dbservice.com \
--cc=alsa-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.