linux-kernel - Re: linux-next: Tree for May 7 (avr32 build failure)

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]

Message-ID: <20150508013357.GA26772@roeck-us.net>
Date:	Thu, 7 May 2015 18:33:57 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Haavard Skinnemoen <hskinnemoen@...il.com>,
	Hans-Christian Egtvedt <egtvedt@...fundet.no>
Subject: Re: linux-next: Tree for May 7 (avr32 build failure)

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
--
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/