Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] EABIhf: breaks kernel build
Date: Fri, 19 Jul 2013 22:07:34 +0200	[thread overview]
Message-ID: <87fvvauxdl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20130719161733.GC3751@free.fr> (Yann E. MORIN's message of "Fri,  19 Jul 2013 18:17:33 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 Yann> Thomas, All,
 Yann> Since the ARM EABIhf stuff was committed, the Linux kernel build is
 Yann> broken, and fails with this message:
 Yann>     armv6-rpi36-linux-gnueabi-gcc: error: -mfloat-abi=soft and
 Yann>     -mfloat-abi=hard may not be used together

 Yann> This is because -mfloat-abi=hard is hard-coded in the wrapper, but the
 Yann> kernel wants to pass -msoft-float.

 Yann> See attach exerpt of my build log (with a instrumented ext-ttolchain
 Yann> wrapper). Notice argv[6] and argv[41]:

 Yann>     argv[6]='-mfloat-abi=hard'
 Yann>     argv[41]='-msoft-float'

 Yann> argv[6] is out hard-coded float ABI option, while argv[41] is passed by
 Yann> the kernel.

 Yann> I don't know how to solve this.

 Yann> The trivial and immediate idea would be to have a black-list of
 Yann> arguments and exclude the ones we pass that conflict with the ones
 Yann> passed on the command line, but this will be *very* complex and always
 Yann> incomplete.

Yeah, but I think it's the best solution still.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2013-07-19 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 16:17 [Buildroot] EABIhf: breaks kernel build Yann E. MORIN
2013-07-19 18:11 ` Yann E. MORIN
2013-07-19 20:07 ` Peter Korsgaard [this message]

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=87fvvauxdl.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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