From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14701] New: Multiple unresolved symbols while building kernel module package
Date: Mon, 28 Mar 2022 06:11:42 +0000 [thread overview]
Message-ID: <bug-14701-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14701
Bug ID: 14701
Summary: Multiple unresolved symbols while building kernel
module package
Product: buildroot
Version: 2021.11.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: jose.pekkarinen@unikie.com
CC: buildroot@uclibc.org
Target Milestone: ---
Hi,
I'm trying to build a package for sgx driver:
https://github.com/intel/linux-sgx
The package looks like:
sgx-driver.mk:
################################################################################
#
# sgx-driver
#
################################################################################
SGX_DRIVER_VERSION = 2.14
SGX_DRIVER_SOURCE = sgx_driver_$(SGX_DRIVER_VERSION).tar.gz
SGX_DRIVER_SITE = https://github.com/intel/linux-sgx-driver/archive/refs/tags
SGX_DRIVER_LICENSE = BSD-3-Clause, GPL-2.0
SGX_DRIVER_LICENSE_FILES = License.txt
$(eval $(kernel-module))
$(eval $(generic-package))
Config.in:
comment "sgx-driver needs a Linux kernel to be built"
depends on !BR2_LINUX_KERNEL
config BR2_PACKAGE_SGX_DRIVER
bool "sgx-driver"
depends on BR2_LINUX_KERNEL
help
Intel sgx driver for secured containers.
https://github.com/intel/linux-sgx-driver
When building with a valid config, the build process
stops like this:
>>> sgx-driver 2.14 Building kernel module(s)
PATH="/usr/src/output/br_admin/output_x86_upxtreme/host/bin:/usr/src/output/br_admin/output_x86_upxtreme/host/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
PKG_CONFIG="/usr/src/output/br_admin/output_x86_upxtreme/host/bin/pkg-config"
PKG_CONFIG_SYSROOT_DIR="/" PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1
PKG_CONFIG_ALLOW_SYSTEM_LIBS=1
PKG_CONFIG_LIBDIR="/usr/src/output/br_admin/output_x86_upxtreme/host/lib/pkgconfig:/usr/src/output/br_admin/output_x86_upxtreme/host/share/pkgconfig"
BR_BINARIES_DIR=/usr/src/output/br_admin/output_x86_upxtreme/images
KCFLAGS=-Wno-attribute-alias /usr/bin/make -j9 -C
/usr/src/output/br_admin/output_x86_upxtreme/build/linux-tc-x86-5.15-sec
HOSTCC="/usr/src/output/br_admin/output_x86_upxtreme/host/bin/ccache
/usr/bin/gcc -O2 -I/usr/src/output/br_admin/output_x86_upxtreme/host/include
-L/usr/src/output/br_admin/output_x86_upxtreme/host/lib
-Wl,-rpath,/usr/src/output/br_admin/output_x86_upxtreme/host/lib" ARCH=x86_64
INSTALL_MOD_PATH=/usr/src/output/br_admin/output_x86_upxtreme/target
CROSS_COMPILE="/usr/src/output/br_admin/output_x86_upxtreme/host/bin/x86_64-TII-linux-gnu-"
DEPMOD=/usr/src/output/br_admin/output_x86_upxtreme/host/sbin/depmod
INSTALL_MOD_STRIP=1
PWD=/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/.
M=/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/. modules
make[2]: Entering directory
'/usr/src/output/br_admin/output_x86_upxtreme/build/linux-tc-x86-5.15-sec'
CC [M]
/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./sgx_main.o
CC [M]
/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./sgx_page_cache.o
CC [M]
/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./sgx_ioctl.o
CC [M]
/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./sgx_vma.o
CC [M]
/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./sgx_util.o
CC [M]
/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./sgx_encl.o
CC [M]
/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./sgx_encl2.o
LD [M]
/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.o
MODPOST
/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./Module.symvers
ERROR: modpost: "flush_work"
[/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.ko]
undefined!
ERROR: modpost: "put_pid"
[/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.ko]
undefined!
ERROR: modpost: "up_read"
[/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.ko]
undefined!
ERROR: modpost: "boot_cpu_data"
[/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.ko]
undefined!
ERROR: modpost: "system_freezing_cnt"
[/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.ko]
undefined!
ERROR: modpost: "mmu_notifier_register"
[/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.ko]
undefined!
ERROR: modpost: "__warn_printk"
[/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.ko]
undefined!
ERROR: modpost: "__x86_indirect_alt_call_rbx"
[/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.ko]
undefined!
ERROR: modpost: "__x86_indirect_thunk_rcx"
[/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.ko]
undefined!
ERROR: modpost: "alloc_pages"
[/usr/src/output/br_admin/output_x86_upxtreme/build/sgx-driver-2.14/./isgx.ko]
undefined!
WARNING: modpost: suppressed 65 unresolved symbol warnings because there were
too many)
WARNING: modpost: modpost: Found 2 writable function pointers.
While the symbols can be found in the original
source code of the kernel. Am I missing something
in the package to resolv the symbols?
Thanks!
José.
--
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 reply other threads:[~2022-03-28 6:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 6:11 bugzilla [this message]
2022-03-29 6:07 ` [Buildroot] [Bug 14701] Multiple unresolved symbols while building kernel module package bugzilla
2022-03-29 6:21 ` bugzilla
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@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.