From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: avr32 build failures in linux-next
Date: Fri, 05 Feb 2016 22:02:12 +0530 [thread overview]
Message-ID: <56B4CE8C.8040307@gmail.com> (raw)
In-Reply-To: <56B4C799.5070401@roeck-us.net>
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.
>
> 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.
>
> 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.
>
> 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.
Regards
Sudip
next prev parent reply other threads:[~2016-02-05 16:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 16:02 avr32 build failures in linux-next Guenter Roeck
2016-02-05 16:32 ` Sudip Mukherjee [this message]
2016-02-06 11:57 ` Hans-Christian Noren Egtvedt
2016-02-06 14:01 ` Måns Rullgård
2016-02-06 16:19 ` Guenter Roeck
2016-02-06 17:28 ` Måns Rullgård
2016-02-08 16:06 ` Andy Shevchenko
2016-02-09 4:02 ` Guenter Roeck
2016-03-09 19:30 ` Andy Shevchenko
2016-03-09 19:50 ` Måns Rullgård
2016-03-10 4:55 ` Sudip Mukherjee
2016-03-10 13:38 ` Måns Rullgård
2016-03-10 13:53 ` Andy Shevchenko
2016-03-10 14:24 ` Måns Rullgård
2016-03-10 14:29 ` One Thousand Gnomes
2016-03-10 14:31 ` Måns Rullgård
2016-03-10 15:10 ` Andy Shevchenko
2016-02-06 15:50 ` Guenter Roeck
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=56B4CE8C.8040307@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=egtvedt@samfundet.no \
--cc=hskinnemoen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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