From: Takashi Iwai <tiwai@suse.de>
To: Martin Holzer <mholzer@gentoo.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: alsa-tools-1.0.0_rc1 has broken gcc 2.9x support
Date: Tue, 02 Dec 2003 17:14:02 +0100 [thread overview]
Message-ID: <s5hznebci45.wl@alsa2.suse.de> (raw)
In-Reply-To: <004c01c3b8ed$e8e9c420$0801a8c0@svrmarty.gnome.at>
At Tue, 2 Dec 2003 17:04:03 +0100,
Martin Holzer wrote:
>
(snip)
> configure: WARNING: If you wanted to set the --build type, don't use --host.
> If a cross compiler is detected then cross compile mode will be used.
> checking for a BSD-compatible install... /bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for i686-pc-linux-gnu-strip... no
> checking for strip... strip
> checking for i686-pc-linux-gnu-g++... g++
> 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 g++ accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of g++... gcc
> checking whether make sets $(MAKE)... (cached) yes
> checking for i686-pc-linux-gnu-gcc... gcc
> 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 dependency style of gcc... gcc
> checking how to run the C preprocessor... gcc -E
> checking for egrep... grep -E
> checking for ANSI C header files... yes
> checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
> checking for ALSA CFLAGS...
> checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread
> checking for libasound headers version >= 1.0.0... found.
> checking for snd_ctl_open in -lasound... yes
> checking for kernel header files... /lib/modules/2.6.0-test11/build/include
looks like you gave --with-kernel option.
2.6.0 tree has incompatible headers to ALSA 1.0.0 and they conflict.
simply run configure without this option.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-12-02 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 16:04 alsa-tools-1.0.0_rc1 has broken gcc 2.9x support Martin Holzer
2003-12-02 16:14 ` Takashi Iwai [this message]
2003-12-02 22:11 ` tom burkart
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=s5hznebci45.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mholzer@gentoo.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.