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: autoconf.h error cross compiling
Date: Tue, 06 Jun 2006 16:20:09 -0400	[thread overview]
Message-ID: <1149625209.4072.57.camel@mindpipe> (raw)

I am trying to cross compile alsa-lib 1.0.11 for a PPC 440 embedded
system.  The build fails with this error:

Making all in instr
mkdir .libs
 powerpc-440-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include
-I../../include -D__ppc__ -g -O2 -MT fm.lo -MD -MP -MF .deps/fm.Tp
o -c fm.c  -fPIC -DPIC -o .libs/fm.o
 powerpc-440-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include
-I../../include -D__ppc__ -g -O2 -MT simple.lo -MD -MP -MF .deps/s
imple.Tpo -c simple.c  -fPIC -DPIC -o .libs/simple.o
 powerpc-440-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../include
-I../../include -D__ppc__ -g -O2 -MT iwffff.lo -MD -MP -MF .deps/i
wffff.Tpo -c iwffff.c  -fPIC -DPIC -o .libs/iwffff.o
In file included
from /opt/crosstool/gcc-3.4.2-glibc-2.3.2/powerpc-440-linux-gnu/lib/gcc/powerpc-440-linux-gnu/3.4.2/../../../../powe
rpc-440-linux-gnu/sys-include/asm/types.h:40,
                 from ../../include/sound/ainstr_iw.h:29,
                 from iwffff.c:47:
/opt/crosstool/gcc-3.4.2-glibc-2.3.2/powerpc-440-linux-gnu/lib/gcc/powerpc-440-linux-gnu/3.4.2/../../../../powerpc-440-linux-gnu/sys-
include/linux/config.h:4:28: linux/autoconf.h: No such file or directory
make[2]: *** [iwffff.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Why is it looking for autoconf.h?  AFAICT that is a kernel header.  Do I
merely have to copy it into the powerpc-440-linux-gnu/sys-include/linux/
directory?

Is the bug in my toolchain or alsa-lib?

Lee

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 20:20 Lee Revell [this message]
2006-06-06 21:04 ` autoconf.h error cross compiling Lee Revell
2006-06-07  9:54 ` Takashi Iwai

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=1149625209.4072.57.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.