| 1 |
On Fri, 2007-07-20 at 08:49 +0200, Luigi Pinna wrote: |
| 2 |
> That is no true. |
| 3 |
> If you copy your old .config and give make, the make asks you for all |
| 4 |
> new options (I think "that" is the right one make oldconfig) |
| 5 |
> Luigi |
| 6 |
|
| 7 |
No. What you seeing is a little different. If you read the Makefile: |
| 8 |
|
| 9 |
# If .config is newer than include/config/auto.conf, someone tinkered |
| 10 |
# with it and forgot to run make oldconfig. |
| 11 |
# if auto.conf.cmd is missing then we are probably in a cleaned tree so |
| 12 |
# we execute the config step to be sure to catch updated Kconfig files |
| 13 |
include/config/auto.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd |
| 14 |
$(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig |
| 15 |
[...] |
| 16 |
|
| 17 |
So you're basically running [silent]oldconfig... But, e.g., if you |
| 18 |
happen to |
| 19 |
|
| 20 |
# mv /path/to/old/.config .config |
| 21 |
# make |
| 22 |
|
| 23 |
(or similar) then oldconfig doesn't get run and you don't get to choose |
| 24 |
new kernel options. Anyway I still hold that oldconfig is the safe bet. |
| 25 |
|
| 26 |
-- |
| 27 |
Albert W. Hopkins |
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-user@g.o mailing list |
Archives