Re: [PATCH, ARM] ARM / linux float ABI discrepancy

[Christophe Lyon <christophe dot lyon at st dot com>]

> The floating-point ABI issue isn't as simple as your patch would suggest,
> because the default can be controlled with the --with-float configure
> option.
Indeed, I did not take this configure flag into account.

I just meant to make the default more coherent.

>  In addition, there are the alternative -mfloat-abi=* spellings,
> so you need either to add MULTILIB_MATCHES for those to work properly, or
> to make -mhard-float and -msoft-float really be aliases for the canonical
> -mfloat-abi= versions using the .opt alias machinery (and then adjust all
> the t-* files using those options accordingly).  (Once my multilib
> selection changes are finished, it wouldn't actually be necessary to mark
> the options as aliases to get the multilib selection working correctly.)

I didn't mention same for the sake of clarity/shortness in my email.

My patch is just here for the casual "user" who wants to add some 
multilibs, without adding -with-float= and who doesn't understand why he 
gets the wrong lib variants generated.


As of handling -with-float= it does seem to require some work in the 
initialization phase, so as to properly override the multilib_defauts 
before they are taken into account.

Christophe.