From: "Michel Benoit" <murpme@gmail.com>
To: Liam Girdwood <lg@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Frank Mandarino <fmandarino@endrelia.com>
Subject: Re: alsa on Atmel at91
Date: Fri, 11 May 2007 09:13:49 +0200 [thread overview]
Message-ID: <c88e466f0705110013n72325746w3698f4627cbbea6e@mail.gmail.com> (raw)
In-Reply-To: <c88e466f0705100716j44711fdnaa6f83e2f27afa3d@mail.gmail.com>
> After reading up on .symvers it seems that there is a version number
> used to select which function to link against.
>
> If I look in the file src/Versions it seems that there is no
> definition for ALSA_1.0.13. Could this be the problem? I'm still
> trying to figure out how and where the version ALSA_X.X.X is passed in
> to the linker.
More research reveals that the symbol defined with @@ is the default
symbol taht is used when no version is given. In my case the symbols
defined in pcm.c are:
.symver __snd_pcm_hw_params_get_period_size,snd_pcm_hw_params_get_period_size@@ALSA_0.9.0rc4
.symver __old_snd_pcm_hw_params_get_period_size,snd_pcm_hw_params_get_period_size@ALSA_0.9
and the __old version of the function should only be called if version
ALSA_0.9 is explicitely set by the app or somehow the default version
is being disabled or ignored.
Does anyone know how an application defines which version of symbols
it wants to use from a library?
Is there a way to disable symbol versioning in a lib?
Is any of this done explicitely as part of the alsa-lib and alsa-utils
build procedures?
Michel
next prev parent reply other threads:[~2007-05-11 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c88e466f0704151238q326df219uf95679897f4c44@mail.gmail.com>
[not found] ` <c88e466f0704170503o450c9af3mc299129751dec208@mail.gmail.com>
[not found] ` <1176813173.32188.181.camel@a10072.wolfsonmicro.main>
[not found] ` <c88e466f0704170857k27a7dc9fk63490e3d4acd172b@mail.gmail.com>
[not found] ` <1176827782.32188.224.camel@a10072.wolfsonmicro.main>
[not found] ` <c88e466f0704180218p708ba602h766f6a3f36c1add0@mail.gmail.com>
[not found] ` <1176889951.32188.246.camel@a10072.wolfsonmicro.main>
[not found] ` <c88e466f0704180500l2f016c4bs28c6a3c1a3663575@mail.gmail.com>
[not found] ` <1176900272.32188.274.camel@a10072.wolfsonmicro.main>
[not found] ` <c88e466f0704180745k1201ff11kc477d9cc8ebf899c@mail.gmail.com>
2007-05-10 11:29 ` alsa on Atmel at91 Michel Benoit
2007-05-10 13:28 ` Michel Benoit
2007-05-10 13:38 ` Liam Girdwood
2007-05-10 13:44 ` Michel Benoit
2007-05-10 14:16 ` Michel Benoit
2007-05-11 7:13 ` Michel Benoit [this message]
2007-05-11 9:07 ` Michel Benoit
2007-05-11 12:12 ` Frank Mandarino
2007-06-11 9:58 ` Matthieu CASTET
2007-06-12 12:57 ` 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=c88e466f0705110013n72325746w3698f4627cbbea6e@mail.gmail.com \
--to=murpme@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=fmandarino@endrelia.com \
--cc=lg@opensource.wolfsonmicro.com \
/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;
as well as URLs for NNTP newsgroup(s).