From: Ryan Coe <bluemrp9@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] linux: update depmod path for install to target
Date: Wed, 11 Sep 2013 08:36:31 -0700 [thread overview]
Message-ID: <52308DFF.1080508@gmail.com> (raw)
In-Reply-To: <CANbLAv=Z6t7RuxrRm+uodNS55WXSKt1Raui8XLcQyoMjqk6mkw@mail.gmail.com>
On 09/11/2013 07:23 AM, Ryan Coe wrote:
>
> I will try it without the second instance and report back.
>
> On Sep 11, 2013 7:20 AM, "Peter Korsgaard" <jacmet@uclibc.org
> <mailto:jacmet@uclibc.org>> wrote:
>
> >>>>> "Ryan" == Ryan Coe <bluemrp9@gmail.com
> <mailto:bluemrp9@gmail.com>> writes:
>
> Hi,
>
> Ryan> Without the depmod in the target install, I do not get the
> necessary
> Ryan> files installed to the target. I am unable to load modules
> until I
> Ryan> manually run depmod -a.
>
> Really? LINUX_MAKE_FLAGS expands to .. DEPMOD=$(HOST_DIR)/sbin/depmod,
> so we ended up passing 2x DEPMOD= to modules_install.
>
> --
> Bye, Peter Korsgaard
>
I can confirm that this does work. The second time that depmod was
passed was causing trouble.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130911/8c1d3b3b/attachment.html>
prev parent reply other threads:[~2013-09-11 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 21:58 [Buildroot] [PATCH 1/1] linux: update depmod path for install to target Ryan Coe
2013-09-11 7:27 ` Thomas Petazzoni
2013-09-11 11:23 ` Peter Korsgaard
2013-09-11 13:51 ` Ryan Coe
2013-09-11 14:20 ` Peter Korsgaard
[not found] ` <CANbLAv=Z6t7RuxrRm+uodNS55WXSKt1Raui8XLcQyoMjqk6mkw@mail.gmail.com>
2013-09-11 15:36 ` Ryan Coe [this message]
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=52308DFF.1080508@gmail.com \
--to=bluemrp9@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