From: Takashi Iwai <tiwai@suse.de>
To: Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: yesterday's morning cvs: via82xx build error?
Date: Mon, 20 Jan 2003 10:41:53 +0100 [thread overview]
Message-ID: <s5hd6ms5fa6.wl@alsa2.suse.de> (raw)
In-Reply-To: <1042926137.30435.11.camel@cmn37.Stanford.EDU>
At 18 Jan 2003 13:42:17 -0800,
Fernando Pablo Lopez-Lezcano wrote:
>
> [I sent this to linux-audio-devel by mistake... no clue what I was
> thinking]
>
> > Date: 17 Jan 2003 18:01:14 -0800
>
> Very strange:
> I'm seeing this while trying to compile the alsa drivers:
>
> gcc -D__KERNEL__ -DMODULE=1
> -I/usr/src/redhat/BUILD/alsa-driver-0.9.0/include
> -I/lib/modules/2.4.19-1.llsmp/build/include -O2
> -mpreferred-stack-boundary=2 -march=i686 -D__SMP__ -DCONFIG_SMP -DLINUX
> -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
> -DKBUILD_BASENAME=via82xx -c -o via82xx.o via82xx.c
> In file included from via82xx.c:1:
> ../alsa-kernel/pci/via82xx.c: In function `snd_via82xx_create':
> ../alsa-kernel/pci/via82xx.c:1588: structure has no member named
> `rate_lock'
> make[1]: *** [via82xx.o] Error 1
>
> The error happens when compiling in an SMP host with gcc2.96, but the
> same tarfile compiles fine on a UP host with gcc2.96 (same kernel) and
> on another UP host with gcc3.2...
fixed on cvs. could you update the cvs tree again?
thanks.
Takashi
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
next prev parent reply other threads:[~2003-01-20 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 21:42 yesterday's morning cvs: via82xx build error? Fernando Pablo Lopez-Lezcano
2003-01-20 9:41 ` Takashi Iwai [this message]
2003-01-21 4:51 ` Fernando Pablo Lopez-Lezcano
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=s5hd6ms5fa6.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=nando@ccrma.Stanford.EDU \
/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.