Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] kmod: install depmod to output/host/usr/sbin
Date: Tue, 10 Sep 2013 22:04:16 +0200	[thread overview]
Message-ID: <87sixctpdr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <522F604C.1000206@gmail.com> (Ryan Coe's message of "Tue, 10 Sep 2013 11:09:16 -0700")

>>>>> "Ryan" == Ryan Coe <bluemrp9@gmail.com> writes:

 Ryan> After the move to kmod, building the Linux kernel no longer generates
 Ryan> the module dependencies.  The Linux build process is looking for
 Ryan> depmod at $(HOST_DIR)/usr/sbin/depmod.  Host-kmod is installing the
 Ryan> symlink for depmod at $(HOST_DIR)/sbin/depmod. Attached is a patch to
 Ryan> change the location of the depmod symlink for host-kmod.

Thanks. I decided to change the reference in linux.mk instead.

Please consider sending a real git formatted (with Signed-off-by) patch
next time.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2013-09-10 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 18:09 [Buildroot] [patch] kmod: install depmod to output/host/usr/sbin Ryan Coe
2013-09-10 20:04 ` Peter Korsgaard [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=87sixctpdr.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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