All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hood <jdthood@yahoo.co.uk>
To: alsa-devel@alsa-project.org
Subject: 1.0.10rc2 alsa-utils build warnings under gcc 4.0.2
Date: Wed, 12 Oct 2005 15:14:44 +0200	[thread overview]
Message-ID: <434D0C44.5000905@yahoo.co.uk> (raw)

FYI alsa-utils build warnings under gcc 4.0.2

(Next time I will run with -Wno-pointer-sign.)


alsamixer.c:542: warning: pointer targets in passing argument 3 of ‘snd_mixer_selem_get_enum_item’ differ in signedness
alsamixer.c:805: warning: pointer targets in passing argument 3 of ‘snd_mixer_selem_get_enum_item’ differ in signedness
aplay.c:1335: warning: pointer targets in passing argument 1 of ‘pcm_write’ differ in signedness
aplay.c:1358: warning: pointer targets in passing argument 1 of ‘voc_pcm_write’ differ in signedness
aplay.c:1378: warning: pointer targets in passing argument 1 of ‘pcm_write’ differ in signedness
aplay.c:1875: warning: pointer targets in passing argument 1 of ‘pcm_write’ differ in signedness
aplay.c:1904: warning: pointer targets in passing argument 1 of ‘pcm_write’ differ in signedness
aplay.c:1929: warning: pointer targets in passing argument 1 of ‘pcm_read’ differ in signedness
aplay.c:2047: warning: pointer targets in assignment differ in signedness
aplay.c:2094: warning: pointer targets in assignment differ in signedness
aseqnet.c:378: warning: pointer targets in passing argument 3 of ‘accept’ differ in signedness



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

                 reply	other threads:[~2005-10-12 13:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=434D0C44.5000905@yahoo.co.uk \
    --to=jdthood@yahoo.co.uk \
    --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.