mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Stefan Müller-Klieser" <s.mueller-klieser@phytec.de>
To: barebox@lists.infradead.org
Subject: [RFC][PATCH 0/1] toolchain conflict for userspace tools
Date: Mon, 20 Apr 2015 15:10:26 +0200	[thread overview]
Message-ID: <1429535427-16243-1-git-send-email-s.mueller-klieser@phytec.de> (raw)

Dear bareboxers,

I ask for help with a problem I am facing. If the buildsystem compiles
gcc with multilib support, gcc can support the float abi callconvention
to be generated dynamically, as yocto starting with v1.7 does. So we
don't have the usual default "--with-float=hard", but gcc sets the
mfloat-abi at runtime for every package.
This seems to work well in general, e.g. modern autotools and the
Kconfig infrastructure for kernel and barebox. However this fails
for the target tools in the barebox script folder. They need to have
the --with-float=hard set, or they will try to compile as softfloat.
I think the general solution would be to give the user the possibility
to redefine the CC for the userspace tools, as this is very specific
to the environment where the barebox gets compiled.
But maybe someone with a deeper knowledge of the Makefile infrastructure
can recommend a better long term solution.

Regards,
Stefan

Stefan Müller-Klieser (1):
  scripts/Makefile: add TARGETCC

 scripts/Makefile | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

-- 
1.9.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2015-04-20 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 13:10 Stefan Müller-Klieser [this message]
2015-04-20 13:10 ` [RFC][PATCH 1/1] scripts/Makefile: add TARGETCC Stefan Müller-Klieser
2015-04-23  7:07 ` [RFC][PATCH 0/1] toolchain conflict for userspace tools Sascha Hauer
2015-04-23  8:49   ` Antwort: " PHYTEC Mailinglists

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=1429535427-16243-1-git-send-email-s.mueller-klieser@phytec.de \
    --to=s.mueller-klieser@phytec.de \
    --cc=barebox@lists.infradead.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