Bug 351136 – Cannot compile x11-drivers/xf86-video-virtualbox-4.0.0

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description wuos 2011-01-08 16:55:56 UTC]

The last lines from emerge output is:


  C       vboxvideo_drv_19 - {C}/vboxvideo_dri.c
  C       vboxvideo_drv - {C}/vboxvideo.c
  C       vboxvideo_drv - {C}/vboxutils.c
  CXX     vboxvideo_drv - {R}/src/VBox/Additions/common/VBoxVideo/HGSMIBase.cpp
/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/src/VBox/Additions/x11/vboxvideo/vboxvideo.c: In function 'vboxClearVRAM':
/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/src/VBox/Additions/x11/vboxvideo/vboxvideo.c:1166: warning: comparison between signed and unsigned [-Wsign-compare]
/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/src/VBox/Additions/x11/vboxvideo/vboxvideo.c:1168: warning: comparison between signed and unsigned [-Wsign-compare]
  CXX     vboxvideo_drv - {R}/src/VBox/GuestHost/HGSMI/HGSMICommon.cpp
  CXX     vboxvideo_drv - {R}/src/VBox/Runtime/common/alloc/heapsimple.cpp
  CXX     vboxvideo_drv - {R}/src/VBox/Runtime/common/alloc/heapoffset.cpp
  CXX     vboxvideo_drv - {R}/src/VBox/Additions/common/VBoxVideo/VBVABase.cpp
  CXX     vboxvideo_drv - {R}/src/VBox/Additions/common/VBoxVideo/Modesetting.cpp
  LD      vboxvideo_drv_70
  LD      vboxvideo_drv_71
  LD      vboxvideo_drv_13
  LD      vboxvideo_drv_14
  LD      vboxvideo_drv_15
  LD      vboxvideo_drv_16
  LD      vboxvideo_drv_17
  LD      vboxvideo_drv_18
  LD      vboxvideo_drv_19
  LD      vboxvideo_drv
ld: unrecognized option '-Wl,-O1'
ld: use the --help option for usage information
kmk: *** [/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/obj/vboxvideo_drv/vboxvideo_drv.o] Error 1
The failing command:
@ld -r               -r   -Wl,-O1 -Wl,--as-needed -m elf_x86_64   -o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/obj/vboxvideo_drv/vboxvideo_drv.o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/obj/vboxvideo_drv/vboxvideo.o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/obj/vboxvideo_drv/vboxutils.o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/obj/vboxvideo_drv/src/VBox/Additions/common/VBoxVideo/HGSMIBase.o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/obj/vboxvideo_drv/src/VBox/GuestHost/HGSMI/HGSMICommon.o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/obj/vboxvideo_drv/src/VBox/Runtime/common/alloc/heapsimple.o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/obj/vboxvideo_drv/src/VBox/Runtime/common/alloc/heapoffset.o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/obj/vboxvideo_drv/src/VBox/Additions/common/VBoxVideo/VBVABase.o /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/obj/vboxvideo_drv/src/VBox/Additions/common/VBoxVideo/Modesetting.o     /var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE/out/linux.amd64/release/lib/additions/VBoxGuestR3LibXFree86.a 
kmk: *** Waiting for unfinished jobs....
kmk: *** Exiting with status 2
emake failed
 * ERROR: x11-drivers/xf86-video-virtualbox-4.0.0 failed:
 *   kmk failed
 * 
 * Call stack:
 *     ebuild.sh, line  56:  Called src_compile
 *   environment, line 3622:  Called die
 * The specific snippet of code:
 *           MAKE="kmk" emake TOOL_YASM_AS=yasm KBUILD_PATH="${S}/kBuild" || die "kmk failed";
 * 
 * If you need support, post the output of 'emerge --info =x11-drivers/xf86-video-virtualbox-4.0.0',
 * the complete build log and the output of 'emerge -pqv =x11-drivers/xf86-video-virtualbox-4.0.0'.
 * The complete build log is located at '/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/temp/environment'.
 * S: '/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE'

>>> Failed to emerge x11-drivers/xf86-video-virtualbox-4.0.0, Log file:

>>>  '/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/temp/build.log'

 * Messages for package x11-drivers/xf86-video-virtualbox-4.0.0:

 * ERROR: x11-drivers/xf86-video-virtualbox-4.0.0 failed:
 *   kmk failed
 * 
 * Call stack:
 *     ebuild.sh, line  56:  Called src_compile
 *   environment, line 3622:  Called die
 * The specific snippet of code:
 *           MAKE="kmk" emake TOOL_YASM_AS=yasm KBUILD_PATH="${S}/kBuild" || die "kmk failed";
 * 
 * If you need support, post the output of 'emerge --info =x11-drivers/xf86-video-virtualbox-4.0.0',
 * the complete build log and the output of 'emerge -pqv =x11-drivers/xf86-video-virtualbox-4.0.0'.
 * The complete build log is located at '/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/temp/environment'.
 * S: '/var/tmp/portage/x11-drivers/xf86-video-virtualbox-4.0.0/work/VirtualBox-4.0.0_OSE'

[Comment 1 wuos 2011-01-08 16:57:45 UTC]

Created attachment 259301 [details]
emerge --info

[Comment 2 Rafał Mużyło 2011-01-08 17:26:23 UTC]

That's probably LDFLAGS vs raw-ldflags.

[Comment 3 Lars Wendler (Polynomial-C) (RETIRED) 2011-01-08 17:27:38 UTC]

+  08 Jan 2011; Lars Wendler <[e-mail]>
+  xf86-video-virtualbox-4.0.0.ebuild:
+  Removed LDFLAGS fix as it breaks compilation. Thanks to wuos for reporting
+  this in bug #351136.

Removed the LDFLAGS fix for now until a better solution has been found...

[Comment 4 Rafał Mużyło 2011-01-08 17:40:05 UTC]

(In reply to comment #3)
> Removed the LDFLAGS fix for now until a better solution has been found...
> 
...and wouldn't raw-ldflags be that solution ?