From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jim Davis <jim.epost@gmail.com>
Cc: linux-next@vger.kernel.org
Subject: Re: Problem building i386_defconfig with next-20130920
Date: Mon, 23 Sep 2013 10:20:50 +1000 [thread overview]
Message-ID: <20130923102050.bb0859b9b44d834a44facae1@canb.auug.org.au> (raw)
In-Reply-To: <CA+r1ZhjS+97EhQYXYSg-U9-SCrymoDmMu9JceBVyj7Wt0N3vgQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
Hi Jim,
On Fri, 20 Sep 2013 10:07:42 -0700 Jim Davis <jim.epost@gmail.com> wrote:
>
> Trying to build a x86 kernel is failing with
>
> kernel/bounds.c:1:0: error: CPU you selected does not support x86-64
> instruction set
> /*
> ^
> kernel/bounds.c:1:0: warning: -mregparm is ignored in 64-bit mode
> [enabled by default]
> make[1]: *** [kernel/bounds.s] Error 1
> make: *** [prepare0] Error 2
>
> Here's the steps I've gone through in detail, just in case it's pilot error :/
>
> jim@krebstar:~/linux$ make distclean
> CLEAN arch/x86/tools
> CLEAN .tmp_versions
> CLEAN scripts/basic
> CLEAN scripts/kconfig
> CLEAN include/config include/generated arch/x86/include/generated
> CLEAN .config include/generated/uapi/linux/version.h
> jim@krebstar:~/linux$ git clean -fdx
> jim@krebstar:~/linux$ git remote -v
> linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (fetch)
> linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (push)
> origin git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> (fetch)
> origin git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> (push)
> jim@krebstar:~/linux$ git remote update
> Fetching origin
> Fetching linux-next
> jim@krebstar:~/linux$ git describe
> v3.12-rc1
> jim@krebstar:~/linux$ git tag | grep '^next-' | tail -1
> next-20130920
> jim@krebstar:~/linux$ make i386_defconfig
So, you are building v3.12-rc1, not linux-next ... i386_defconfig is one
of the builds I do before releasing linux-next (but not on just Linus'
tree) and it did not fail for me on Friday (gcc 4.6.3 if it matters), so
maybe this is fixed by something after -rc1 or in linux-next.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-09-23 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 17:07 Problem building i386_defconfig with next-20130920 Jim Davis
2013-09-23 0:20 ` Stephen Rothwell [this message]
2013-09-23 2:20 ` Jim Davis
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=20130923102050.bb0859b9b44d834a44facae1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jim.epost@gmail.com \
--cc=linux-next@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).