mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: PHYTEC Mailinglists <mailinglists@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org,
	barebox <barebox-bounces@lists.infradead.org>
Subject: Antwort: Re: [RFC][PATCH 0/1] toolchain conflict for userspace tools
Date: Thu, 23 Apr 2015 10:49:08 +0200	[thread overview]
Message-ID: <OFFA5BCBD9.D4B2A4C3-ONC1257E30.002F0F9B-C1257E30.00307257@phytec.de> (raw)
In-Reply-To: <20150423070728.GK6325@pengutronix.de>

Hi Sascha,

"barebox" <barebox-bounces@lists.infradead.org> wrote on 04/23/2015 
09:07:28 AM:

> Von: Sascha Hauer <s.hauer@pengutronix.de>
> An: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
> Kopie: barebox@lists.infradead.org
> Datum: 04/23/2015 09:08 AM
> Betreff: Re: [RFC][PATCH 0/1] toolchain conflict for userspace tools
> Gesendet von: "barebox" <barebox-bounces@lists.infradead.org>
> 
> Hi Stefan,
> 
> On Mon, Apr 20, 2015 at 03:10:26PM +0200, Stefan Müller-Klieser wrote:
> > 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.
> 
> We discussed this here and came to the conclusion that not CC should be
> exchanged but rather we should have userspace specific CFLAGS. The
> currently used CFLAGS contains stuff not suitable for userspace anyway.
> Would introducing CFLAGS_USERSPACE work for you?

Sure, that sounds intuitive. Thanks!
Stefan

> 
> Sascha
> 
> -- 
> Pengutronix e.K.                           | |
> Industrial Linux Solutions                 | http://www.pengutronix.de/ 
|
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 
|
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox


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

      reply	other threads:[~2015-04-23  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 13:10 Stefan Müller-Klieser
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   ` PHYTEC Mailinglists [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=OFFA5BCBD9.D4B2A4C3-ONC1257E30.002F0F9B-C1257E30.00307257@phytec.de \
    --to=mailinglists@phytec.de \
    --cc=barebox-bounces@lists.infradead.org \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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