Virtualbox compile errors on Slack 13.0 64?
in [Slackware]
|
Prev: Slack-13 - AMD-800
Next: 32bit support for Slackware64
From: Peter Chant on 8 Sep 2009 03:36 Does anyone get this error when building Virtualbox from slackbuilds? /tmp/SBo/VirtualBox-3.0.4_OSE/src/VBox/Frontends/VirtualBox/src/VBoxLineTextEdit.cpp: In member function 'bool QBasicAtomicInt::ref()': /tmp/SBo/VirtualBox-3.0.4_OSE/src/VBox/Frontends/VirtualBox/src/VBoxLineTextEdit.cpp:121: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. kmk[2]: *** [/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/obj/VirtualBox/src/VBoxLineTextEdit.o] Error 1 The failing command: @g++ -c -O2 -fPIC -g -pipe -Wall -Wextra -Wno-missing-field-initializers - Wno-trigraphs -frtti -fno-exceptions -Wno-non-virtual-dtor -Wno-long-long - fshort-wchar -fno-strict-aliasing -fvisibility=hidden - DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -fvisibility- inlines-hidden -pthread -m64 - I/tmp/SBo/VirtualBox-3.0.4_OSE/src/VBox/Frontends/VirtualBox/include - I/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/obj/VirtualBox/include - I/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/bin/sdk/bindings/xpcom/include - I/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/xpcom - I/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/string - I/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/xpcom - I/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub - I/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/ipcd -I/usr/lib64/qt/include/QtCore -I/usr/lib64/qt/include/QtGui - I/usr/lib64/qt/include/QtNetwork -I/usr/lib64/qt/include - I/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/obj/VirtualBox/qtmoc -I/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/obj/VirtualBox/qtuic -I/usr/include/SDL -I/tmp/SBo/VirtualBox-3.0.4_OSE/include - I/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release - DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DVBOX -DVBOX_OSE - DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING - DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" - DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib64/virtualbox\" - DRTPATH_SHARED_LIBS=\"/usr/lib64/virtualbox\" -DRTPATH_APP_DOCS=\"\" - DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DRT_OS_LINUX - D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DPIC -DIN_RING3 - DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_SHARED -DHAVE_CONFIG_H - DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -DVBOX_WITH_XPCOM - DVBOX_WITH_XPCOM_NAMESPACE_CLEANUP -DVBOX_GUI_SEPARATE_VM_PROCESS - DVBOX_WITH_REGISTRATION -DVBOX_WITH_REGISTRATION_REQUEST - DVBOX_WITH_UPDATE_REQUEST -DVBOX_WITH_ALSA -DVBOX_WITH_E1000 - DVBOX_WITH_NETFLT -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -D_REENTRANT - DVBOX_GUI_USE_QIMAGE -DVBOX_GUI_USE_SDL -Wp,- MD,/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/obj/VirtualBox/src/VBoxLineTextEdit.o.dep -Wp,- MT,/tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/obj/VirtualBox/src/VBoxLineTextEdit.o -Wp,-MP -o /tmp/SBo/VirtualBox-3.0.4_OSE/out/linux.amd64/release/obj/VirtualBox/src/VBoxLineTextEdit.o /tmp/SBo/VirtualBox-3.0.4_OSE/src/VBox/Frontends/VirtualBox/src/VBoxLineTextEdit.cpp kmk[2]: *** Waiting for unfinished jobs.... kmk[2]: Leaving directory `/tmp/SBo/VirtualBox-3.0.4_OSE' kmk[2]: Entering directory `/tmp/SBo/VirtualBox-3.0.4_OSE' kmk[2]: *** Exiting with status 2 kmk[1]: *** [pass_dlls_this] Error 2 kmk[1]: Leaving directory `/tmp/SBo/VirtualBox-3.0.4_OSE' kmk: *** [pass_dlls_order] Error 2 -- http://www.petezilla.co.uk
From: Simon Sibbez on 8 Sep 2009 04:08 Peter Chant wrote: > Does anyone get this error when building Virtualbox from slackbuilds? you need multilib (but just for the compile)
From: Peter Chant on 8 Sep 2009 08:08 Simon Sibbez wrote: > Peter Chant wrote: > >> Does anyone get this error when building Virtualbox from slackbuilds? > > you need multilib (but just for the compile) Already have it, needed it for proprietary 32 bit only printer drivers. -- http://www.petezilla.co.uk
From: Jim Diamond on 8 Sep 2009 09:37 On 2009-09-08 at 09:08 ADT, Peter Chant <REMpeteOVE(a)petezilla.co.uk> wrote: > Simon Sibbez wrote: > >> Peter Chant wrote: >> >>> Does anyone get this error when building Virtualbox from slackbuilds? >> >> you need multilib (but just for the compile) > > Already have it, needed it for proprietary 32 bit only printer drivers. > In Peter's first message there was >> /tmp/SBo/VirtualBox-3.0.4_OSE/src/VBox/Frontends/VirtualBox/src/VBoxLineTextEdi >> t.cpp: >> In member function 'bool QBasicAtomicInt::ref()': >> /tmp/SBo/VirtualBox-3.0.4_OSE/src/VBox/Frontends/VirtualBox/src/VBoxLineTextEdi >> t.cpp:121: >> internal compiler error: Segmentation fault >> Please submit a full bug report, >> with preprocessed source if appropriate. >> See <http://gcc.gnu.org/bugs.html> for instructions. Peter, I compiled vbox 3.04 with no problems by running their VirtualBox-3.0.4-50677-Linux_amd64.run package. The fact that you got an "internal compiler error" makes me wonder whether you have a (possibly transient) hardware fault. Did you try running it a second time in case one of your bits was hit by a stray neutrino? If that doesn't work, try d/l'ing and running that package, it installs mostly into /opt, so even though you don't have it installed as a slackware package, it isn't dropping files all over your system. Cheers. Jim
From: Peter Chant on 8 Sep 2009 15:35
Jim Diamond wrote: > Peter, I compiled vbox 3.04 with no problems by running their > VirtualBox-3.0.4-50677-Linux_amd64.run > package. The fact that you got an "internal compiler error" makes me > wonder whether you have a (possibly transient) hardware fault. That worked simply, combined with the slackbuild for the kernel module! > > Did you try running it a second time in case one of your bits was hit > by a stray neutrino? If that doesn't work, try d/l'ing and running > that package, it installs mostly into /opt, so even though you don't > have it installed as a slackware package, it isn't dropping files all > over your system. > Crashes in exactly the same place. Annoying thing is, I'm suffering several IT problems at once, so I was planning on using virtual box to configure a couple of extra slack virtual boxes for testing purposes. Basically, the error is still there but I have a solution for a working virtualbox! -- http://www.petezilla.co.uk |