linux-kernel - Re: building in 32bit chroot on x86

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+55aFyD0OMV1eoc9wh_hLcnRhHq2FwJf4EZcORmHPNxTRSX9Q@mail.gmail.com>
Date:   Tue, 5 Jun 2018 11:38:32 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     tmb@...eia.org
Cc:     Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: building in 32bit chroot on x86_64 host broken

On Tue, Jun 5, 2018 at 11:23 AM Thomas Backlund <tmb@...eia.org> wrote:
>   #
> -# CONFIG_64BIT is not set
>
> So something _does_ strip away the needed config bit

Why do you need it?

I get

  CONFIG_X86_32=y
  CONFIG_X86=y

and CONFIG_64BIT never gets set.

It is true that I don't get the

  # CONFIG_64BIT is not set

line, but why do you care?

            Linus