Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Nov 2013 16:40:17 +0100
From:      =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@FreeBSD.org>
To:        Matthias Apitz <guru@unixarea.de>
Cc:        "freebsd-emulation@freebsd.org" <freebsd-emulation@freebsd.org>
Subject:   Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor
Message-ID:  <CAE-m3X3n473dtXnrHTP6yMnKc1T=q93AnE=5oDhW7m=b_o_tRg@mail.gmail.com>
In-Reply-To: <20131113122618.GA30563@sh4-5.1blu.de>
References:  <20131113122618.GA30563@sh4-5.1blu.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 13, 2013 at 1:26 PM, Matthias Apitz <guru@unixarea.de> wrote:
>
> 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

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.

-- 
Bernhard Froehlich
http://www.bluelife.at/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-m3X3n473dtXnrHTP6yMnKc1T=q93AnE=5oDhW7m=b_o_tRg>