public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Nick Krause <xerofoify@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Compile issues with se7206_defconfig
Date: Tue, 8 Jul 2014 12:30:03 -0700	[thread overview]
Message-ID: <20140708193003.GA30984@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdVpWMboV1JGnOY7BtB1Qcm2=70Q079NPSGfut4Kjz34dQ@mail.gmail.com>

On Tue, Jul 08, 2014 at 09:24:49PM +0200, Geert Uytterhoeven wrote:
> On Tue, Jul 8, 2014 at 6:45 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> >> > net/built-in.o: In function `__sk_run_filter':
> >> > filter.c:(.text+0x3156c): undefined reference to `__fpscr_values'
> >> > filter.c:(.text+0x31760): undefined reference to `__fpscr_values'
> >> > filter.c:(.text+0x31c8c): undefined reference to `__fpscr_values'
> >> > filter.c:(.text+0x31f00): undefined reference to `__fpscr_values'
> >> > filter.c:(.text+0x323b0): undefined reference to `__fpscr_values'
> >>
> >> Toolchain issue: the compiler doesn't recognize the option to disable
> >> the FPU, so it isn't passed, cfr.
> >> www.spinics.net/lists/netdev/msg278300.html
> >
> > Seems that similar problems were fixed earlier without requiring a toolchain
> > change. What is different this time (besides the apparent difficulty to build a
> > new toolchain) ? Or am I missing something ?
> 
> sh4-linux-gcc doesn't recognize -m2a-nofpu, so that is not passed.
> It does recognize -m4a-nofpu, but when that's passed, it complains
> about opcode not valid for this cpu variant in inline asm/
> 
> Ah, it also recognizes -m4-nofpu. If I add that, se7206_defconfig builds.
> I assume a proper sh2a-linux toolchain will not recognize the -m4-nofpu,
> so it won't be passed due to $(call cc-option).
> 
> Does this sound like an acceptable solution? If yes, I'll send a patch.
> 
Sounds good to me.

Guenter

  reply	other threads:[~2014-07-08 19:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  2:56 Compile issues with se7206_defconfig Nick Krause
2014-07-08  4:03 ` Guenter Roeck
2014-07-08  4:16   ` Fwd: " Nick Krause
2014-07-08  8:08   ` Geert Uytterhoeven
2014-07-08 16:45     ` Guenter Roeck
2014-07-08 19:24       ` Geert Uytterhoeven
2014-07-08 19:30         ` Guenter Roeck [this message]
2014-07-09  1:09           ` Fwd: " Nick Krause

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=20140708193003.GA30984@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xerofoify@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