Re: Problem with ALSA on PPC

[Lee Revell <rlrevell@joe-job.com>]

On Mon, 2006-06-12 at 13:03 +0200, Takashi Iwai wrote:
> At Sat, 10 Jun 2006 12:59:15 -0400,
> Lee Revell wrote:
> > > > I found the problem by installing strace on the PPC board.  alsa-lib is
> > > > looking for its config files using the original path from the build
> > > > host.  Either my build environment is still incorrect or it's a bug -
> > > > probably the former ;-)
> > > > 
> > > > Once I am done maybe I will write an embedded ALSA HOWTO.
> > > > 
> > > > Lee
> > > > 
> > > 
> > > I had/have a very similar problem with the Dreamcast - I can only use
> > > the oss emulation
> > > 
> > > Asking about here didn't get me an answer so I await any answers to your
> > > problem with anticipation...
> > > 
> > > / # aplay -l
> > > **** List of PLAYBACK Hardware Devices ****
> > > aplay: device_list:230: control open (0): Invalid argument
> > 
> > I don't know how I ever could have solved this without strace - the ALSA
> > library is a twisty maze of function pointers.
> 
> Yeah, plugins hell.
> 
> >  Have you looked into
> > porting strace to your platform?
> 
> The open/close of all config stuff is done only in src/input.c and
> output.c.  The open of device files is done via snd_open_device()
> defined in include/local.h.  So, checking these entries cover most of
> open/close operations in alsa-lib.

How can I build alsa-lib with a non-standard --prefix, but at runtime
have it look for its config files in the standard location?  IOW how do
I prevent the --prefix from being prepended?

I am generating a ramdisk image that is transferred over to a PPC board,
and except for this problem, alsa-lib works on the target.

Looking at ./configure options, it seems like it's not possible?

Lee