linux-kernel - Re: Build/qemu test results for v4.18-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFx=UFQQi3c6MoA1jWaMf+-9vXC4pU56H_9dG3S8tbJdHA@mail.gmail.com>
Date:   Wed, 27 Jun 2018 08:27:47 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Will Deacon <will.deacon@....com>,
        Thomas Gleixner <tglx@...utronix.de>, mcroce@...hat.com,
        sbrivio@...hat.com, David Miller <davem@...emloft.net>
Subject: Re: Build/qemu test results for v4.18-rc2

On Tue, Jun 26, 2018 at 8:40 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> The problem on x86-64 cross-building to i386 is that the *compiler* is
> the same, but the flags are not, and the games the Makefile plays
> aren't sufficient. It plays with changing HOSTCC to CC in order to get
> he right target compiler, but since the difference between i386 and
> x86-64 is not the compiler but the "-m64" in the cflags, it doesn't
> actually do what it intended to do.
>
> We'll get it sorted, I think.

So right now the build fix is likely to be this:

    https://patchwork.ozlabs.org/patch/935246/

but note that it's literally just a build fix, and for a i386
cross-compile it embeds the wrong binary so it won't actually run
correctly. For this whole "test the concept" stage that's fine.

                Linus