mdadm 3.2.1 doesn't compile with gcc 4.6.0

mdadm 3.2.1 doesn't compile with gcc 4.6.0

[Tobias Powalowski]

[-- Attachment #1: Type: text/plain, Size: 302 bytes --]

Hi guys,
mdadm.c:106:6: error: variable 'auto_update_home' set but not used [-
Werror=unused-but-set-variable]


any help would be much appreciated.
thanks
greetings
tpowa
-- 
Tobias Powalowski
Archlinux Developer & Package Maintainer (tpowa)
http://www.archlinux.org
tpowa@archlinux.org

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: mdadm 3.2.1 doesn't compile with gcc 4.6.0

[NeilBrown]

On Tue, 26 Apr 2011 09:00:17 +0200 Tobias Powalowski <t.powa@gmx.de> wrote:

> Hi guys,
> mdadm.c:106:6: error: variable 'auto_update_home' set but not used [-
> Werror=unused-but-set-variable]
> 
> 
> any help would be much appreciated.
> thanks
> greetings
> tpowa

Thanks for the report.

If you build with
  make CWFLAGS=

it will not treat warnings as errors and it should successfully compile.

I have committed a fix:

http://neil.brown.name/git?p=mdadm;a=commitdiff;h=7e90264df5060cd308ce56206ec7dfa29e2aa041

Thanks,
NeilBrown

RE: mdadm 3.2.1 doesn't compile with gcc 4.6.0

[Mike Viau]

> On Tue, 26 Apr 2011 09:00:17 +0200  wrote:
>
> Hi guys,
> mdadm.c:106:6: error: variable 'auto_update_home' set but not used [-
> Werror=unused-but-set-variable]
>

I have not grepped the source code for other instances of 'auto_update_home' so it may or may not actually be used.

If its not ever used you can try commenting out the declaration of 'auto_update_home' and then re-compile?

Lastly, you could drop the -Werror=unused-but-set-variable option, as it is turning the warning (which may happen and still compile) into an error (which when happens, will not compile).



-M