[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150512200743.GA6155@roeck-us.net>
Date: Tue, 12 May 2015 13:07:43 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: anees <rean12is@...il.com>
Cc: Jonas Bonn <jonas@...thpole.se>, linux@...ts.openrisc.net,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] OpenRISC: Fix kernel build problem on OpenRISC
On Tue, May 12, 2015 at 03:45:21PM +0200, anees wrote:
> Kernel build fails with error "target elf32-or32 not found"
> This is due to the change in OpenRISC compiler prefix from "or12"
> to "or1k". Add config options that set architecture output format
> default to "or1k" but also allow user to select older prefix.
>
> Tested with gcc version 4.9.1 uclibc
>
> Signed-off-by: anees <rean12is@...il.com>
> ---
> arch/openrisc/Kconfig | 12 ++++++++++++
> arch/openrisc/kernel/vmlinux.lds.S | 6 +++---
> 2 files changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/arch/openrisc/Kconfig b/arch/openrisc/Kconfig
> index e5a693b..c7fe7c8 100644
> --- a/arch/openrisc/Kconfig
> +++ b/arch/openrisc/Kconfig
> @@ -75,6 +75,18 @@ config OPENRISC_BUILTIN_DTB
> string "Builtin DTB"
> default ""
>
> +config OUTPUT_FORMAT_TYPE
> + string "Architecture output format type"
> + default "or1k"
> + help
> + Write "or12" if building kernel against an older toolchain
> + else leave the default (or1k)
> +
That means I'll have to use different toolchains for different kernel
versions, or hand-edit default configuration files to able to work
with the same toolchain. Both is, from a testing perspective,
quite annoying.
Maybe I should simply stop testing older kernels for openrisc
after this patch has been merged; that would be much easier.
Jonas, is that ok with you ?
Side note: I didn't drop it from Cc:, but the openrisc.net domain
name expired and appears to be for sale.
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/
Powered by blists - more mailing lists