John Stoffel <stoffel@casc.com>:
> Before on startup it would give:
>
> [root@jfs linux]# make config
> rm -f include/asm
> ( cd include ; ln -sf asm-i386 asm)
> python -O scripts/cmlconfigure.py -DX86 -B 2.4.4-pre7 -W -i config.out
> rules.out
> ISA=y (deduced from X86)
> Side effects from config.out:
> NETDEVICES=m (deduced from ATALK)
> SOUND_OSS=m (deduced from SOUND_VIA82CXXX)
> SOUND_OSS=y (deduced from SOUND_YMFPCI_LEGACY)
> SOUND=y (deduced from SOUND_OSS)
> python -O scripts/configtrans.py -h include/linux/autoconf.h -s
> .config config.out
>
>
> So I poked around, found the RTC setting, read the help and now I
> understand why I should have had it enabled all along. No problem.
> So saved my changes and exited.
>
> I then restarted, and it came up properly, but I'm now getting the
> following output:
>
> [root@jfs linux]# make config
> rm -f include/asm
> ( cd include ; ln -sf asm-i386 asm)
> python -O scripts/cmlconfigure.py -DX86 -B 2.4.4-pre7 -W -i config.out
> rules.out
> ISA=y (deduced from X86)
>
>
> Notice that it's still setting the ISA=y flag, but not the rest it was
> complaining about. I think it should have either updated this setting
> by default for the ISA bus, or warned on exit that it still needed to
> be set.
>
> I think this is a true bug somewhere.
Nope, it's a benign side-effect of the order of evaluation of command-line
switches. Here's what's happening:
1. X86=y is being set and frozen.
2. ISA=y is deduced from X86
3. config.out is read in.
In step 3, you don't see any side effects from config.out because they
were calculated last time and wruitten into the saved configuration.
You still see the ISA=y message because your config.out has not yet been
read in at the time that side effect is computed.
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>"Among the many misdeeds of British rule in India, history will look upon the Act depriving a whole nation of arms as the blackest." -- Mohandas Ghandhi, An Autobiography, pg 446 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 30 2001 - 21:00:23 EST