Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Cross compiling kernel module for the target
Date: Thu, 20 Dec 2018 10:07:33 +0100	[thread overview]
Message-ID: <20181220100733.5c6d0860@windsurf> (raw)
In-Reply-To: <CA+OsCCQ2TWYiEv-a8uRaJVSd4YX9A4T_EV1ihC1Y2ZyrNPAkag@mail.gmail.com>

Hello,

Please keep the mailing list in Cc when replying. Thanks!

On Thu, 20 Dec 2018 09:55:41 +0100, ?ukasz Przenios?o wrote:
> Hello Thomas, thank you for answer.
> Yes, I know it should point to the build dir, but the problem is, I dont
> have that directory and I dont know how to "place" is there. On my host I
> have seen that this build dir is a soft link to the linux headers folder,
> thus, thought this is the way around it. Could you please give me a hint on
> what I am missing in the buildroot config maybe?

Are you building a Linux kernel image as part of your Buildroot
configuration ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-12-20  9:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20  7:39 [Buildroot] Cross compiling kernel module for the target Łukasz Przeniosło
2018-12-20  8:04 ` Thomas Petazzoni
     [not found]   ` <CA+OsCCQ2TWYiEv-a8uRaJVSd4YX9A4T_EV1ihC1Y2ZyrNPAkag@mail.gmail.com>
2018-12-20  9:07     ` Thomas Petazzoni [this message]
2018-12-20  9:14       ` Łukasz Przeniosło
2018-12-20  9:20         ` Thomas Petazzoni
2018-12-20  9:34           ` Łukasz Przeniosło
2018-12-20 13:04             ` Thomas Petazzoni
2018-12-20 20:49               ` Łukasz Przeniosło
2018-12-20 21:04                 ` Łukasz Przeniosło
2018-12-21  7:14                   ` Łukasz Przeniosło

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=20181220100733.5c6d0860@windsurf \
    --to=thomas.petazzoni@bootlin.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