All of lore.kernel.org
 help / color / mirror / Atom feed
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 06:51:54 -0700	[thread overview]
Message-ID: <5230757A.10201@gmail.com> (raw)
In-Reply-To: <874n9rsiti.fsf@dell.be.48ers.dk>

On 09/11/2013 04:23 AM, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> writes:
>
>   Thomas> Dear Ryan Coe,
>   Thomas> On Tue, 10 Sep 2013 14:58:35 -0700, Ryan Coe wrote:
>   >> $(TARGET_MAKE_ENV) $(MAKE1) $(LINUX_MAKE_FLAGS) -C $(@D) 		\
>   >> -			DEPMOD="$(HOST_DIR)/usr/sbin/depmod" modules_install ;		\
>   >> +			DEPMOD="$(HOST_DIR)/sbin/depmod" modules_install ;		\
>
>   Thomas> Not sure why we have to pass DEPMOD here since it's already part of
>   Thomas> LINUX_MAKE_FLAGS. Am I missing something?
>
> No, I think you're right. I've removed it in git.
>
> Thanks.
>

Without the depmod in the target install, I do not get the necessary 
files installed to the target.  I am unable to load modules until I 
manually run depmod -a.

  reply	other threads:[~2013-09-11 13:51 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 [this message]
2013-09-11 14:20       ` Peter Korsgaard
     [not found]         ` <CANbLAv=Z6t7RuxrRm+uodNS55WXSKt1Raui8XLcQyoMjqk6mkw@mail.gmail.com>
2013-09-11 15:36           ` Ryan Coe

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=5230757A.10201@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.