Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
On Tue, Nov 26, 2013 at 3:50 PM, Matthias Apitz g...@unixarea.de wrote: Hello, After getting finally compiled and install virtualbox: # pkg_info | fgrep virtualbox virtualbox-ose-4.3.2 A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.3.0 VirtualBox kernel module for FreeBSD # uname -a FreeBSD aurora.Sisis.de 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18 12:10:57 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC i386 The VirtualBox crashes on startup with the following bt in gdb: #0 0x in ?? () [New Thread 28803080 (LWP 100232/VirtualBox)] (gdb) bt #0 0x in ?? () #1 0x2813c10e in __dynamic_cast (src_ptr=0x289ca650, src_type=0x2dcc4bc0, dst_type=0x2dcc4c10, src2dst=0) at ../../.././../gcc-4.6.3/libstdc++-v3/libsupc++/dyncast.cc:61 #2 0x2d9a6842 in KConfigGroup::reparent () from /usr/local/kde4/lib/libkdecore.so.7 #3 0x2d99e82d in KConfigGroup::KConfigGroup () from /usr/local/kde4/lib/libkdecore.so.7 #4 0x2da907c3 in KStandardDirs::addCustomized () from /usr/local/kde4/lib/libkdecore.so.7 #5 0x2da82e96 in KComponentData::KComponentData () from /usr/local/kde4/lib/libkdecore.so.7 #6 0x2da82c7c in KComponentData::KComponentData () from /usr/local/kde4/lib/libkdecore.so.7 #7 0x2da82581 in KGlobal::findDirectChild_helper () from /usr/local/kde4/lib/libkdecore.so.7 #8 0x2da81528 in KGlobal::dirs () from /usr/local/kde4/lib/libkdecore.so.7 #9 0x2da815f8 in KGlobal::config () from /usr/local/kde4/lib/libkdecore.so.7 #10 0x2cf295d6 in qt_plugin_instance () from /usr/local/kde4/lib/kde4/plugins/gui_platform/libkde.so #11 0x2a537711 in QApplicationPrivate::x11_apply_settings () from /usr/local/lib/qt4/libQtGui.so.4 #12 0x2a53fc5d in qt_set_x11_resources () from /usr/local/lib/qt4/libQtGui.so.4 #13 0x2a53d8be in qt_init () from /usr/local/lib/qt4/libQtGui.so.4 #14 0x2a4bc1fa in QApplicationPrivate::construct () from /usr/local/lib/qt4/libQtGui.so.4 #15 0x2a4bcbf6 in QApplication::QApplication () from /usr/local/lib/qt4/libQtGui.so.4 #16 0x29335dc9 in TrustedMain (argc=1, argv=0xbfbfd524) at CIShared.h:52 #17 0xbfbfd3f0 in ?? () #18 0x28966200 in ?? () #19 0xbfbfd490 in ?? () #20 0xbfbfd524 in ?? () #21 0x28829800 in ?? () #22 0x in ?? () (gdb) Any ideas? This looks like a libstdc++ bug that is triggered by Qt and might already be fixed in more recent 10-stable. So please try to update to 10.0-BETA3 first. Btw: I have had to # pkg_delete -f compat8x-i386-8.4.804000.201309_1 to get its shared lib out of the way; Yeah that is a known issue. I guess I need to add the compat8x, 9x, 10x ports to the conflicting list in vbox. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
El día Tuesday, November 26, 2013 a las 03:54:57PM +0100, Bernhard Fr?hlich escribió: On Tue, Nov 26, 2013 at 3:50 PM, Matthias Apitz g...@unixarea.de wrote: The VirtualBox crashes on startup with the following bt in gdb: #0 0x in ?? () [New Thread 28803080 (LWP 100232/VirtualBox)] (gdb) bt #0 0x in ?? () #1 0x2813c10e in __dynamic_cast (src_ptr=0x289ca650, src_type=0x2dcc4bc0, dst_type=0x2dcc4c10, src2dst=0) at ../../.././../gcc-4.6.3/libstdc++-v3/libsupc++/dyncast.cc:61 #2 0x2d9a6842 in KConfigGroup::reparent () from /usr/local/kde4/lib/libkdecore.so.7 #3 0x2d99e82d in KConfigGroup::KConfigGroup () from /usr/local/kde4/lib/libkdecore.so.7 #4 0x2da907c3 in KStandardDirs::addCustomized () from /usr/local/kde4/lib/libkdecore.so.7 #5 0x2da82e96 in KComponentData::KComponentData () from /usr/local/kde4/lib/libkdecore.so.7 #6 0x2da82c7c in KComponentData::KComponentData () from /usr/local/kde4/lib/libkdecore.so.7 #7 0x2da82581 in KGlobal::findDirectChild_helper () from /usr/local/kde4/lib/libkdecore.so.7 #8 0x2da81528 in KGlobal::dirs () from /usr/local/kde4/lib/libkdecore.so.7 #9 0x2da815f8 in KGlobal::config () from /usr/local/kde4/lib/libkdecore.so.7 #10 0x2cf295d6 in qt_plugin_instance () from /usr/local/kde4/lib/kde4/plugins/gui_platform/libkde.so #11 0x2a537711 in QApplicationPrivate::x11_apply_settings () from /usr/local/lib/qt4/libQtGui.so.4 #12 0x2a53fc5d in qt_set_x11_resources () from /usr/local/lib/qt4/libQtGui.so.4 #13 0x2a53d8be in qt_init () from /usr/local/lib/qt4/libQtGui.so.4 #14 0x2a4bc1fa in QApplicationPrivate::construct () from /usr/local/lib/qt4/libQtGui.so.4 #15 0x2a4bcbf6 in QApplication::QApplication () from /usr/local/lib/qt4/libQtGui.so.4 #16 0x29335dc9 in TrustedMain (argc=1, argv=0xbfbfd524) at CIShared.h:52 ... This looks like a libstdc++ bug that is triggered by Qt and might already be fixed in more recent 10-stable. So please try to update to 10.0-BETA3 first. My kernel and userland are r255948 (October 1st) and the ports are from r328930 (as well October 1st). Do you really think that this is to old? Thx matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
On Tue, Nov 26, 2013 at 4:03 PM, Matthias Apitz g...@unixarea.de wrote: El día Tuesday, November 26, 2013 a las 03:54:57PM +0100, Bernhard Fr?hlich escribió: On Tue, Nov 26, 2013 at 3:50 PM, Matthias Apitz g...@unixarea.de wrote: The VirtualBox crashes on startup with the following bt in gdb: #0 0x in ?? () [New Thread 28803080 (LWP 100232/VirtualBox)] (gdb) bt #0 0x in ?? () #1 0x2813c10e in __dynamic_cast (src_ptr=0x289ca650, src_type=0x2dcc4bc0, dst_type=0x2dcc4c10, src2dst=0) at ../../.././../gcc-4.6.3/libstdc++-v3/libsupc++/dyncast.cc:61 #2 0x2d9a6842 in KConfigGroup::reparent () from /usr/local/kde4/lib/libkdecore.so.7 #3 0x2d99e82d in KConfigGroup::KConfigGroup () from /usr/local/kde4/lib/libkdecore.so.7 #4 0x2da907c3 in KStandardDirs::addCustomized () from /usr/local/kde4/lib/libkdecore.so.7 #5 0x2da82e96 in KComponentData::KComponentData () from /usr/local/kde4/lib/libkdecore.so.7 #6 0x2da82c7c in KComponentData::KComponentData () from /usr/local/kde4/lib/libkdecore.so.7 #7 0x2da82581 in KGlobal::findDirectChild_helper () from /usr/local/kde4/lib/libkdecore.so.7 #8 0x2da81528 in KGlobal::dirs () from /usr/local/kde4/lib/libkdecore.so.7 #9 0x2da815f8 in KGlobal::config () from /usr/local/kde4/lib/libkdecore.so.7 #10 0x2cf295d6 in qt_plugin_instance () from /usr/local/kde4/lib/kde4/plugins/gui_platform/libkde.so #11 0x2a537711 in QApplicationPrivate::x11_apply_settings () from /usr/local/lib/qt4/libQtGui.so.4 #12 0x2a53fc5d in qt_set_x11_resources () from /usr/local/lib/qt4/libQtGui.so.4 #13 0x2a53d8be in qt_init () from /usr/local/lib/qt4/libQtGui.so.4 #14 0x2a4bc1fa in QApplicationPrivate::construct () from /usr/local/lib/qt4/libQtGui.so.4 #15 0x2a4bcbf6 in QApplication::QApplication () from /usr/local/lib/qt4/libQtGui.so.4 #16 0x29335dc9 in TrustedMain (argc=1, argv=0xbfbfd524) at CIShared.h:52 ... This looks like a libstdc++ bug that is triggered by Qt and might already be fixed in more recent 10-stable. So please try to update to 10.0-BETA3 first. My kernel and userland are r255948 (October 1st) and the ports are from r328930 (as well October 1st). Do you really think that this is to old? Yeah there have been quite a number of fixes between ALPHA1 and BETA3. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
Does sudo -u your_account VirtualBox work? This works for me and i see exactly the same backtrace on 10.0-BETA3 (approx. 1 week old) when i start directly from my user account. Lutz __ Diese E-Mail wurde aus dem Sicherheitsverbund E-Mail made in Germany versendet: [1]http://www.gmx.net/e-mail-made-in-germany References 1. http://www.gmx.net/e-mail-made-in-germany?mc=footer@textl...@emig.emig ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
Does sudo -u your_account VirtualBox work? This works for me and i see exactly the same backtrace on 10.0-BETA3 (approx. 1 week old) when i start directly from my user account. Lutz Hi, I started it in my HOME, but as root. How this is supposed to be started? Thx matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
El día Wednesday, November 27, 2013 a las 07:00:54AM +0100, Matthias Apitz escribió: Does sudo -u your_account VirtualBox work? This works for me and i see exactly the same backtrace on 10.0-BETA3 (approx. 1 week old) when i start directly from my user account. Lutz Hi, I started it in my HOME, but as root. How this is supposed to be started? Thx The command; # sudo -u guru VirtualBox let show up and error dialog box with the message Failed to create the VirtualBox COM object The application will now terminate. Details: Callee RC: NS_ERROR_ABORT (0x80004004) Thx matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
El día Wednesday, November 13, 2013 a las 04:40:17PM +0100, Bernhard Fr?hlich escribió: @/usr/local/bin/kmk_redirect -wo /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o.dep -- yasm -f elf32 -DASM_FORMAT_ELF -D__YASM__ -Worphan-labels -g dwarf2 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/PATM/ -I/usr/include/ -I/usr/X11R6/include/ -I/usr/local/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/dtrace/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/ -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -DIN_RING3 -DHC_ARCH_BITS=32 -DGC_ARCH_BITS=64 -DIN_VMM_R3 -DIN_DIS -DIN_GMM_R3 -DIN_DBG -DVBOX_IN_VMM -DVBOX_WITH_FIRST_IEM_STEP -DVBOX_WITH_REM -DVBOX_WITH_MULTI_CORE -DVBOX_WITH_PCI_PASSTHROUGH -DVBOX_WITH_SAFE_STR -DVBOX_WITH_RAW_RING1 -DVBOX_WITH_USB -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_NETSHAPER -DVBOX_WITH_RAW_MODE -DVBOX_WITH_RAW_MODE_NOT_R0 -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm -M ... We are currently investigating what is failing there and the vbox developers suggested to execute the failed command manually and add the option -e to the command line switches and post the resulting output. This would show the preprocessor file which is passed to yasm and would help to narrow it down. I have created a small shell script with the failing command, which does not give much more information: # sh kmk.sh + /usr/local/bin/kmk_redirect -wo /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o.dep -- yasm -f elf32 -DASM_FORMAT_ELF -D__YASM__ -Worphan-labels -g dwarf2 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/PATM/ -I/usr/include/ -I/usr/X11R6/include/ -I/usr/local/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/dtrace/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/ -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -DIN_RING3 -DHC_ARCH_BITS=32 -DGC_ARCH_BITS=64 -DIN_VMM_R3 -DIN_DIS -DIN_GMM_R3 -DIN_DBG -DVBOX_IN_VMM -DVBOX_WITH_FIRST_IEM_STEP -DVBOX_WITH_REM -DVBOX_WITH_MULTI_CORE -DVBOX_WITH_PCI_PASSTHROUGH -DVBOX_WITH_SAFE_STR -DVBOX_WITH_RAW_RING1 -DVBOX_WITH_USB -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_NETSHAPER -DVBOX_WITH_RAW_MODE -DVBOX_WITH_RAW_MODE_NOT_R0 -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm -M -e /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143: error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS16_size' in preprocessor /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143: warning: (AssertCompileSizeML:5) X86TSS16 is 1 bytes instead of 44 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206: error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS64_size' in preprocessor /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206: warning: (AssertCompileSizeML:5) X86TSS64 is 1 bytes instead of 136 The problems are raised by these lines in the file: /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac struc X86TSS16 .selPrevresw 1 .sp0resw 1 .ss0resw 1 .sp1resw 1 .ss1resw 1 .sp2resw 1 .ss2resw 1 .ip resw 1 .flags resw 1 .ax resw 1 .cx resw 1 .dx resw 1 .bx resw 1 .sp resw 1 .bp resw 1 .si resw 1 .di resw 1 .es resw 1 .cs resw 1 .ss resw 1 .ds resw 1 .selLdt resw 1 endstruc
Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
On Thu, Nov 14, 2013 at 10:50 AM, Matthias Apitz g...@unixarea.de wrote: El día Wednesday, November 13, 2013 a las 04:40:17PM +0100, Bernhard Fr?hlich escribió: @/usr/local/bin/kmk_redirect -wo /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o.dep -- yasm -f elf32 -DASM_FORMAT_ELF -D__YASM__ -Worphan-labels -g dwarf2 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/PATM/ -I/usr/include/ -I/usr/X11R6/include/ -I/usr/local/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/dtrace/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/ -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -DIN_RING3 -DHC_ARCH_BITS=32 -DGC_ARCH_BITS=64 -DIN_VMM_R3 -DIN_DIS -DIN_GMM_R3 -DIN_DBG -DVBOX_IN_VMM -DVBOX_WITH_FIRST_IEM_STEP -DVBOX_WITH_REM -DVBOX_WITH_MULTI_CORE -DVBOX_WITH_PCI_PASSTHROUGH -DVBOX_WITH_SAFE_STR -DVBOX_WITH_RAW_RING1 -DVBOX_WITH_USB -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_NETSHAPER -DVBOX_WITH_RAW_MODE -DVBOX_WITH_RAW_MODE_NOT_R0 -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm -M ... We are currently investigating what is failing there and the vbox developers suggested to execute the failed command manually and add the option -e to the command line switches and post the resulting output. This would show the preprocessor file which is passed to yasm and would help to narrow it down. I have created a small shell script with the failing command, which does not give much more information: # sh kmk.sh + /usr/local/bin/kmk_redirect -wo /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o.dep -- yasm -f elf32 -DASM_FORMAT_ELF -D__YASM__ -Worphan-labels -g dwarf2 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/PATM/ -I/usr/include/ -I/usr/X11R6/include/ -I/usr/local/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/dtrace/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/ -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -DIN_RING3 -DHC_ARCH_BITS=32 -DGC_ARCH_BITS=64 -DIN_VMM_R3 -DIN_DIS -DIN_GMM_R3 -DIN_DBG -DVBOX_IN_VMM -DVBOX_WITH_FIRST_IEM_STEP -DVBOX_WITH_REM -DVBOX_WITH_MULTI_CORE -DVBOX_WITH_PCI_PASSTHROUGH -DVBOX_WITH_SAFE_STR -DVBOX_WITH_RAW_RING1 -DVBOX_WITH_USB -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_NETSHAPER -DVBOX_WITH_RAW_MODE -DVBOX_WITH_RAW_MODE_NOT_R0 -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm -M -e /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143: error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS16_size' in preprocessor /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143: warning: (AssertCompileSizeML:5) X86TSS16 is 1 bytes instead of 44 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206: error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS64_size' in preprocessor /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206: warning: (AssertCompileSizeML:5) X86TSS64 is 1 bytes instead of 136 The problems are raised by these lines in the file: /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac struc X86TSS16 .selPrevresw 1 .sp0resw 1 .ss0resw 1 .sp1resw 1 .ss1resw 1 .sp2resw 1 .ss2resw 1 .ip resw 1 .flags resw 1 .ax resw 1 .cx resw 1 .dx resw 1 .bx resw 1 .sp resw 1 .bp resw 1 .si resw 1 .di resw 1 .es resw 1 .cs
Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
El día Thursday, November 14, 2013 a las 12:30:10PM +0100, Bernhard Fr?hlich escribió: It looks like the compiler should compare the size of the defined storage with some defines about X86TSS16 and X86TSS64 and does not know them... No clue how to fix this :-( Hm this output does not include the information that we were looking for. It was expected to see the yasm output of the asm file because we want to rule out that it is an yasm bug. If you look further into the definition of AssertCompileSize you will see it does a check on the size of the struct that fails because it thinks the size is 1 but it should be 136 as defined in the second parameter. It took me some time to figure out, how the yasm engine should work; I took away the /usr/local/bin/kmk_redirect part (because it only catches the output of yasm and redirekts it to a file); and, more important, one must remove the '-o file' option from the yasm call to get the preprocessor output on stdout; it is here (around 4500 lines): http://www.unixarea.de/yasm.out What makes me worry are the amount of empty lines at the beginning while parsing the file emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/asmdefs.mac but I'm not an x386 Assembler expert, only for IBM /370 main frames :-) HIH matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
[Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
Hello, This is with 10-CUR r255948 with ports as r328930 (~ 1st of October) on i386 architecture; I have unpacked the file virtualbox-cft-4.3.0-20131020.tar.gz and making emulators/virtualbox-ose gives: # make install clean BATCH=yes USE_GCC=any ... kBuild: Pass - Build Programs kBuild: Pass - Libraries kBuild: Pass - DLLs kBuild: Compiling VBoxVMM - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143: error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS16_size' in preprocessor /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143: warning: (AssertCompileSizeML:5) X86TSS16 is 1 bytes instead of 44 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206: error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS64_size' in preprocessor /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206: warning: (AssertCompileSizeML:5) X86TSS64 is 1 bytes instead of 136 kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o] Error 1 The failing command: @/usr/local/bin/kmk_redirect -wo /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o.dep -- yasm -f elf32 -DASM_FORMAT_ELF -D__YASM__ -Worphan-labels -g dwarf2 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/PATM/ -I/usr/include/ -I/usr/X11R6/include/ -I/usr/local/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/dtrace/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/ -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -DIN_RING3 -DHC_ARCH_BITS=32 -DGC_ARCH_BITS=64 -DIN_VMM_R3 -DIN_DIS -DIN_GMM_R3 -DIN_DBG -DVBOX_IN_VMM -DVBOX_WITH_FIRST_IEM_STEP -DVBOX_WITH_REM -DVBOX_WITH_MULTI_CORE -DVBOX_WITH_PCI_PASSTHROUGH -DVBOX_WITH_SAFE_STR -DVBOX_WITH_RAW_RING1 -DVBOX_WITH_USB -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_NETSHAPER -DVBOX_WITH_RAW_MODE -DVBOX_WITH_RAW_MODE_NOT_R0 -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm -M kmk: *** Deleting file `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o' kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o] Deleting file `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.lst' *** Error code 2 Stop. make: stopped in /usr/ports/emulators/virtualbox-ose Please advice. Thanks matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
