[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140708164525.GB12935@roeck-us.net>
Date: Tue, 8 Jul 2014 09:45:25 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
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 08, 2014 at 10:08:46AM +0200, Geert Uytterhoeven wrote:
> On Tue, Jul 8, 2014 at 6:03 AM, Guenter Roeck <linux@...ck-us.net> wrote:
> > On 07/07/2014 07:56 PM, Nick Krause wrote:
> >> There seems to me a build issue with this config. I will paste my logs
> >> for this build below this message.
> >> Cheers Nick
> >> scripts/mod/empty.c:1:0: error: cannot use atomic model soft-imask in user
> >> mode
> >> /* empty file to figure out endianness / word size */
> >> ^
> >> make[2]: *** [scripts/mod/empty.o] Error 1
> >> make[2]: *** Waiting for unfinished jobs....
> >> make[1]: *** [scripts/mod] Error 2
> >> make[1]: *** Waiting for unfinished jobs....
> >> CHK include/generated/utsrelease.h
> >> UPD include/generated/utsrelease.h
> >> Generating include/generated/machtypes.h
> >> CC kernel/bounds.s
> >> kernel/bounds.c:1:0: error: cannot use atomic model soft-imask in user
> >> mode
> >> /*
> >> ^
> >> make[1]: *** [kernel/bounds.s] Error 1
> >> make: *** [prepare0] Error 2
> >> make: *** Waiting for unfinished jobs....
> >> make: *** [scripts] Error 2
> >
> > What kernel version ? I see a build failure in mainline, but it is
> > different.
>
> Indeed.
>
> > 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 ?
Thanks,
Guenter
--
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