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 19:12:21 +0000 [thread overview]
Message-ID: <bug-16075-163-BQ0yWEgX9A@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-16075-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=16075
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
CC| |yann.morin.1998@free.fr
--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
mscdex, All,
You are calling the autotools-package macro in your linux externsion; that
is going to create an actual package, which is what is actually causing you
trouble.
The linux-ext file should be limited exactly to defining the linux extension.
Downloading the sources for the extension should be done in a separate
package.
See for example the fbtft linux extension, which is simple enough to be
a good example.
Regards,
Yann E. MORIN.
--
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
prev parent reply other threads:[~2024-05-15 19:12 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 ` [Buildroot] [Bug 16075] " bugzilla
2024-05-15 19:12 ` bugzilla [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=bug-16075-163-BQ0yWEgX9A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.