All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Carnecky <tom@dbservice.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: internal structures and 32/64bit compatibility
Date: Sun, 04 Dec 2005 01:12:26 +0000	[thread overview]
Message-ID: <4392427A.9090608@dbservice.com> (raw)
In-Reply-To: <43923767.2090704@dbservice.com>

Tomas Carnecky wrote:
> 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.

... they should update their packages ;)


> 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 ?
> 

was easier that I've expected:

./configure --prefix=~/root LDFLAGS="-L/emul/linux/x86/usr/lib -m32" 
CFLAGS="-L/emul/linux/x86/usr/lib -m32"

and the package compiled without errors, copied the library to the lib32 
path and now I can play WoW and listen to music !

but the aoss wrapper library (version 1.0.10) still fails:

$ ALSA_OSS_DEBUG=1 LD_PRELOAD=/emul/linux/x86/usr/lib/libaoss.so.0.0.0 
TeamSpeak
ERROR: ld.so: object '/emul/linux/x86/usr/lib/libaoss.so.0.0.0' from 
LD_PRELOAD cannot be preloaded: ignored.
Opened PCM dsp0 for stream 0 (result = -2)
Opened PCM default for stream 0 (result = 0)
Opened PCM default for stream 1 (result = 0)
open("/dev/dsp", 2, 0) -> 18
ioctl(18, SNDCTL_DSP_RESET)
ioctl(18, SNDCTL_DSP_SETDUPLEX)
ioctl(18, SNDCTL_DSP_GETCAPS, 0x590e9168) -> [13056]
ioctl(18, SNDCTL_DSP_SETFRAGMENT, 0x590e916c[3000c])
dsp ioctl error = -22
close(18) -> 0
$

Maybe a bug in TeamSpeak itself, not initializing the device properly, 
but it works fine under native oss. I even tracked down the file and 
line on which it fails (posted to the alsa-user mailing list). So if 
someone has a clue how to fix this I'd be more than happy to test it.

Just commenting out the function call didn't help, so that call seems to 
be important for the device initialization. Seems like the function 
arguments ate calculated wrong, but I'm not a sound expert and I don't 
know what the valid fucntiion arguments are.

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

  reply	other threads:[~2005-12-04  1:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-04  0:25 internal structures and 32/64bit compatibility Tomas Carnecky
2005-12-04  1:12 ` Tomas Carnecky [this message]
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=4392427A.9090608@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.