Skip to contentSkip to conversation

make cloneconfig ?

DISCUSSION [email protected] 1 participant 1 message Apr 24, 2008 Kconfig

lore
Share & tools
lore
#0 lore raw
Quoted 2 lines

Isn't "cloneconfig" basically just "zcat /proc/config.gz > .config && make oldconfig" ???

yes (see below)

Quoted 2 lines

If so, why do we need yet another "make <some_target>" Makefile rule? What would actually be gained?

ease of use and less confused users of suse-kernel based distro`s.
i have seen people giving hints for kernel compilation and telling "just do make cloneconfig" to non-suse users, just because they didn`t know, that this is suse specific.

ok, thats not a real reason because you could argue that suse should drop it for more consistent end-user experience, but i think its much easier (and hassle free) to add it to mainline than drop it from suse.

roland

List:       linux-kernel
Subject:    [kbuild 3/5] Add cloneconfig target
From:       Andreas Gruenbacher <agruen () suse ! de>
Date:       2005-01-18 18:41:23
Message-ID: 20050118192608.500213000.suse.de

[Download message RAW]

Cloneconfig takes the first configuration it finds which appears to belong to the running kernel, and configures the kernel sources to match this configuration as closely as possible.

scripts/kconfig/Makefile +16 -0
Index: linux-2.6.11-rc1-bk6/scripts/kconfig/Makefile
===================================================================
@@ -37,6 +37,22 @@ allnoconfig: $(obj)/conf
 allmodconfig: $(obj)/conf
 	$< -m arch/$(ARCH)/Kconfig
 
+UNAME_RELEASE := $(shell uname -r)
+CLONECONFIG := $(firstword $(wildcard /proc/config.gz \
+				      /lib/modules/$(UNAME_RELEASE)/.config \
+				      /etc/kernel-config \
+				      /boot/config-$(UNAME_RELEASE)))
+cloneconfig: $(obj)/conf
+	$(Q)case "$(CLONECONFIG)" in				\
+	'')	echo -e "The configuration of the running"	\
+			"kernel could not be determined\n";	\
+		false ;;					\
+	*.gz)	gzip -cd $(CLONECONFIG) > .config.running ;;	\
+	*)	cat $(CLONECONFIG) > .config.running ;;		\
+	esac &&							\
+	echo -e "Cloning configuration file $(CLONECONFIG)\n"
+	$(Q)$< -D .config.running arch/$(ARCH)/Kconfig
+
 defconfig: $(obj)/conf
 ifeq ($(KBUILD_DEFCONFIG),)
 	$< -d arch/$(ARCH)/Kconfig

--
Andreas Gruenbacher <[email protected]>
SUSE Labs, SUSE LINUX PRODUCTS GMBH

Quoted 17 lines

-----Ursprüngliche Nachricht-----
Von: "Jesper Juhl" <[email protected]>
Gesendet: 24.04.08 00:43:56
An: "[email protected]" <[email protected]>
CC: [email protected], [email protected]
Betreff: Re: make cloneconfig ?

Quoted 8 lines · On 24/04/2008, [email protected] <[email protected]> wrote:

any reason why "make cloneconfig" never made it into mainline?

many people are quite used to it and every time i build vanilla kernel i step into that trap "oh - thats a suseism"

make cloneconfig exists since /proc/config.gz - but while that one went into mainline, cloneconfig never did.

anyone know the reason for that ?

Quoted 13 lines
Quoted 3 lines

i wished, distros kernels were more similar to vanilla kernels - so what about making them more similar ?

Isn't "cloneconfig" basically just "zcat /proc/config.gz > .config &&
make oldconfig" ??? If so, why do we need yet another "make
<some_target>" Makefile rule? What would actually be gained?

Signature · 3 lines
Jesper Juhl <[email protected]>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

_______________________________________________________________
Schon gehört? Der neue WEB.DE MultiMessenger kann`s mit allen:
http://www.produkte.web.de/messenger/?did=3016