All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Liam Girdwood <liam.girdwood@wolfsonmicro.com>
Cc: Adrian McMenamin <adrian@mcmen.demon.co.uk>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Problem with ALSA on PPC
Date: Mon, 12 Jun 2006 18:33:10 -0400	[thread overview]
Message-ID: <1150151590.3062.61.camel@mindpipe> (raw)
In-Reply-To: <1150112496.21190.38.camel@localhost.localdomain>

On Mon, 2006-06-12 at 12:41 +0100, Liam Girdwood wrote:
> Fwiw, I've been using OE 
> 
> http://www.openembedded.org/
> 
> to do all my embedded (non x86) ALSA user space building. It's quite
> simple and I've not had any issues wih building alsa-* yet. It even
> creates the device nodes and puts all the config files in the correct
> place in your target file system. 

I use Kegel's crosstool:

http://www.kegel.com/crosstool/

and modified scripts from the board vendor.  I can't easily switch as
this is what everyone else in the shop uses.

I guess OE solves this problem by building in a chroot or something?  I
cannot see a way to prevent alsa-lib from prepending $PREFIX to the
location of the config files.

Lee

  reply	other threads:[~2006-06-12 22:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 22:18 Problem with ALSA on PPC Lee Revell
2006-06-10  1:26 ` Lee Revell
2006-06-10 10:00   ` Adrian McMenamin
2006-06-10 16:59     ` Lee Revell
2006-06-12 11:03       ` Takashi Iwai
2006-06-12 21:57         ` Lee Revell
2006-06-13  9:35           ` Takashi Iwai
2006-06-13 10:57             ` Manuel Lauss
2006-06-13 18:22               ` Lee Revell
2006-06-13 15:45             ` Lee Revell
2006-06-13 16:20               ` Takashi Iwai
2006-06-12 11:41     ` Liam Girdwood
2006-06-12 22:33       ` Lee Revell [this message]
2006-06-13  0:40     ` Lee Revell
2006-06-13 18:09       ` Adrian McMenamin

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=1150151590.3062.61.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=adrian@mcmen.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=liam.girdwood@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 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.