From: Thomas Backlund <tmb@mageia.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: building in 32bit chroot on x86_64 host broken - IGNORE
Date: Tue, 5 Jun 2018 21:11:01 +0259 [thread overview]
Message-ID: <48aa249f-22e8-924c-120c-8384eff9efb4@mageia.org> (raw)
In-Reply-To: <8f46ed9a-85c0-8df4-2d1e-d268cbc9d0e9@mageia.org>
Den 2018-06-05 kl. 20:52, skrev Thomas Backlund:
>
> I have a 32bit x86 and a 64bit x86_64 install on the system.
>
> With linux source up to 4.16.x I could do:
>
> setarch i686 (or use command linux32)
> chroot /path/to/32bit/
> (/dev, /proc, /sys, /run is bind mounted in the chroot)
>
> Then I could build a 32bit kernel in the chroot without booting the
> 32bit system...
>
> (host is running a 4.14 longterm kernel)
>
> but building from 4.17 source in the chroot I get:
>
>
> $ uname -m
> i686
> $ make oldconfig
> scripts/kconfig/conf --oldconfig Kconfig
> *
> * Restart config...
> *
> *
> * Linux/x86 4.17.0 Kernel Configuration
> *
> 64-bit kernel (64BIT) [Y/n/?] (NEW)
>
>
>
>
> So it does not pick up 32bit anymore ...
>
> Is this intentional ? If so, why ? If not, how can I fix it ?
>
Never mind...
For some reason I seem to have lost this in the .config update to 4.17:
# CONFIG_64BIT is not set
Re-adding it restores proper behaviour...
Sorry for the noise...
--
Thomas
next prev parent reply other threads:[~2018-06-05 18:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 21:58 Linux 4.17 Linus Torvalds
2018-06-05 17:53 ` building in 32bit chroot on x86_64 host broken (was: Linux 4.17) Thomas Backlund
2018-06-05 18:11 ` Linus Torvalds
2018-06-05 18:24 ` building in 32bit chroot on x86_64 host broken Thomas Backlund
2018-06-05 18:38 ` Linus Torvalds
2018-06-05 18:51 ` Thomas Backlund
2018-06-05 19:13 ` Linus Torvalds
2018-06-05 19:36 ` Thomas Backlund
2018-06-06 1:37 ` Masahiro Yamada
2018-06-06 1:54 ` Linus Torvalds
2018-06-06 2:19 ` Linus Torvalds
2018-06-06 3:31 ` Masahiro Yamada
2018-06-07 19:36 ` Thomas Backlund
2018-06-07 19:40 ` Linus Torvalds
2018-06-07 19:49 ` Thomas Backlund
2018-06-09 12:16 ` Masahiro Yamada
2018-06-08 9:12 ` Michal Kubecek
2018-06-09 12:23 ` Masahiro Yamada
2018-06-09 16:49 ` Theodore Y. Ts'o
2018-06-05 18:12 ` Thomas Backlund [this message]
2018-06-05 20:10 ` python errors in tools/testing/selftests/tc-testing (was: Linux 4.17) Thomas Backlund
2018-06-05 21:01 ` python errors in tools/testing/selftests/tc-testing - IGNORE Thomas Backlund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48aa249f-22e8-924c-120c-8384eff9efb4@mageia.org \
--to=tmb@mageia.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®