linux-kernel - Re: avr32 build failures in linux-next

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: <20160206115722.GA32647@samfundet.no>
Date:	Sat, 6 Feb 2016 12:57:22 +0100
From:	Hans-Christian Noren Egtvedt <egtvedt@...fundet.no>
To:	Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:	Guenter Roeck <linux@...ck-us.net>,
	Haavard Skinnemoen <hskinnemoen@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: avr32 build failures in linux-next

Around Fri 05 Feb 2016 22:02:12 +0530 or thereabout, Sudip Mukherjee wrote:
> On Friday 05 February 2016 09:32 PM, Guenter Roeck wrote:
>>Hi,
>>
>>I am getting persistent build failures with av32 in linux-next.
> 
> me too.

linux-next is Torvalds master branch?

>>Example for avr32:defconfig:
>>
>>fs/built-in.o: In function `anon_inode_getfile':
>>(.text+0x2ae90): relocation truncated to fit: R_AVR32_21S against
>>`.text'+296c0
>>
>>All builds but avr32:allnoconfig fail with such truncated relocations.

Weirdly I do not get this when I build torvalds/master with allnoconfig.

The avr32 kernel was never very fond of CONFIG_CC_OPTIMIZE_FOR_SIZE=n, it
was always built with CONFIG_CC_OPTIMIZE_FOR_SIZE=y for actual usage.

>>Toolchain used is the old gcc 4.2.4 toolchain from kernel.org. I have been
>>unable to find or build newer versions of gcc for avr32.
>>
>>Does anyone know if a more recent toolchain for avr32 is available ?
> 
> https://sourceware.org/ml/crossgcc/2015-10/msg00050.html
> says avr32 has been depreciated.

Last release of avr32-linux GCC was the 4.2.4 patches in Buildroot for AVR32.

Atmel never upstreamed the AVR32 patches for GCC.

>>Another question is if the avr32 kernel still supported, or if I should
>>just stop trying to build test it. Any thoughts ?
> 
> I have already stopped building it.

I build the kernel and try to fix small issues here and there.

If it is too unstable for you in the test bench, feel free to remove it.

-- 
Best regards,
Hans-Christian Egtvedt