public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Guenter Roeck <linux@roeck-us.net>
Cc: anees <rean12is@gmail.com>, Jonas Bonn <jonas@southpole.se>,
	linux@lists.openrisc.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] OpenRISC: Fix kernel build problem on OpenRISC
Date: Wed, 13 May 2015 11:58:22 +0200	[thread overview]
Message-ID: <1431511102.2398.187.camel@x220> (raw)
In-Reply-To: <20150512200743.GA6155@roeck-us.net>

On Tue, 2015-05-12 at 13:07 -0700, Guenter Roeck wrote:
> 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@gmail.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.

Also quite annoying would be
    $ grep OUTPUT_FORMAT .config 
    CONFIG_OUTPUT_FORMAT_TYPE="typo"

(Note the missing CONFIG_OUTPUT_FORMAT= line.)

What might be less annoying would be something (completely untested)
like:
    choice
	prompt "Architecture output format type"
	default OUTPUT_FORMAT_OR1K
	help
	  Choose "or12" if building kernel against an older toolchain
	  else leave the default "or1k".

    config OUTPUT_FORMAT_OR1K
	bool "or1k"

    config OUTPUT_FORMAT_OR12
	bool "or12"

    enchoice

    config OUTPUT_FORMAT
	string
	default "elf32-or1k" if OUTPUT_FORMAT_OR1K
	default "elf32-or12" if OUTPUT_FORMAT_OR12

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

Would testing be easier if you'd be provided with two defconfig files?
Ie, one for "elf32-or1k" and "elf32-or12".

(Note that "elf32-or12" smells like a typo to me. Shouldn't that be
"elf32-or32"? If not, where does "elf32-or32" fir in this story?)

> Side note: I didn't drop it from Cc:, but the openrisc.net domain
> name expired and appears to be for sale.

That's ominous.

Thanks,


Paul Bolle


  reply	other threads:[~2015-05-13  9:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 13:45 [PATCH 1/1] OpenRISC: Fix kernel build problem on OpenRISC anees
2015-05-12 20:07 ` Guenter Roeck
2015-05-13  9:58   ` Paul Bolle [this message]
2015-05-13 13:20     ` Guenter Roeck
2015-05-13 13:33       ` Paul Bolle
2015-05-13 13:41         ` Jonas Bonn
2015-05-13 14:28           ` Paul Bolle
2015-05-13 14:44             ` Geert Uytterhoeven
2015-05-13 16:49               ` Guenter Roeck
2015-05-13 16:57           ` Guenter Roeck
2015-06-10 20:21           ` Guenter Roeck
2015-06-11  9:52             ` Paul Bolle
2015-06-11 15:42               ` Guenter Roeck
2015-05-13 13:45         ` 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=1431511102.2398.187.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=jonas@southpole.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@lists.openrisc.net \
    --cc=linux@roeck-us.net \
    --cc=rean12is@gmail.com \
    /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