alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: alsa-utils cross-compilation problem
Date: Tue, 19 Oct 2010 01:03:29 +0200	[thread overview]
Message-ID: <4CBCD241.6010100@gmail.com> (raw)
In-Reply-To: <AANLkTikV4gGR8Pstd9vFQvBXi7BJcpi6hcK+DRuX4swe@mail.gmail.com>

On 10/18/2010 08:52 AM, Reena Chauhan wrote:
> hi
> I had tried to cross compile the Alsa-utils 1.0.23&  m getting following
> errors:
> checking for libasound headers version>= 1.0.16... not present.
> configure: error: Sufficiently new version of libasound not found
>
> In my host PC alsa-lib 1.0.22 is installed
>

You need to cross-compile alsa-lib as well and then point the build 
process of alsa-utils to the correct pathes.

I can really suggest to let this job be done by some kind of 
cross-compile environment such as buildroot 
(http://buildroot.uclibc.org) or OpenEmbedded unless you have very good 
reasons to do it yourself.

Daniel

      reply	other threads:[~2010-10-18 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18  6:52 alsa-utils cross-compilation problem Reena Chauhan
2010-10-18 23:03 ` Daniel Mack [this message]

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=4CBCD241.6010100@gmail.com \
    --to=zonque@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).