From: Lee Revell <rlrevell@joe-job.com>
To: Elimar Riesebieter <riesebie@lxtec.de>
Cc: pkg-alsa-devel <pkg-alsa-devel@lists.alioth.debian.org>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: 1.0.13rc3: relocation error: mocp: symbol snd_pcm_hw_params_get_channels_min ..
Date: Tue, 26 Sep 2006 17:03:29 -0400 [thread overview]
Message-ID: <1159304610.2899.231.camel@mindpipe> (raw)
In-Reply-To: <20060926204053.GB3067@samweis.home.lxtec.de>
On Tue, 2006-09-26 at 22:40 +0200, Elimar Riesebieter wrote:
> On Tue, 26 Sep 2006 the mental interface of
> Lee Revell told:
>
> > On Tue, 2006-09-26 at 22:13 +0200, Elimar Riesebieter wrote:
> > > Hi all,
> > >
> > > I am testing 1.0.13rc3 (lib/driver/utils) on PPC/2.6.18
> > >
> > > Starting a soundapp like moc gives:
> > >
> > > "relocation error: mocp: symbol snd_pcm_hw_params_get_channels_min,
> > > version ALSA_0.9.0rc4 not defined in file libasound.so.2 with link
> > > time reference"
> > >
> > > Any hints?
> > >
> >
> > Application was compiled against a different alsa-lib version than is
> > present.
>
> This was my idea as well, but apps compiled with versions << 1.0.12
> are running with 1.0.13rc2?
It's not guaranteed that using a wrong library version won't work. It
may or may not. Just use the same version.
Lee
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-09-26 21:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 20:13 1.0.13rc3: relocation error: mocp: symbol snd_pcm_hw_params_get_channels_min Elimar Riesebieter
2006-09-26 20:23 ` Lee Revell
2006-09-26 20:40 ` Elimar Riesebieter
2006-09-26 21:03 ` Lee Revell [this message]
2006-09-26 21:31 ` Elimar Riesebieter
2006-09-27 12:35 ` Takashi Iwai
2006-09-27 18:13 ` Elimar Riesebieter
2006-09-27 18:55 ` Jaroslav Kysela
2006-09-28 10:28 ` Mike Frysinger
2006-09-27 6:41 ` Jaroslav Kysela
2006-09-27 18:07 ` Elimar Riesebieter
2006-09-27 19:23 ` Takashi Iwai
2006-09-27 19:48 ` Elimar Riesebieter
2006-09-28 10:18 ` Takashi Iwai
2006-09-28 10:34 ` Mike Frysinger
2006-09-28 18:02 ` Elimar Riesebieter
2006-09-28 18:16 ` Mike Frysinger
2006-09-28 18:44 ` Elimar Riesebieter
2006-09-28 18:52 ` Lee Revell
2006-09-28 19:15 ` Elimar Riesebieter
2006-09-28 19:33 ` Mike Frysinger
2006-09-28 18:59 ` Mike Frysinger
2006-09-28 19:28 ` Elimar Riesebieter
2006-09-28 19:52 ` Mike Frysinger
2006-09-29 10:03 ` Takashi Iwai
2006-09-29 19:54 ` Elimar Riesebieter
2006-09-28 10:23 ` Mike Frysinger
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=1159304610.2899.231.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pkg-alsa-devel@lists.alioth.debian.org \
--cc=riesebie@lxtec.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