linux-kernel - Re: cris/arch-v10/lib/string.c compile error

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 18 Feb 2008 09:39:12 +0100
From:	Jesper Nilsson <jesper.nilsson@...s.com>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	mikael.starvik@...s.com, dev-etrax@...s.com,
	linux-kernel@...r.kernel.org
Subject: Re: cris/arch-v10/lib/string.c compile error

On Sat, Feb 16, 2008 at 11:57:39AM +0200, Adrian Bunk wrote:
> Next file, same problem:
> <--  snip  -->
> 
> ...
>   CC      arch/cris/arch-v10/lib/string.o
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/cris/arch-v10/lib/string.c:138: error: lvalue required as increment operand
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/cris/arch-v10/lib/string.c:138: error: lvalue required as increment operand
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/cris/arch-v10/lib/string.c:139: error: lvalue required as increment operand
> ...
> 
> <--  snip  -->
> 
> And looking at Jan Dittmer's page [1] that problem is not limited to the 
> SVN head gcc I'm using since he's running into the same error with
> gcc 4.0.4.
> 
> Can you try compiling a cris kernel with a gcc 4 based toolchain?

Yes, I'll set that up and squash the compile errors in one go.

Thanks again for the heads up.

> cu
> Adrian
> 
> [1] http://l4x.org/k/?d=38964

/^JN - Jesper Nilsson
--
               Jesper Nilsson -- jesper.nilsson@...s.com
--
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/