From: Takashi Iwai <tiwai@suse.de>
To: Bernhard Gerlach <gerlacbd@emt.iis.fhg.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Q: Error on compiling/linking
Date: Fri, 10 Oct 2003 12:27:33 +0200 [thread overview]
Message-ID: <s5hu16h75gq.wl@alsa2.suse.de> (raw)
In-Reply-To: <3F865EE1.8080704@emt.iis.fhg.de>
At Fri, 10 Oct 2003 09:25:21 +0200,
Bernhard Gerlach wrote:
>
>
> Unfortunatly I forget to mention that the functions listed in the
> documentation which is linked to on Takashi's page (section "Documents
> on Alsa") seem to work, eg. snd_card_get_name, snd_seq_open and so on.
> That is the old api, isn't it?
ehm, yeah, most likely. i'm not sure which page you are referring to,
but i've not updated my web pages since long time...
>
>
> Takashi Iwai wrote:
>
> >>When compiling/linking, I receive:
> >>"undefined reference to `snd_seq_client_info_malloc'"
> >>Same for snd_seq_client_info_get_name and for snd_seq_client_info_free.
> >>
> >>What's wrong? Is'nt my lib up to date? (I read that the sequencer api
> >>has been rewritten with get/set functions, but in which version?)
> >
> >
> > how do you link libasound?
>
> The compiler options are -Wl,-Bdynamic -lasound.
> ldd says (when commenting out the not working function calls and
> compiling) that libasound.so.2 was linked.
then, no idea.
it'd be better to show your whole code then.
ciao,
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
next prev parent reply other threads:[~2003-10-10 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 16:08 Q: Error on compiling/linking gerlacbd
2003-10-09 16:25 ` Takashi Iwai
2003-10-10 7:25 ` Bernhard Gerlach
2003-10-10 10:27 ` Takashi Iwai [this message]
2003-10-10 11:32 ` Bernhard Gerlach
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=s5hu16h75gq.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=gerlacbd@emt.iis.fhg.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 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.