From: "RKHenry" <robert.henry@earthlink.net>
To: alsa-devel@alsa-project.org
Subject: Please, send ./configure output to <alsa-devel@alsa-project.org>
Date: Fri, 11 Mar 2005 13:49:35 -0500 [thread overview]
Message-ID: <000001c5266b$1368ab30$6401a8c0@rkh> (raw)
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
./configure --with-cards=sscape --with-sequencer=yes
checking for gcc... gcc
checking for C compiler default output... 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 ANSI C... none needed
checking for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking whether gcc needs -traditional... no
checking for current directory... /usr/src/alsa/alsa-driver-1.0.8
checking cross compile...
checking for directory with kernel source... /usr/src/linux
checking for directory with kernel build...
checking for kernel version... 2.2.16-22
checking for GCC version... Kernel compiler: gcc egcs-2.91.66 19990314/Linux
(egcs-1.1.2 release) Used compiler: 2.96
Fatal error: Compiler type does not match
Decoded kernel compiler: type=egcs version=2.91.66
Decoded used compiler: type=gcc version=2.96
Please, send ./configure output to <alsa-devel@alsa-project.org>
[-- Attachment #2: Type: text/html, Size: 8289 bytes --]
next reply other threads:[~2005-03-11 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 18:49 RKHenry [this message]
2005-03-11 20:01 ` Please, send ./configure output to <alsa-devel@alsa-project.org> 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='000001c5266b$1368ab30$6401a8c0@rkh' \
--to=robert.henry@earthlink.net \
--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.