[U-Boot] [PATCH 2/2] x86: Allow 32-bit toolchain to compile 64-bit U-Boot

[Andy Shevchenko]

On Sun, Jul 23, 2017 at 1:26 PM, Bin Meng <bmeng.cn at gmail.com> wrote:
> On Sun, Jul 23, 2017 at 6:07 PM, Andy Shevchenko
> <andy.shevchenko at gmail.com> wrote:
>> On Sun, Jul 23, 2017 at 1:05 PM, Bin Meng <bmeng.cn at gmail.com> wrote:
>>> On Sun, Jul 23, 2017 at 6:01 PM, Andy Shevchenko
>>> <andy.shevchenko at gmail.com> wrote:
>>>> On Sun, Jul 23, 2017 at 12:37 PM, Bin Meng <bmeng.cn at gmail.com> wrote:
>>
>>>> The subject is a bit cofusing. As I read (and as I understand) we need
>>>> to have 64-bit toolchain available (multilib package and so on).
>>>> Basically what you do is "enforcing 64-bit toolchain to be used". Right?
>>>>
>>>
>>> Yes, multilib package is required for 64-bit toolchain to build 32-bit
>>> U-Boot. Maybe the confusion comes from what we call 32-bit/64-bit
>>> toolchains. Or maybe we should call it pre-configured toolchain for
>>> building 32-bit/64-bit codes? The issue is when using kernel.org
>>> i386-linux-gcc to build qemu-x86_64_defconfig (64-bit U-Boot), the
>>> issue is seen. It's because the i386-linux-gcc is pre-configured with
>>> '-m32' which is for building 32-bit codes.
>>
>> My point is that subject (and maybe commit message) should be massaged
>> a bit to avoid confusion.
>>
>
> Sure. Reword it as "Allow toolchains that are pre-configured to build
> 32-bit codes to compile 64-bit U-Boot"?

Hmm... The flag you are adding does enforce or allow?
So, if -m64 will still allow to compile 32-bit code, then it's
allowing, otherwise it's enforcing.
Or I miss something?

-- 
With Best Regards,
Andy Shevchenko