Hi all :))
I've seen posts here about doing 'make allyesconfig' on 2.4.19,
but allyesconfig is not on my 2.4.19 tree... AFAIK, the 'allyesconfig'
target is on 2.5.x branch, am I wrong?
BTW, if 'allyesconfig' is only on the 2.5 branch, is going to be
included somewhere on 2.4? I would find it very useful when doing
test compilations ;) A .config with all options enabled will be
useful too if 'allyesconfig' cannot be included on 2.4.
And, if anyone is interested, I've compiled 2.4.19, 2.4.20-pre2
and 2.4.20-pre2-ac3 with GCC 3.2 and all has going OK (with my
.config, at least).
If I am missing something, please tell, thanks :)
Ra?l
On Sun, 18 Aug 2002, DervishD wrote:
> included somewhere on 2.4? I would find it very useful when doing
> test compilations ;) A .config with all options enabled will be
> useful too if 'allyesconfig' cannot be included on 2.4.
>
> And, if anyone is interested, I've compiled 2.4.19, 2.4.20-pre2
> and 2.4.20-pre2-ac3 with GCC 3.2 and all has going OK (with my
> .config, at least).
>
> If I am missing something, please tell, thanks :)
man yes
On Sun, Aug 18, 2002 at 11:55:52PM +0200, DervishD wrote:
> Hi all :))
>
> I've seen posts here about doing 'make allyesconfig' on 2.4.19,
> but allyesconfig is not on my 2.4.19 tree... AFAIK, the 'allyesconfig'
> target is on 2.5.x branch, am I wrong?
you can download (and apply) kbuild-2.5 for 2.4.19 on sourceforge :
http://sourceforge.net/projects/showfiles.php?group_id=18813
I agree that allyesconfig and allmodconfig are very convenient ways to test
kernels and compilation problems.
Cheers,
Willy
On Mon, Aug 19, 2002 at 01:09:25AM -0400, Christian Robert wrote:
>
> http://sourceforge.net/projects/showfiles.php?group_id=18813
>
> The above link give: Invalid Project error message.
Sorry, I was careful about copying the URL, but added a silly 's' to
project :-(
here is the good one (with cut'n'paste this time) :
http://sourceforge.net/project/showfiles.php?group_id=18813
Willy
Hi Willy :)
>I agree that allyesconfig and allmodconfig are very convenient ways
>to test kernels and compilation problems.
Thanks for your answer :). I'm particularly interested in
allmodconfig for compilation problems.
Ra?l
On Mon, Aug 19, 2002 at 03:25:31PM +0200, DervishD wrote:
> Thanks for your answer :). I'm particularly interested in
> allmodconfig for compilation problems.
Take a copy of Configure from Linux-2.5
and add the following lines to the top-level Makefile around line 300:
+randconfig: symlinks
+ $(CONFIG_SHELL) scripts/Configure -r arch/$(ARCH)/config.in
+
+allyesconfig: symlinks
+ $(CONFIG_SHELL) scripts/Configure -y arch/$(ARCH)/config.in
+
+allnoconfig: symlinks
+ $(CONFIG_SHELL) scripts/Configure -n arch/$(ARCH)/config.in
+
+allmodconfig: symlinks
+ $(CONFIG_SHELL) scripts/Configure -m arch/$(ARCH)/config.in
+
+defconfig: symlinks
+ yes '' | $(CONFIG_SHELL) scripts/Configure -d arch/$(ARCH)/config.in
That gives you the targets you have requested from 2.5
Sam