From: "Imanol Trapote" <i.trapote@ziv.es>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, a.llano@usyscom.com
Subject: Re: Problems with ALSA in embedded device
Date: Thu, 06 Mar 2008 13:39:25 +0100 [thread overview]
Message-ID: <1204807165.3196.27.camel@debian.ziv.es> (raw)
In-Reply-To: <s5hy78y4mol.wl%tiwai@suse.de>
Thanks
I try that, but ALSA didn't work properly on the embedded system.
I will try use SALSA instead of ALSA.
I wrote her because doesn't exist SALSA mailing list.
I need to use aplay, I suppose with --enable-libasound, aplay must work?
It's neccesary change something else in alsa-utils to use aplay with
SALSA?
Thanks in advance.
El mar, 04-03-2008 a las 14:56 +0100, Takashi Iwai escribió:
> At Tue, 04 Mar 2008 14:29:20 +0100,
> Imanol Trapote wrote:
> >
> > Hi all,
> >
> > I am developing a product in an embedded system that uses ALSA library.
> > This system can't use the dynamic linker, I am using flat binaries.
> >
> > I use this configuration options:
> >
> > --without-libdl \
> > --with-pthread \
> > --with-softload \
> > --disable-alisp \
> > --disable-hwdep \
> > --disable-seq \
> > --disable-resmgr \
> > --disable-rawmidi \
> > --disable-old-symbols \
> > --disable-python \
> > --disable-mixer
> >
> > I try to use the same configuration options in a PC for debugging, and I
> > get the same problem, when I try to list devices with aplay, I get this:
> >
> > aplay -L
> > ALSA lib conf.c:2699:(snd_config_hooks_call) Cannot open shared library
> > (null)
> > ALSA lib conf.c:3076:(snd_config_update_r) hooks failed, removing
> > configuration
> >
> > It's possible use ALSA without dynamic libraries, with this
> > configuration
>
> Add --disable-shared and --enable-static. See INSTALL for details.
>
> I guess SALSA-lib would suit better in your case, though...
>
>
> Takashi
----------------------------------------- PLEASE NOTE -------------------------------------------
This message, along with any attachments, may be confidential or legally privileged.
It is intended only for the named person(s), who is/are the only authorized recipients.
If this message has reached you in error, kindly destroy it without review and notify the sender immediately.
Thank you for your help.
ZIV uses virus scanning software but excludes any liability for viruses contained in any attachment.
------------------------------------ ROGAMOS LEA ESTE TEXTO -------------------------------
Este mensaje y sus anexos pueden contener información confidencial y/o con derecho legal.
Está dirigido únicamente a la/s persona/s o entidad/es reseñadas como único destinatario autorizado.
Si este mensaje le hubiera llegado por error, por favor elimínelo sin revisarlo ni reenviarlo y notifíquelo inmediatamente al remitente. Gracias por su colaboración.
ZIV utiliza software antivirus, pero no se hace responsable de los virus contenidos en los ficheros anexos.
next prev parent reply other threads:[~2008-03-06 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 13:29 Problems with ALSA in embedded device Imanol Trapote
2008-03-04 13:56 ` Takashi Iwai
2008-03-06 12:39 ` Imanol Trapote [this message]
2008-03-06 14:12 ` Takashi Iwai
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=1204807165.3196.27.camel@debian.ziv.es \
--to=i.trapote@ziv.es \
--cc=a.llano@usyscom.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox