Yes, but take care of permissions. you need root permissions in ARM root file system.
On 6/20/07, Paul Kavan pkavan@gmail.com wrote:
On 6/20/07, Nobin Mathew nobin.mathew@gmail.com wrote:
Build alsa-lib and alsa-utils with prefix option
--prefix=/usr
while installing give the destination directory
make install DESTDIR=$MYINSTALLDIR
Then copy the installed executables to ARM root file sytem
This should solve the issue.
On 6/20/07, Takashi Iwai tiwai@suse.de wrote:
At Tue, 19 Jun 2007 16:31:31 -0400, Lee Revell wrote:
On 6/19/07, Paul Kavan < pkavan@gmail.com> wrote:
it should not be looking in this directory, but rather in "usr/share/alsa/alsa.conf". Might be why it cannot find the
alsa.conf
I struggled with the exact same problem about a year ago, I don't remember the solution but it's in the list archives.
The problem is likely you pass --prefix=$MYROOT/usr or so. The prefix option should be unchanged.
Anyway, alsa-lib-1.0.14a has extra configure options, --with-configdir and --with-plugindir, with which you can specify the exact paths, independent from $prefix.
Takashi
Thanks Takashi and Mathew. I just want to make sure I am clear on this. I create my embedded rfs for an ARM9 processor on my host machine. The path to the rfs is:
$HOME/buildroot/build_arm/root/...
So, you are saying that when I configure alsa-libs, I should be using:
CC=arm-linux-gcc ./configure --target=arm-linux --with-versioned=no --prefix=/usr
and then
make install DESTDIR=$HOME/buildroot/build_arm/root
Is this correct? I just want to make sure the libs will get into my target's rfs that way.
Thanks.
Paul
--
Paul David Kavan Project Engineer GRH Electronics, Inc. 402-734-4900 pkavan@gmail.com