Skip to contentSkip to conversation

allow module-init-tools on uClinux

PATCH New Nicolas Pitre 2 participants 5 messages Dec 3, 2008 – Dec 4, 2008

lore
Share & tools
lore

Nicolas Pitre

author
#0 lore raw

PATCH 1/1 allow module-init-tools on uClinux

Matching *-*-linux* is too restrictive.

Signed-off-by Nicolas Pitre <[email protected]>
module-init-tools/module-init-tools-match-uclinux.patch +23 -0
Index: package/module-init-tools/module-init-tools-match-uclinux.patch
===================================================================
@@ -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
+
#1 lore raw

PATCH 1/1 allow module-init-tools on uClinux

Quoted 1 line · Nicolas Pitre

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

author
#2 lore raw

PATCH 1/1 allow module-init-tools on uClinux

Quoted 6 lines · Bernhard Reutner-Fischer
Quoted 1 line · Nicolas Pitre

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.

Quoted 2 lines

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

#3 lore raw

PATCH 1/1 allow module-init-tools on uClinux

Quoted 11 lines · Nicolas Pitre
Quoted 6 lines · Bernhard Reutner-Fischer
Quoted 1 line · Nicolas Pitre

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.

Quoted 6 lines
Quoted 3 lines

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..

author
#4 lore raw

PATCH 1/1 allow module-init-tools on uClinux

Quoted 6 lines · Bernhard Reutner-Fischer
Quoted 2 lines · Nicolas Pitre

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: