From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: "David S. Miller" <davem@davemloft.net>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH v2] avr32: Fix build failure conflicting types for 'sys_execve'
Date: Mon, 13 Dec 2010 18:27:46 +0100 [thread overview]
Message-ID: <1292261266.18008.72.camel@hcegtvedt> (raw)
In-Reply-To: <201012131812.03487.PeterHuewe@gmx.de>
On Mon, 2010-12-13 at 18:12 +0100, Peter Hüwe wrote:
> Am Montag 13 Dezember 2010, 09:12:53 schrieb Hans-Christian Egtvedt:
> > > (but it still failed for quite a while longer due to other issues ;)
> > What other issues?
>
> There's a linker error at the end:
>
> CC init/version.o
> LD init/built-in.o
> LD vmlinux
> lib/lib.a(vsprintf.o): In function `resource_string':
> vsprintf.c:(.text+0x149e): relocation truncated to fit: R_AVR32_9UW_PCREL
> against `.text'+16a8
> vsprintf.c:(.text+0x14ae): relocation truncated to fit: R_AVR32_9UW_PCREL
> against `.text'+16ac
>
> which seems to exist since May 26th in Linus' tree.
> See
> http://kisskb.ellerman.id.au/kisskb/buildresult/2631302/
> http://kisskb.ellerman.id.au/kisskb/target/664/
> for more details.
>
> Unfortunately I wasn't able to locate the offending commit using git bisect :/
Hmm, I haven't seen that, which toolchain and which configuration do you
use?
--
Hans-Christian Egtvedt
next prev parent reply other threads:[~2010-12-13 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 23:19 [PATCH] " Peter Huewe
2010-12-09 7:54 ` Hans-Christian Egtvedt
2010-12-09 18:21 ` [stable] " Greg KH
2010-12-09 18:42 ` Peter Hüwe
2010-12-09 19:13 ` Greg KH
2010-12-09 21:15 ` [PATCH v2] " Peter Huewe
2010-12-10 10:25 ` Hans-Christian Egtvedt
2010-12-12 19:37 ` Peter Hüwe
2010-12-13 8:12 ` Hans-Christian Egtvedt
2010-12-13 17:12 ` Peter Hüwe
2010-12-13 17:27 ` Hans-Christian Egtvedt [this message]
2010-12-10 15:58 ` [PATCH] " David Howells
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=1292261266.18008.72.camel@hcegtvedt \
--to=hans-christian.egtvedt@atmel.com \
--cc=PeterHuewe@gmx.de \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®