From owner-freebsd-emulation@FreeBSD.ORG Thu Nov 14 14:19:34 2013 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C10F7A15; Thu, 14 Nov 2013 14:19:34 +0000 (UTC) Received: from sh4-5.1blu.de (sh4-5.1blu.de [178.254.11.41]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8501E2E7E; Thu, 14 Nov 2013 14:19:34 +0000 (UTC) Received: from ftp51246-2575596 by sh4-5.1blu.de with local (Exim 4.76) (envelope-from ) id 1Vgxlb-0003zg-9Y; Thu, 14 Nov 2013 15:19:31 +0100 Date: Thu, 14 Nov 2013 15:19:31 +0100 From: Matthias Apitz To: Bernhard Froehlich , "freebsd-emulation@freebsd.org" Subject: Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor Message-ID: <20131114141931.GA4100@sh4-5.1blu.de> References: <20131113122618.GA30563@sh4-5.1blu.de> <20131114095030.GA26987@sh4-5.1blu.de> <20131114124644.GA27601@sh4-5.1blu.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20131114124644.GA27601@sh4-5.1blu.de> X-Operating-System: FreeBSD 7.0-RELEASE (i386) User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: Matthias Apitz List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 14:19:34 -0000 El día Thursday, November 14, 2013 a las 01:46:44PM +0100, Matthias Apitz escribió: > 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 :-) btw: why yasm does not complain about line 733 in yasm.out: X86FXSTATE_size EQU $ - X86FXSTATE but about line 765: X86TSS16_size EQU $ - X86TSS16 i.e. from where it knows X86FXSTATE_size, but not X86TSS16_size? matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: guru@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