From: Guenter Roeck <linux@roeck-us.net>
To: Jonas Bonn <jonas@southpole.se>
Cc: linux@openrisc.net, linux-kernel@vger.kernel.org,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
Subject: Re: [PATCH] openrisc: Support both old (or32) and new (or1k) toolchain
Date: Thu, 18 Sep 2014 21:56:38 -0700 [thread overview]
Message-ID: <541BB786.1070700@roeck-us.net> (raw)
In-Reply-To: <1410210049-30800-1-git-send-email-linux@roeck-us.net>
ping ... comments / feedback anyone ?
Guenter
On 09/08/2014 02:00 PM, Guenter Roeck wrote:
> The output file format for openrisc has changed from "elf32-or32"
> to "elf32-or1k" when using the or1k instead of the older or32 toochain.
> Select the correct output format automatically to be able to compile
> the kernel with both toolchain variants.
>
> Cc: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> Candidate for -stable ?
>
> arch/openrisc/kernel/vmlinux.lds.S | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/arch/openrisc/kernel/vmlinux.lds.S b/arch/openrisc/kernel/vmlinux.lds.S
> index 2d69a85..1c5d21a 100644
> --- a/arch/openrisc/kernel/vmlinux.lds.S
> +++ b/arch/openrisc/kernel/vmlinux.lds.S
> @@ -30,7 +30,13 @@
> #include <asm/cache.h>
> #include <asm-generic/vmlinux.lds.h>
>
> -OUTPUT_FORMAT("elf32-or32", "elf32-or32", "elf32-or32")
> +#ifdef __OR1K__
> +#define __OUTPUT_FORMAT "elf32-or1k"
> +#else
> +#define __OUTPUT_FORMAT "elf32-or32"
> +#endif
> +
> +OUTPUT_FORMAT(__OUTPUT_FORMAT, __OUTPUT_FORMAT, __OUTPUT_FORMAT)
> jiffies = jiffies_64 + 4;
>
> SECTIONS
>
next prev parent reply other threads:[~2014-09-19 4:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 21:00 [PATCH] openrisc: Support both old (or32) and new (or1k) toolchain Guenter Roeck
2014-09-19 4:56 ` Guenter Roeck [this message]
2014-09-22 2:53 ` Stefan Kristiansson
2014-09-22 3:54 ` Guenter Roeck
2014-09-22 6:23 ` Jonas Bonn
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=541BB786.1070700@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jonas@southpole.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@openrisc.net \
--cc=stefan.kristiansson@saunalahti.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.