All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roberto J. Dohnert" <rjdohnert@gmail.com>
To: Nick Krause <xerofoify@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Arm Build Failing
Date: Sun, 20 Jul 2014 00:10:35 -0400	[thread overview]
Message-ID: <53CB413B.4090409@gmail.com> (raw)
In-Reply-To: <CAPDOMVh9knmN1y-LZWvsAKcrKKPQsi0+skNG1D0aQgP+hg3ssQ@mail.gmail.com>

It looks like its trying to invoke the native (x86) compiler, but 
passing it options that only make sense to an ARM compiler.

Cheers

Roberto J. Dohnert
Roberto J. Dohnert
Lead Developer
Black Lab Software Inc.
PO Box 698
Franklinton NC 27525
http://www.pc-opensystems.com
http://www.blacklablinux.org

On 07/20/2014 12:03 AM, Nick Krause wrote:
> arm-linux-gnueabihf-gcc: error: unrecognized command line option ‘-m64’
> arm-linux-gnueabihf-gcc: error: unrecognized command line option ‘-mno-mmx’
> arm-linux-gnueabihf-gcc: error: unrecognized command line option ‘-mno-sse’
> arm-linux-gnueabihf-gcc: error: unrecognized command line option ‘-mno-red-zone’
> arm-linux-gnueabihf-gcc: error: unrecognized command line option
> ‘-mcmodel=kernel’
> This happens every time I try to build new arch code this week. Is there a easy
> fix for this?
> Cheers Nick
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


  reply	other threads:[~2014-07-20  4:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-20  4:03 Arm Build Failing Nick Krause
2014-07-20  4:10 ` Roberto J. Dohnert [this message]
2014-07-20  4:15   ` 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=53CB413B.4090409@gmail.com \
    --to=rjdohnert@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.