[RFC][PATCH 0/1] toolchain conflict for userspace tools

Sascha Hauer s.hauer at pengutronix.de
Thu Apr 23 00:07:28 PDT 2015

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?


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 |

More information about the barebox mailing list