From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16075] Cannot use linux kernel extensions from external tree (building zfs into kernel)
Date: Wed, 15 May 2024 16:45:30 +0000 [thread overview]
Message-ID: <bug-16075-163-EWy2NgWmyp@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-16075-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=16075
--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
Is it possible that you have `include */*.mk` in your external.mk? This will
include your `linux/linux-ext-zfs-inkernel.mk` in the "main" buildroot include,
but it should only be included in the linux-extensions-specific section in
buildroot linux/linux.mk:
include $(sort $(wildcard $(foreach ext,$(BR2_EXTERNAL_DIRS), \
$(ext)/linux/linux-ext-*.mk)))
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-15 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 6:22 [Buildroot] [Bug 16075] New: Cannot use linux kernel extensions from external tree (building zfs into kernel) bugzilla
2024-05-15 16:45 ` bugzilla [this message]
2024-05-15 19:12 ` [Buildroot] [Bug 16075] " bugzilla
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=bug-16075-163-EWy2NgWmyp@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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