Ah, thanks for clarifying this. Unfortunately this means, that there is a small chance, that "make oldconfig" will not work correctly in all cases, eg. upgrading a kernel to a newer version could yield into such failed compile step :-(
Am Monday 11 September 2006 08:33 schrieb Erez Zilber: > Toralf Förster wrote: > > Your're right, sorry, > > > > I forgot this to say that: > > - first I created a random .config file using "make rndconfig" > > - after that I removed all options not fitting my system > > - then I prepended some options commonly used by me on top of the .config > > file > > - and run finally a "make oldconfig" to-hopefully- get a clean config > > > > Doesn't "make oldconfig" make a clean .config file ? > > > > > Here's what the kernel's README file has to say about it: > "make oldconfig": Default all questions based on the contents of your > existing ./.config file and asking about new config symbols. > > I guess that 'make rndconfig' selected CONFIG_INFINIBAND=y, but didn't > select CONFIG_INFINIBAND_ADDR_TRANS=y. Then, 'make oldconfig' asked you > about new symbols. I guess that running 'make rndconfig' may create > scenarios like this, but I don't think that there's a bug in iSER's > Kconfig file. If you still want to use your .config file, reselect > InfiniBand in 'make menuconfig'. It will set CONFIG_INFINIBAND_ADDR_TRANS=y. > > I hope this helps. > > Erez > > -- MfG/Sincerely Toralf Förster
pgpANvQzXX86B.pgp
Description: PGP signature
_______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
