[lkml]   [2011]   [May]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Fix corruption of CONFIG_X86_32 in 'make oldconfig'

    * David Woodhouse <> wrote:

    > On Mon, 2011-05-30 at 12:58 +0200, Ingo Molnar wrote:
    > >
    > > * Theodore Tso <tytso@MIT.EDU> wrote:
    > >
    > > > I'd think that "make ARCH=x86_64 oldconfig"
    > > >
    > > > ... where the old configuration contained CONFIG_X86_32
    > > > should trigger a warning, if not an outright error that
    > > > stops the build....
    > >
    > > That would be a rather sad regression for me: i use that command
    > > regularly to transform .configs that came in bugreports into a config
    > > suitable for a testbox that has a different bitness userspace
    > > installed.
    > And if it has a different SCSI or ATA controller? Then you need
    > something like:
    > 'make CONFIG_SATA_MV=y oldconfig'
    > to make your config actually useful.

    When it wont boot straight away (often it does) i use a
    Kconfig-needed set of minimal set of configs that enables the minimal
    hardware environment.

    But bitness is not really a 'hardware environment' thing - it's a CPU
    mode thing that i want to match to 32-bit or 64-bit user-space,
    depending on which one i want to boot.

    So bitness *is* special, even if we ignored all the well-established
    workflows where people became to rely on (and appreciate) what
    ARCH=i386 and ARCH=x86_64 specifiers give us today and which ARCH=x86
    does not replace in an equivalent fashion.



     \ /
      Last update: 2011-05-30 13:37    [W:3.624 / U:1.644 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site