Virtualbox compile errors on Slack 13.0 64?
in [Slackware]
|
Prev: Slack-13 - AMD-800
Next: 32bit support for Slackware64
From: Jim Diamond on 8 Sep 2009 21:01 On 2009-09-08 at 16:35 ADT, Peter Chant <REMpeteOVE(a)petezilla.co.uk> wrote: > 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! Huh. I just used the vbox automated kernel module thing. A whole lot nicer than chasing down the right vmware-any-any patch. >> 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. Ok, probably not a neutrino :-) Jim
From: Peter Chant on 9 Sep 2009 19:24 Jim Diamond wrote: >> That worked simply, combined with the slackbuild for the kernel module! > > Huh. I just used the vbox automated kernel module thing. A whole lot > nicer than chasing down the right vmware-any-any patch. > I missed that. Where is it? >>> 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. > Ok, probably not a neutrino :-) Well, I had to underclock the machine as initially when doing intensive stuff it hung. At least I think I have underclocked. I've never tried overclocking and the bios tells you all sorts of info except for what speed you have the CPU running at. I think I might cut a hole in the case an run a piece of pipe down to the CPU fan, that seems to be the thing that you get on newer PC cases than mine. -- http://www.petezilla.co.uk
From: Peter Chant on 9 Sep 2009 20:04 Peter Chant wrote: > I missed that. Where is it? > >>>> 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. >> Ok, probably not a neutrino :-) Hmm, same thing compiling wxwidgets: /tmp/txz/wxWidgets-2.8.10/bk-deps g++ -c -o richtextdll_richtextsymboldlg.o -I./.pch/wxprec_richtextdll -D__WXGTK__ -I./src/regex -DWXUSINGDLL -DWXMAKINGDLL_RICHTEXT -fPIC -DPIC -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES - I/tmp/txz/wxWidgets-2.8.10/lib/wx/include/gtk2-unicode-release-2.8 - I./include -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include - I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 - I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/X11R6/include - DWX_PRECOMP -pthread -Wall -Wundef -Wno-ctor-dtor-privacy -O2 -fno-strict- aliasing -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -O2 ../src/richtext/richtextsymboldlg.cpp ../src/richtext/richtextsymboldlg.cpp:1302: 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. make: *** [richtextdll_richtextsymboldlg.o] Error 1 bash-3.1# Just waiting to see what the results are of building it on a pure 64 bit system under virtualbox. Am using the slackbuilds in slacky.eu. -- http://www.petezilla.co.uk
From: Jim Diamond on 9 Sep 2009 20:21 On 2009-09-09 at 20:24 ADT, Peter Chant <REMpeteOVE(a)petezilla.co.uk> wrote: > Jim Diamond wrote: > >>> That worked simply, combined with the slackbuild for the kernel module! >> >> Huh. I just used the vbox automated kernel module thing. A whole lot >> nicer than chasing down the right vmware-any-any patch. >> > > I missed that. Where is it? /etc/rc.d/rc.vboxdrv setup (I don't recall if I had to handraulically move rc.vboxdrv from /etc/init.d to /etc/rc.d or not.) >>>> 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. >> Ok, probably not a neutrino :-) > Well, I had to underclock the machine as initially when doing intensive > stuff it hung. At least I think I have underclocked. I've never tried > overclocking and the bios tells you all sorts of info except for what speed > you have the CPU running at. > I think I might cut a hole in the case an run a piece of pipe down to the > CPU fan, that seems to be the thing that you get on newer PC cases than > mine. Hmmm... have you tried running memtest or doing other hardware diagnostics? You may have something from the manufacturer if the machine came with a commercial OS. Cheers. Jim
From: Peter Chant on 15 Sep 2009 20:02
Jim Diamond wrote: > Hmmm... have you tried running memtest or doing other hardware > diagnostics? You may have something from the manufacturer if the > machine came with a commercial OS. Slax comes with memtest. I think it was a basic thermal issue. Shutting a core down helped. Things only got unstable on a large compile. In the past this has always been thermally related. -- http://www.petezilla.co.uk |