From: Guenter Roeck <linux@roeck-us.net>
To: Nick Krause <xerofoify@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Compile issues with se7206_defconfig
Date: Mon, 07 Jul 2014 21:03:27 -0700 [thread overview]
Message-ID: <53BB6D8F.70900@roeck-us.net> (raw)
In-Reply-To: <CAPDOMVid3nbw0-3n_5d8QF_c5uOosWyYRPtqW29ZUB9Ziz7F+Q@mail.gmail.com>
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.
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'
Guenter
next prev parent reply other threads:[~2014-07-08 4:03 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 [this message]
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
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=53BB6D8F.70900@roeck-us.net \
--to=linux@roeck-us.net \
--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