From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] allow module-init-tools on uClinux
Date: Wed, 3 Dec 2008 22:34:38 +0100 [thread overview]
Message-ID: <20081203213438.GH8563@mx.loc> (raw)
In-Reply-To: <alpine.LFD.2.00.0812031618170.14328@xanadu.home>
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..
next prev parent reply other threads:[~2008-12-03 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 20:47 [Buildroot] [PATCH] allow module-init-tools on uClinux Nicolas Pitre
2008-12-03 21:07 ` Bernhard Reutner-Fischer
2008-12-03 21:21 ` Nicolas Pitre
2008-12-03 21:34 ` Bernhard Reutner-Fischer [this message]
2008-12-04 0:00 ` Nicolas Pitre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081203213438.GH8563@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox