[Buildroot] [PATCH] allow module-init-tools on uClinux

[Buildroot] [PATCH] allow module-init-tools on uClinux

[Nicolas Pitre]

Matching *-*-linux* is too restrictive.

Signed-off-by: Nicolas Pitre <nico@cam.org>

Index: package/module-init-tools/module-init-tools-match-uclinux.patch
===================================================================
--- package/module-init-tools/module-init-tools-match-uclinux.patch	(revision 0)
+++ package/module-init-tools/module-init-tools-match-uclinux.patch	(revision 0)
@@ -0,0 +1,23 @@
+# relax target match to also include uclinux
+--- module-init-tools-3.2.2/configure.orig	2008-11-27 12:26:35.000000000 -0500
++++ module-init-tools-3.2.2/configure	2008-11-27 12:26:47.000000000 -0500
+@@ -2818,7 +2818,7 @@
+ 
+ 
+ case $target in
+-*-*-linux*) ;;
++*-*linux*) ;;
+ *) { { echo "$as_me:$LINENO: error: Linux only, dude!" >&5
+ echo "$as_me: error: Linux only, dude!" >&2;}
+    { (exit 1); exit 1; }; };;
+--- module-init-tools-3.2.2/configure.in.orig	2008-11-27 12:26:14.000000000 -0500
++++ module-init-tools-3.2.2/configure.in	2008-11-27 12:26:56.000000000 -0500
+@@ -21,7 +21,7 @@
+ AC_SUBST(LDADD)
+ 
+ case $target in
+-*-*-linux*) ;;
++*-*linux*) ;;
+ *) AC_MSG_ERROR([Linux only, dude!]);;
+ esac
+ 

[Buildroot] [PATCH] allow module-init-tools on uClinux

[Bernhard Reutner-Fischer]

On Wed, Dec 03, 2008 at 03:47:47PM -0500, Nicolas Pitre wrote:
>Matching *-*-linux* is too restrictive.

yes, but
1) you would be better off to set BR2_PACKAGE_BUSYBOX_HIDE_OTHERS=y in
your toplevel .config, i.e. use the busybox module tools.
2) The current version is 3.5
3) Please fix this upstream, iff it is still required for 3.5

[Buildroot] [PATCH] allow module-init-tools on uClinux

[Nicolas Pitre]

On Wed, 3 Dec 2008, Bernhard Reutner-Fischer wrote:

> On Wed, Dec 03, 2008 at 03:47:47PM -0500, Nicolas Pitre wrote:
> >Matching *-*-linux* is too restrictive.
> 
> yes, but
> 1) you would be better off to set BR2_PACKAGE_BUSYBOX_HIDE_OTHERS=y in
> your toplevel .config, i.e. use the busybox module tools.

That won't help me at all for the _cross_ installation of kernel 
modules.

> 2) The current version is 3.5
> 3) Please fix this upstream, iff it is still required for 3.5

Eventually.  In the mean time this allows for the kernel to build and 
its modules to be installed.


Nicolas

[Buildroot] [PATCH] allow module-init-tools on uClinux

[Bernhard Reutner-Fischer]

On Wed, Dec 03, 2008 at 04:21:11PM -0500, Nicolas Pitre wrote:
>On Wed, 3 Dec 2008, Bernhard Reutner-Fischer wrote:
>
>> On Wed, Dec 03, 2008 at 03:47:47PM -0500, Nicolas Pitre wrote:
>> >Matching *-*-linux* is too restrictive.
>> 
>> yes, but
>> 1) you would be better off to set BR2_PACKAGE_BUSYBOX_HIDE_OTHERS=y in
>> your toplevel .config, i.e. use the busybox module tools.
>
>That won't help me at all for the _cross_ installation of kernel 
>modules.

Sure it would. Busybox doesn't have that configuration issue, works fine
on every arch and is even smaller. You don't _need_ module-init-tools in
the first place, if i'm not mistaken.
>
>> 2) The current version is 3.5
>> 3) Please fix this upstream, iff it is still required for 3.5
>
>Eventually.  In the mean time this allows for the kernel to build and 
>its modules to be installed.

Not sure if i understand you here. Why do you need a cross module-init-tools
to build or install a kernel? Just curious..

[Buildroot] [PATCH] allow module-init-tools on uClinux

[Nicolas Pitre]

On Wed, 3 Dec 2008, Bernhard Reutner-Fischer wrote:

> On Wed, Dec 03, 2008 at 04:21:11PM -0500, Nicolas Pitre wrote:
> >Eventually.  In the mean time this allows for the kernel to build and 
> >its modules to be installed.
> 
> Not sure if i understand you here. Why do you need a cross module-init-tools
> to build or install a kernel? Just curious..

FRom target/linux/Makefile.in line 203: