[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdVpWMboV1JGnOY7BtB1Qcm2=70Q079NPSGfut4Kjz34dQ@mail.gmail.com>
Date: Tue, 8 Jul 2014 21:24:49 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Nick Krause <xerofoify@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Compile issues with se7206_defconfig
On Tue, Jul 8, 2014 at 6:45 PM, Guenter Roeck <linux@...ck-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.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
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