From: Lee Revell <rlrevell@joe-job.com>
To: Elimar Riesebieter <riesebie@lxtec.de>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: 2.6.19rc1: pcm_native.c doesn't build
Date: Thu, 05 Oct 2006 16:26:48 -0400 [thread overview]
Message-ID: <1160080009.2481.98.camel@mindpipe> (raw)
In-Reply-To: <20061005201928.GD3809@frodo.home.lxtec.de>
On Thu, 2006-10-05 at 22:19 +0200, Elimar Riesebieter wrote:
> Hi all,
>
> I tried to build alsa-driver (sources) 1.0.13 against kernel
> 2.6.19rc1 on i386. The build stops with:
>
Is 2.6.19rc1 newer than ALSA 1.0.13? Building old ALSA against a new
kernel is not supported.
> /usr/bin/make -C /usr/src/linux-2.6.19-rc1 \
> SUBDIRS=/usr/src/modules/alsa-driver O=/usr/src/linux-2.6.19-rc1 \
> CPP="gcc-4.1 -E" CC="gcc-4.1" modules
> make[4]: Entering directory `/usr/src/linux-2.6.19-rc1'
> CC [M] /usr/src/modules/alsa-driver/acore/pcm_native.o
> /usr/src/modules/alsa-driver/acore/pcm_native.c:3569: error: unknown field \
> 'writev' specified in initializer
> /usr/src/modules/alsa-driver/acore/pcm_native.c:3569: warning: \
> initialization from incompatible pointer type
> /usr/src/modules/alsa-driver/acore/pcm_native.c:3589: error: unknown field \
> 'readv' specified in initializer
> /usr/src/modules/alsa-driver/acore/pcm_native.c:3589: warning: \
> initialization from incompatible pointer type
>
> Any hints?
>
> Elimar
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-10-05 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 20:19 2.6.19rc1: pcm_native.c doesn't build Elimar Riesebieter
2006-10-05 20:26 ` Lee Revell [this message]
2006-10-05 20:44 ` Elimar Riesebieter
2006-10-06 11:33 ` 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=1160080009.2481.98.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=riesebie@lxtec.de \
/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.