virtualbox-5.2.10 vs. kernel 4.17-rc1+


One thing I don’t understand about Linux kernel development is the reasoning behind saying, “Oh, we don’t use this anymore, therefore nobody else is using it,” and renaming or removing something accordingly. This recently happened with pci_get_bus_and_slot(), breaking VirtualBox modules once again. You’ll see this error because of it:

/var/tmp/portage/app-emulation/virtualbox-modules-5.2.10/work/vboxpci/linux/VBoxPci-linux.c: In function ‘vboxPciLinuxDevDetachHostDriver’:
/var/tmp/portage/app-emulation/virtualbox-modules-5.2.10/work/vboxpci/linux/VBoxPci-linux.c:92:40: error: implicit declaration of function ‘pci_get_bus_and_slot’; did you mean ‘pci_get_domain_bus_and_slot’? [-Werror=implicit-function-declaration]
 # define PCI_DEV_GET_SLOT(bus, devfn)  pci_get_bus_and_slot(bus, devfn)
                                        ^

The following user patch will allow it to build:


2 responses on “virtualbox-5.2.10 vs. kernel 4.17-rc1+

  1. Third that. What the frigging f? Can they agree to an API that does not break stuff for ages? Just deprecate it give the users like 1 or 2 years to get to the new API on their own time. Just announce the EOL in advance like everybody else.

Leave a Reply