linux-kernel - Re: Build error on arm in crypto/cast6.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200909161628.33631.elendil@planet.nl>
Date:	Wed, 16 Sep 2009 16:28:32 +0200
From:	Frans Pop <elendil@...net.nl>
To:	linux-kernel@...r.kernel.org
Cc:	linux-crypto@...r.kernel.org,
	Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: Build error on arm in crypto/cast6.c

On Wednesday 16 September 2009, Frans Pop wrote:
> $ git describe master
> v2.6.31-4547-g0cb583f
>
> gcc version 4.3.2
>
> crypto/cast6.c:372:39: error: macro "W" passed 2 arguments, but takes just 1
> crypto/cast6.c:372: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or  ‘__attribute__’ before ‘{’ token
> crypto/cast6.c:413:16: error: macro "W" passed 2 arguments, but takes just 1
> crypto/cast6.c: In function ‘cast6_setkey’:
> crypto/cast6.c:413: error: ‘W’ undeclared (first use in this function)
> crypto/cast6.c:413: error: (Each undeclared identifier is reported only once
> crypto/cast6.c:413: error: for each function it appears in.) 
> crypto/cast6.c:414:20: error: macro "W" passed 2 arguments, but takes just 1
>
> Strange thing is that this file does not look to have changed.
>
> Maybe it's a result of enabling the new config option
> CRYPTO_DEV_MV_CESA?

Seems unrelated. Kernel compiles fine with CRYPTO_DEV_MV_CESA set and
CRYPTO_CAST6 unset. I did have CRYPTO_CAST6 set to m for .31 kernel
builds without seeing any problems.

As I'm running Debian stable there've no major changes (if any) in the
build environment.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/