Re: [PATCH 5/6] gcc-cross: Pass EXTRA_OECONF_GCC_FLOAT to configure

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Wed, 2015-05-06 at 23:47 -0700, Khem Raj wrote:
> > On May 6, 2015, at 1:11 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > 
> > But we build gcc-cross-arm once. This will cause it to rebuild depending
> > on which machine you target? Worse, it likely will now do this for all
> > architectures, not just arm.
> 
> only when float ABI changes which may be common across a subset of architectures.
> 
> although, I think its going to become a severe usability issue. Look
> at the archives there are so many issues reported in various forums which end up exactly to this problem, since users expect
> that once they installed the SDK it works out of box for the default architecture which is not
> the case. It just seems wrong build optimization to make it common per arch it if we can’t have user expectations met.

To be honest I haven't seen that many reports of the problem. We do ship
an environment file and in that file we have the options gcc needs to
work, the sysroot, the other cflags and the float abi. Unless we go back
to a setup of hardcoding the cflags into gcc and have a gcc per set of
cflags, this isn't going to work since it solves part of the problem but
not all of it.

Our other alternative is to wrap gcc with a script (preferred in PATH)
which ensures the right cflags are present. I'd obviously prefer not to
do that but it is an option if we believe people can't cope with the
environment script.

Cheers,

Richard