From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14701] Multiple unresolved symbols while building kernel module package
Date: Tue, 29 Mar 2022 06:21:17 +0000 [thread overview]
Message-ID: <bug-14701-163-0bTzUitrDi@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14701-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14701
--- Comment #2 from José Pekkarinen <jose.pekkarinen@unikie.com> ---
as a workaround I have added to the package the following line:
SGX_DRIVER_MAKE_OPTS=KBUILD_MODPOST_WARN=1
That allows to build and test stuff. I'm uncertain this is a
kernel bug instead of a buildroot one by now.
--
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:[~2022-03-29 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 6:11 [Buildroot] [Bug 14701] New: Multiple unresolved symbols while building kernel module package bugzilla
2022-03-29 6:07 ` [Buildroot] [Bug 14701] " bugzilla
2022-03-29 6:21 ` bugzilla [this message]
2022-03-29 7:23 ` bugzilla
2022-03-30 5:37 ` bugzilla
2022-04-07 5:18 ` 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-14701-163-0bTzUitrDi@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