All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henderson <dhenderson@digital-pipe.com>
To: alsa-devel@alsa-project.org
Subject: compile problems
Date: Mon, 27 Jun 2011 09:09:39 -0400	[thread overview]
Message-ID: <4E088113.6040500@digital-pipe.com> (raw)

Greetings all!  I've tried this question in the "alsa user" group 
without success, but was pointed in the direction of this mailing list.  
Currently I'm trying to compile the alsa packages to get it compiled for 
a custom Linux distro.  I'm not having any problems compiling the 
alsa-lib package, but when I try to compile alsa-utils, I keep getting 
the following error:

checking for libasound headers version>= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not
found.


To provide more details about the situation, I'm using an existing 
distro (Kubuntu 9.10) to build the alsa packages and are using the 
/opt/staging/alsa directory to compile and "install" to (using the 
DESTDIR parameter).  Seeing as how this is a staging directory and not 
the actual place the package is being installed to, I'm having the afore 
mentioned problem because the alsa-utils package is looking under /... 
for the header files instead of the /opt/staging/alsa/... directory.  Is 
there a compile-time parameter that I can use so that alsa-utils looks 
in the staging directory for the header files - just during the compile 
phase?

Thanks,
Dave

             reply	other threads:[~2011-06-27 13:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 13:09 David Henderson [this message]
2011-06-27 13:35 ` compile problems Adrian Pardini
2011-06-27 13:56   ` David Henderson
2011-06-27 14:25     ` Adrian Pardini
2011-06-27 14:27       ` Adrian Pardini
2011-06-27 15:06         ` David Henderson
2011-06-27 14:59       ` David Henderson
2011-06-27 15:20     ` Takashi Iwai
2011-06-27 15:31       ` David Henderson
2011-06-27 16:07         ` Takashi Iwai
2011-06-27 16:30           ` David Henderson
2011-06-28  7:08             ` Takashi Iwai
2011-06-28 18:49               ` David Henderson
2011-06-28 14:12             ` David Henderson
2011-06-28 14:20               ` Takashi Iwai
2011-06-28 14:44                 ` David Henderson
2011-06-28 14:55                   ` Paul Menzel
2011-06-28 15:00                     ` David Henderson
  -- strict thread matches above, loose matches on Subject: below --
2008-10-30  2:49 jon doe
2008-10-30  5:38 ` Luis R. Rodriguez
2000-11-02 17:19 Problems with AMD CFI chips mark.langsdorf
2000-11-03 18:29 ` Compile problems Gregory Schallert
2000-11-04  2:20   ` David Woodhouse
2000-06-24 22:24 Jason Gunthorpe
2000-06-25 10:11 ` David Woodhouse
2000-06-25 23:08   ` Jason Gunthorpe
2000-06-26  6:44     ` David Woodhouse
2000-06-26  8:35       ` Jason Gunthorpe
2000-06-26  6:45     ` David Woodhouse
2000-06-26  8:37       ` Jason Gunthorpe

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=4E088113.6040500@digital-pipe.com \
    --to=dhenderson@digital-pipe.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 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.