Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 508502 - app-emulation/virtualbox-modules - x86_64-pc-linux-gnux32-ld: Relocatable linking with relocations from format elf64-x86-64 (.../work/vboxdrv/linux/SUPDrv-linux.o) to format elf32-x86-64 (.../work/vboxdrv/vboxdrv.o) is not supported
Summary: app-emulation/virtualbox-modules - x86_64-pc-linux-gnux32-ld: Relocatable lin...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Lars Wendler (Polynomial-C)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-23 13:37 UTC by Tiago Marques
Modified: 2017-12-19 17:15 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
info (info,6.56 KB, text/plain)
2015-08-19 18:09 UTC, Toralf Förster
Details
app-emulation:virtualbox-modules-5.0.2:20150819-170417.log (app-emulation:virtualbox-modules-5.0.2:20150819-170417.log,3.91 KB, text/plain)
2015-08-19 18:09 UTC, Toralf Förster
Details
emerge-history.txt (emerge-history.txt,440.85 KB, text/plain)
2015-08-19 18:09 UTC, Toralf Förster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tiago Marques 2014-04-23 13:37:18 UTC
Hi,

Looking for some help getting this package to build. My system is currently setup with ABI_X86="x32" only, as I was having trouble building other packages with ABI_X86="x32 64", not sure why.

Below is the output I get and it builds fine if I "cd" into the build directory and type "make". The problem seems to stem from the LDFLAGS variable being passed to make:

LDFLAGS=-m elf32_x86_64

Help on how to try to fix this is highly appreciated.

Best regards,
Tiago


>>> Emerging (1 of 5) app-emulation/virtualbox-modules-4.2.22
 * vbox-kernel-module-src-4.2.22.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                                                                     [ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.12.13-gentoo/build
 * Found sources for kernel version:
 *     3.12.13-gentoo
>>> Unpacking source...
>>> Unpacking vbox-kernel-module-src-4.2.22.tar.xz to /var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work
>>> Source unpacked in /var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work
>>> Preparing source in /var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work ...
ln: failed to create symbolic link ‘Module.symvers’: File exists
 * Preparing vboxdrv module
make HOSTCC=x86_64-pc-linux-gnux32-gcc CROSS_COMPILE=x86_64-pc-linux-gnux32- 'LDFLAGS=-m elf32_x86_64' KERN_DIR=/usr/src/linux KERNOUT=/lib/modules/3.12.13-gentoo/build all
*** Building 'vboxdrv' module ***
make[1]: Entering directory `/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work/vboxdrv'
make KBUILD_VERBOSE= SUBDIRS=/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work/vboxdrv SRCROOT=/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work/vboxdrv CONFIG_MODULE_SIG= -C /usr/src/linux modules
make[2]: Entering directory `/usr/src/linux-3.12.13-gentoo'

...

  LD [M]  /var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work/vboxdrv/vboxdrv.o
x86_64-pc-linux-gnux32-ld: Relocatable linking with relocations from format elf64-x86-64 (/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work/vboxdrv/linux/SUPDrv-linux.o) to format elf32-x86-64 (/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work/vboxdrv/vboxdrv.o) is not supported
make[3]: *** [/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work/vboxdrv/vboxdrv.o] Error 1
make[2]: *** [_module_/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work/vboxdrv] Error 2
make[2]: Leaving directory `/usr/src/linux-3.12.13-gentoo'
make[1]: *** [vboxdrv] Error 2
make[1]: Leaving directory `/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work/vboxdrv'
make: *** [all] Error 2
 * ERROR: app-emulation/virtualbox-modules-4.2.22::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info '=app-emulation/virtualbox-modules-4.2.22::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/virtualbox-modules-4.2.22::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/temp/environment'.
 * Working directory: '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work'
 * S: '/var/tmp/portage/app-emulation/virtualbox-modules-4.2.22/work'


Reproducible: Always
Comment 1 Toralf Förster gentoo-dev 2015-08-19 18:09:01 UTC
Created attachment 409486 [details]
info

confirmed
  -----------------------------------------------------------------

  This is an unstable amd64 chroot image (named amd64-plasma-unstable_20150811-144142) at a hardened host acting as a tinderbox.

  Portage 2.2.20.1 (python 2.7.10-final-0, default/linux/amd64/13.0/desktop/plasma, gcc-4.9.3, glibc-2.21-r1, 4.1.4-hardened x86_64)
=================================================================
System uname: Linux-4.1.4-hardened-x86_64-Intel-R-_Core-TM-_i7-3770_CPU_@_3.40GHz-with-gentoo-2.2
Comment 2 Toralf Förster gentoo-dev 2015-08-19 18:09:03 UTC
Created attachment 409488 [details]
app-emulation:virtualbox-modules-5.0.2:20150819-170417.log
Comment 3 Toralf Förster gentoo-dev 2015-08-19 18:09:06 UTC
Created attachment 409490 [details]
emerge-history.txt
Comment 4 Tiago Marques 2015-11-27 12:00:08 UTC
Installed the modules compiled outside of Portage and they load fine. virtualbox-bin also seems to work great. Thus far haven't noticed any issues.
Comment 5 Nick Bowler 2016-05-16 21:29:56 UTC
I think this is bug 427052.