From alsa-devel-owner@alsa.jcu.cz  Wed Aug 26 11:13:07 1998
Received: from ural2.hszk.bme.hu (nobody@ural2.hszk.bme.hu [152.66.130.2])
	by marvin.jcu.cz (8.8.8/8.8.8) with ESMTP id LAA18184
	for <alsa-devel@alsa.jcu.cz>; Wed, 26 Aug 1998 11:10:51 +0200
Received: (from sa027@localhost)
	by ural2.hszk.bme.hu (8.8.8/8.8.8) id LAA02315;
	Wed, 26 Aug 1998 11:10:51 +0200 (MET DST)
Date: Wed, 26 Aug 1998 11:10:50 +0200 (MET DST)
From: Simon Andras <sa027@hszk.bme.hu>
To: alsa-devel@alsa.jcu.cz
Subject: ALSA-driver 0.2.0 gcc warnings
Message-ID: <Pine.GSO.4.02A.9808261059170.1100-100000@ural2>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Hello,

1.
During the compilation of the alsa-driver 0.2.0, 
gcc 2.8.1-1 (or 2.8.1) dumps a lot of warnings
about functions: "Return type is defaulted to int"
or something similar. Not a huge problem, only
this new gcc is "too" smart and warns for every
little dirt (even for a main() without return)

2.
"Too many {'s" and "Too many }'s" are common
during compilation.

3.
ALSA-utils: aplay.c :  braces around ambigous else
It compiles OK, but always complains about these
missing braces...worths a patch ??


Does these problems need a patch or I should 
just forget them because of the "too smart" gcc 2.8.1 ?

Bye
-- Simon Andras sa027@ural2.hszk.bme.hu		L I N U X



