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 22:25:04 +0200	[thread overview]
Message-ID: <20160426222504.66c17f22@free-electrons.com> (raw)
In-Reply-To: <CAN34foyVVDZTtB06iWVW_g=OrcPy+8g2wiiTPqDwWNqT1cXTAg@mail.gmail.com>

Hello,

(Resending with the Buildroot mailing list in Cc. Please always keep
the list in Cc. Thanks!)

On Tue, 26 Apr 2016 16:20:17 -0400, Stephen Beckwith wrote:

> KMOD_MEM_MODULE_MAKE_OPTS = NETAPP_DIR=$(BR2_EXTERNAL)/netapp

Get rid of this.

> #inform the kernel that a module needs to be build
> obj-m := hwdd_memory.o
> hwdd_memory-objs := hwdd_mem.o hwdd_memalgo.o hwdd_cache_algos.o
> 
> # Global Includes here
> GBL_INCLUDES = $(NETAPP_DIR)/include
> KNL_INCLUDES = $(NETAPP_DIR)/include/kernel

And those two variable definitions.

> #Add here the CFLAGS to pass in to get the Defined Symbol
> CFLAGS_hwdd_memory.o := -DCONFIG_NETAPP_HWDD -I$(GBL_INCLUDES)
> -I$(KNL_INCLUDES)

And replace this by:

ccflags-y := -DCONFIG_NETAPP_HWDD -I$(src)/include -I$(src)/include/kernel

Again, I've spent time creating an example that I've tested. Since I
can't reproduce your test case, please try my example, which you can
test as I'm providing the entire source code :)

Best regards,

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

  parent reply	other threads:[~2016-04-26 20:25 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
     [not found]   ` <CAN34foyVVDZTtB06iWVW_g=OrcPy+8g2wiiTPqDwWNqT1cXTAg@mail.gmail.com>
2016-04-26 20:25     ` Thomas Petazzoni [this message]
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=20160426222504.66c17f22@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