From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: mikael.starvik@axis.com, dev-etrax@axis.com,
linux-kernel@vger.kernel.org
Subject: Re: cris/arch-v10/lib/string.c compile error
Date: Mon, 18 Feb 2008 09:39:12 +0100 [thread overview]
Message-ID: <20080218083912.GK11007@axis.com> (raw)
In-Reply-To: <20080216095739.GE9962@cs181133002.pp.htv.fi>
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@axis.com
next prev parent reply other threads:[~2008-02-18 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 9:57 cris/arch-v10/lib/string.c compile error Adrian Bunk
2008-02-18 8:39 ` Jesper Nilsson [this message]
2008-02-22 16:19 ` [PATCH] CRIS: Import string.c (memcpy) from newlib: fixes compile error with gcc 4 Jesper Nilsson
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=20080218083912.GK11007@axis.com \
--to=jesper.nilsson@axis.com \
--cc=bunk@kernel.org \
--cc=dev-etrax@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.com \
/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.