ports/151603: Self-built virtualbox-ose-kmod vboxnetflt.ko kernel module fails to load with "link_elf: symbol RTR0Init undefined" message
ggg_mail at inbox.ru
Wed Oct 20 16:40:10 UTC 2010
>Synopsis: Self-built virtualbox-ose-kmod vboxnetflt.ko kernel module fails to load with "link_elf: symbol RTR0Init undefined" message
>Arrival-Date: Wed Oct 20 16:40:09 UTC 2010
>Originator: Grigory Rechistov
FreeBSD atakua.doesntexist.org 8.1-STABLE FreeBSD 8.1-STABLE #3: Wed Oct 20 02:06:12 MSD 2010 root at atakua.doesntexist.org:/usr/obj/usr/src/sys/INTOX i386
I found that on my system certain Virtualbox kernel modules fail to load after they are build from ports system as opposed to ones installed from packages. For instance, I decided to upgrade virtualbox-3.2.6 to virtualbox-3.2.8. THe former was from packages, the new version was build from ports with portupgrade.
But when I try to load new modules I am unsuccessfull:
# kldload vboxdrv // this works OK
#kldload vboxnetflt // returns "No such file or directory"
Additionally I get "link_elf: symbol RTR0Init undefined" on 1st console and in dmesg.
Yesterday I csup'ped to the latest stable sources, rebuilt the kernel and rebuilt Virtualbox (3.2.10) - no luck, still the same issue.
Apparently something is not built up correctly.
I have the following make.conf:
# added by use.perl 2010-07-30 23:49:23
#CFLAGS= -O2 -fno-strict-aliasing -pipe
CFLAGS = -pipe
# Seems to broke some kernel modules
#COPTFLAGS= -O -pipe
I also noted that certain other ports that require kernel modules (e.g. cuse4bsd and webcamd) fail to load the module and work if they are built from sources not acquired from packages.
1. Install virtualbox-ose-kmod from sources
2. Try to load vboxnetflt with kldload
3. See the dmesg message and no module is loaded
Using packages, even from older version with more new main port, works.
More information about the freebsd-ports-bugs