All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: One more cross compile issue: alsa-utils
Date: Tue, 06 Jun 2006 17:46:18 -0400	[thread overview]
Message-ID: <1149630378.4072.89.camel@mindpipe> (raw)

OK I have managed to cross compile alsa-lib 1.0.11 but now alsa-utils
complains about not being able to find the alsa-lib headers.

>From alsa-utils/config.log:

Invocation command line was

  $ ./configure --host=ppc-linux
--prefix=/home/rlrevell/cross-compile/usr/local
--includedir=/home/rlrevell/cross-compile/usr/local/include

...

This is where it dies:

configure:5355: checking dependency style of powerpc-440-linux-gnu-gcc
configure:5445: result: gcc3
configure:5475: checking for a BSD-compatible install
configure:5530: result: /usr/bin/install -c
configure:5541: checking whether ln -s works
configure:5545: result: yes
configure:5583: checking for ALSA CFLAGS
configure:5589: result:
configure:5592: checking for ALSA LDFLAGS
configure:5601: result:  -lasound -lm -ldl -lpthread
configure:5605: checking for libasound headers version >= 1.0.9
configure:5673: powerpc-440-linux-gnu-gcc -c -g -O2  conftest.c >&5
conftest.c:15:28: alsa/asoundlib.h: No such file or directory
conftest.c:36:9: #error not present
conftest.c:47:10: #error not present
configure:5679: $? = 1
configure: failed program was:

But, /home/rlrevell/cross-compile/usr/local/include/alsa/asoundlib.h
exists!!!  Why does ./configure insist that it does not?

Lee

             reply	other threads:[~2006-06-06 21:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 21:46 Lee Revell [this message]
2006-06-06 23:19 ` One more cross compile issue: alsa-utils Lee Revell

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=1149630378.4072.89.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.