Fwd: Compile issues with se7206_defconfig

From: Nick Krause
Date: Tue Jul 08 2014 - 21:10:00 EST

Guenter Roeck wrote on Tue, Jul 8, 2014 at 3:30 PM
Subject: Re: Compile issues with se7206_defconfig
To: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
Cc: Nick Krause <xerofoify@xxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx"

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@xxxxxxxxxxxx> 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.


Please send the patch to the maintainers of this and cc me so I can test it to
see if it works.
Cheers Nick
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/