From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>
Subject: Re: linux-next: Tree for May 7 (avr32 build failure)
Date: Thu, 7 May 2015 18:33:57 -0700 [thread overview]
Message-ID: <20150508013357.GA26772@roeck-us.net> (raw)
In-Reply-To: <20150507164715.4eec2e84@canb.auug.org.au>
On Thu, May 07, 2015 at 04:47:15PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150506:
>
> The ext4 tree gained a build failure so I used the version from
> next-20150506.
>
> The vfs tree gained a conflict against the f2fs tree.
>
> The rcu tree gained conflicts against the tip tree.
>
> Non-merge commits (relative to Linus' tree): 2460
> 2454 files changed, 114321 insertions(+), 47105 deletions(-)
>
> ----------------------------------------------------------------------------
>
New build failure with avr32:atngw100mkii_evklcd101_defconfig (and several
other avr32 builds):
vsprintf.c:(.text+0x16a8): relocation truncated to fit:
R_AVR32_16N_PCREL against symbol `_ctype' defined in .text section in lib/lib.a(ctype.o)
This is with 4.2.4-atmel.1.1.3.avr32linux.1.
Possibly commit 'lib/vsprintf: add %pT format specifier' caused the object
file size to exceed some limit.
Guenter
next prev parent reply other threads:[~2015-05-08 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 6:47 linux-next: Tree for May 7 Stephen Rothwell
2015-05-08 1:33 ` Guenter Roeck [this message]
2015-05-08 1:54 ` linux-next: Tree for May 7 (openrisc, sparc qemu BUG due to 'hrtimer: Get rid of hrtimer softirq') Guenter Roeck
2015-05-08 6:36 ` Geert Uytterhoeven
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=20150508013357.GA26772@roeck-us.net \
--to=linux@roeck-us.net \
--cc=egtvedt@samfundet.no \
--cc=hskinnemoen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).