Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Multi-File Kernel Module Build Fails
Date: Tue, 26 Apr 2016 21:49:28 +0200	[thread overview]
Message-ID: <20160426214928.5d518086@free-electrons.com> (raw)
In-Reply-To: <CAN34fowqUhJX9LZ-7qkzr=20-dKFFX9r8suAuXpVnn-brbacQw@mail.gmail.com>

Hello,

On Tue, 26 Apr 2016 14:44:28 -0400, Stephen Beckwith wrote:

>    I posted this same issue last week and received no response.  After some
> more investigation and trying several different options, I am still STUCK
> and cannot move forward.

Since you didn't post your entire code, we're not able to reproduce the
exact same situation. However, to show how things can work, I've
created a minimal example of a kernel module with two C files and one
header file (to mimic your use case) and then the corresponding
Buildroot package.

See:

  http://thomas.enix.org/example-kernel-module.html

for all the files, both the kernel module itself and the Buildroot
packaging.

Let me know if that works for you.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-04-26 19:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 18:44 [Buildroot] Multi-File Kernel Module Build Fails Stephen Beckwith
2016-04-26 19:49 ` Thomas Petazzoni [this message]
     [not found]   ` <CAN34foyVVDZTtB06iWVW_g=OrcPy+8g2wiiTPqDwWNqT1cXTAg@mail.gmail.com>
2016-04-26 20:25     ` Thomas Petazzoni
2016-04-26 21:00       ` Stephen Beckwith
2016-04-27 16:01         ` Stephen Beckwith
2016-04-28 19:23   ` Peter Korsgaard
2016-04-28 20:00     ` Thomas Petazzoni

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=20160426214928.5d518086@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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