From: Andrei Boros <andrei@srr.ro>
To: alsa-devel@lists.sourceforge.net
Subject: alsa-lib cvs compilation attempt:
Date: Mon, 10 Mar 2003 13:24:44 +0200 [thread overview]
Message-ID: <3E6C75FC.47BE6A73@srr.ro> (raw)
A cvs tree from 5 min. ago in alsa-lib:
loads of warnings for pcm_linear.c
Here are only some of them. I know these aren't critical, but there are
so many of them...
gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include -O2 -Wall -W
-pipe -g -Wp,-MD,.deps/pcm_linear.pp -c -fPIC -DPIC pcm_linear.c -o
pcm_linear.lo
pcm_linear.c: In function `snd_pcm_linear_convert':
pcm_linear.c:171: warning: `src' might be used uninitialized in this
function
pcm_linear.c:172: warning: `dst' might be used uninitialized in this
function
pcm_linear.c:173: warning: `src_step' might be used uninitialized in
this function
pcm_linear.c:173: warning: `dst_step' might be used uninitialized in
this function
pcm_linear.c:174: warning: `frames1' might be used uninitialized in this
function
pcm_linear.c: In function `snd_pcm_linear_getput':
pcm_linear.c:207: warning: `src' might be used uninitialized in this
function
pcm_linear.c:208: warning: `dst' might be used uninitialized in this
function
pcm_linear.c:209: warning: `src_step' might be used uninitialized in
this function
pcm_linear.c:209: warning: `dst_step' might be used uninitialized in
this function
pcm_linear.c:210: warning: `frames1' might be used uninitialized in this
function
--
ing. Andrei Boros
mailto:andrei@srr.ro / +40-21-303-1870
Centrul pt. Tehnologia Informatiei
Societatea Romana de Radiodifuziune
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2003-03-10 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 11:24 Andrei Boros [this message]
2003-03-10 14:14 ` alsa-lib cvs compilation attempt: 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=3E6C75FC.47BE6A73@srr.ro \
--to=andrei@srr.ro \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox