All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: developing audio with ALSA
Date: Mon, 18 Aug 2008 11:34:40 +0100	[thread overview]
Message-ID: <g8bj80$fmd$1@ger.gmane.org> (raw)
In-Reply-To: <000e01c90112$e89e7e30$ba3ea8c0@Richwave.net>

Henry Ho wrote:
> Hi
> 
> After reading the cross-compilation instruction in INSTALL file, 
> I already successfully configured the alsa-lib-2.0.17. I also 
> successfully made the library. Adding --prefix=xxx during 
> configuration can set the output directory to xxx.
> 
> I also modify my Makefile for application, including the search 
> path of libasound.so.2.***. Now I can successfully make it.
> 
> However, when I run my application on the target, I got the following 
> error message:
> 
> ******************************************************************************************
> ./pcm: error while loading shared libraries: libasound.so.2: cannot open 
> shared object file: No such file or directory
> ******************************************************************************************
> 
> I have put libasound.so.2.0.0 in /tmp of the target. I also modified 
> /etc/ld.so.conf, adding /tmp in ld.so.conf file. However, I cannot 
> find ldconfig on the target. Is anyone can tell me how to solve it?
> Should I rebuild a busybox with this command?

I'm wondering if you are mixing up --prefix and DESTDIR...

--prefix is the location that should be the *running systems* path on 
normal use. Even if you have a folder on your development machine that 
is different to that. e.g. say you are booting from compact flash: on 
your dev machine this may be mounted as /media/cf, but when you use it 
to boot it is actually the / of that system.

In this case I'd recommend you do:
./configure --prefix=/usr ....
make
sudo make DESTDIR=/media/cf install

That will install things in /media/cf.

You then need to modify other parts of your build to look in /media/cf 
for stuff and to strip out /media/cf from the linking, but that's 
another story.


All that said, I'd imagine you just didn't copy the symlinks that 
accoumpany the file libasound.so.2.0.0 ... it should come sith some 
symlinks that give it the name libasound.so.2 as well. (i.e. 
libasound.so.2 is a symlink to libasound.so.2.0.0)


Col

  parent reply	other threads:[~2008-08-18 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18  9:15 developing audio with ALSA Henry Ho
2008-08-18  9:57 ` Alan Horstmann
2008-08-18 10:34 ` Colin Guthrie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-13  6:48 Henry Ho
2008-08-13  8:19 ` Colin Guthrie

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='g8bj80$fmd$1@ger.gmane.org' \
    --to=gmane@colin.guthr.ie \
    --cc=alsa-devel@alsa-project.org \
    /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.