From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15161] kernel can't support SUBDIR
Date: Sat, 10 Dec 2022 08:58:19 +0000 [thread overview]
Message-ID: <bug-15161-163-EAO0KiIDMc@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15161-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15161
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998@free.fr
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Luffy, All,
When you provide overrides of standard pacjages, you have to provide
them with the same layout as the upstream version of those programs.
We can't support arbitrary overrides.
You should fix your kernel tree and your out-of-tree driver, either:
- move the driver in-tree rather than rely on a symlink, or
- ensure the driver is a proper out-of-tree driver and can compile
standalone, and create a buildroot package for it (see kernel-module
in the manual and existing packages for examples).
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:[~2022-12-10 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 4:32 [Buildroot] [Bug 15161] New: kernel can't support SUBDIR bugzilla
2022-11-30 4:34 ` [Buildroot] [Bug 15161] " bugzilla
2022-12-01 11:09 ` bugzilla
2022-12-01 11:49 ` bugzilla
2022-12-10 8:58 ` 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-15161-163-EAO0KiIDMc@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