All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henderson <dhenderson@digital-pipe.com>
To: Adrian Pardini <pardo.bsso@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: compile problems
Date: Mon, 27 Jun 2011 09:56:37 -0400	[thread overview]
Message-ID: <4E088C15.3030608@digital-pipe.com> (raw)
In-Reply-To: <BANLkTi=mDwbo59wT5tAhmV0K60f6+TT2BQ@mail.gmail.com>

On 06/27/2011 09:35 AM, Adrian Pardini wrote:
> On 27/06/2011, David Henderson<dhenderson@digital-pipe.com>  wrote:
> [...]
>> checking for libasound headers version>= 1.0.16... not present.
>> configure: error: Sufficiently new version of libasound not
>> found.
>>
>>
>> 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?
> Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the
> configure script.
>
>

Thanks for the help Adrian.  I tried passing that parameter to the 
configure script and here's the below output:

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for cross-compiler... gcc
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for ALSA CFLAGS...  -I/opt/staging/alsa
checking for ALSA LDFLAGS...  -lasound -lm -ldl -lpthread
checking for libasound headers version >= 1.0.16... not present.
configure: error: Sufficiently new version of libasound not found.

I've double checked that the header files are present:
$ ls -1 /opt/staging/alsa/var/share/include/alsa/
alisp.h
asoundef.h
asoundlib.h
conf.h
control_external.h
control.h
error.h
global.h
hwdep.h
iatomic.h
input.h
mixer_abst.h
mixer.h
output.h
pcm_external.h
pcm_extplug.h
pcm.h
pcm_ioplug.h
pcm_old.h
pcm_plugin.h
pcm_rate.h
rawmidi.h
seq_event.h
seq.h
seqmid.h
seq_midi_event.h
sound/
timer.h
version.h


Thoughts?  Thanks - Dave

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

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 13:09 compile problems David Henderson
2011-06-27 13:35 ` Adrian Pardini
2011-06-27 13:56   ` David Henderson [this message]
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=4E088C15.3030608@digital-pipe.com \
    --to=dhenderson@digital-pipe.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=pardo.bsso@gmail.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.