Your message dated Fri, 14 Dec 2018 17:36:49 +0100 with message-id <98d13a39-fc31-5151-15ba-066bd48a4...@debian.org> and subject line Re: virtualbox-dkms: module FTBFS for 4.18.0-3-686, 4.18.0-3-686-pae has caused the Debian Bug report #916077, regarding virtualbox-dkms: module FTBFS for 4.18.0-3-686, 4.18.0-3-686-pae to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: virtualbox-dkms Version: 5.2.22-dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + virtualbox-guest-additions-iso Hi, virtualbox-dkms fails to build a module for 4.18.0-3-686, 4.18.0-3-686-pae (in an i386 chroot on an amd64 host, in case it matters). There are no problems bulding for 4.18.0-3-amd64. The (attached) make.log starts with: DKMS make.log for virtualbox-5.2.22 for kernel 4.18.0-3-686 (i686) Sun Dec 9 20:00:18 UTC 2018 make: Entering directory '/usr/src/linux-headers-4.18.0-3-686' make[4]: dpkg-architecture: Command not found CC [M] /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrv.o CC [M] /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvGip.o CC [M] /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvSem.o In file included from /var/lib/dkms/virtualbox/5.2.22/build/include/VBox/types.h:30:0, from /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/../SUPDrvInternal.h:35, from /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.c:32: /var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:280:9: error: unknown type name '__uint128_t' typedef __uint128_t uint128_t; ^~~~~~~~~~~ /var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:299:9: error: unknown type name '__int128_t' typedef __int128_t int128_t; ^~~~~~~~~~ Andreas
make.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---Hello, On Sun, 09 Dec 2018 21:09:25 +0100 Andreas Beckmann <a...@debian.org> wrote: > Package: virtualbox-dkms > Version: 5.2.22-dfsg-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + virtualbox-guest-additions-iso > > Hi, > > virtualbox-dkms fails to build a module for 4.18.0-3-686, > 4.18.0-3-686-pae (in an i386 chroot on an amd64 host, in case > it matters). There are no problems bulding for 4.18.0-3-amd64. > The (attached) make.log starts with: > I think you can't build kernel modules in this way... nobody reported regressions so far, please try with an i386 kernel space too :) G. > > DKMS make.log for virtualbox-5.2.22 for kernel 4.18.0-3-686 (i686) > Sun Dec 9 20:00:18 UTC 2018 > make: Entering directory '/usr/src/linux-headers-4.18.0-3-686' > make[4]: dpkg-architecture: Command not found > CC [M] /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.o > CC [M] /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrv.o > CC [M] /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvGip.o > CC [M] /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/SUPDrvSem.o > In file included from > /var/lib/dkms/virtualbox/5.2.22/build/include/VBox/types.h:30:0, > from > /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/../SUPDrvInternal.h:35, > from > /var/lib/dkms/virtualbox/5.2.22/build/vboxdrv/linux/SUPDrv-linux.c:32: > /var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:280:9: error: > unknown type name '__uint128_t' > typedef __uint128_t uint128_t; > ^~~~~~~~~~~ > /var/lib/dkms/virtualbox/5.2.22/build/include/iprt/types.h:299:9: error: > unknown type name '__int128_t' > typedef __int128_t int128_t; > ^~~~~~~~~~ > > > Andreas
--- End Message ---
