From owner-freebsd-emulation@freebsd.org  Tue Oct 22 20:38:47 2019
Return-Path: <owner-freebsd-emulation@freebsd.org>
Delivered-To: freebsd-emulation@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id C1B38164B33
 for <freebsd-emulation@mailman.nyi.freebsd.org>;
 Tue, 22 Oct 2019 20:38:47 +0000 (UTC)
 (envelope-from jkim@FreeBSD.org)
Received: from smtp.freebsd.org (smtp.freebsd.org
 [IPv6:2610:1c1:1:606c::24b:4])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits)
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "smtp.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 46yQMW4hznz4Fsy;
 Tue, 22 Oct 2019 20:38:47 +0000 (UTC)
 (envelope-from jkim@FreeBSD.org)
Received: from freefall.freebsd.org
 (static-71-168-218-4.cmdnnj.fios.verizon.net [71.168.218.4])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 (Authenticated sender: jkim/mail)
 by smtp.freebsd.org (Postfix) with ESMTPSA id 7A23117593;
 Tue, 22 Oct 2019 20:38:47 +0000 (UTC)
 (envelope-from jkim@FreeBSD.org)
Subject: Re: [package - head-amd64-default][emulators/virtualbox-ose] Failed
 for virtualbox-ose-5.2.34 in build
From: Jung-uk Kim <jkim@FreeBSD.org>
To: Michael Butler <imb@protected-networks.net>, freebsd-emulation@freebsd.org
References: <201910221733.x9MHX2po002857@beefy18.nyi.freebsd.org>
 <ef0b53fc-7a4d-b813-6eed-cfbc5a0d9a0c@protected-networks.net>
 <1a89a677-189b-e0ae-6b62-9b6da95897dc@FreeBSD.org>
Message-ID: <b63c424e-e6a3-3a7c-c990-d7de28ef6a7a@FreeBSD.org>
Date: Tue, 22 Oct 2019 16:38:46 -0400
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101
 Thunderbird/68.2.0
MIME-Version: 1.0
In-Reply-To: <1a89a677-189b-e0ae-6b62-9b6da95897dc@FreeBSD.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-emulation@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Development of Emulators of other operating systems
 <freebsd-emulation.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-emulation>, 
 <mailto:freebsd-emulation-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-emulation/>
List-Post: <mailto:freebsd-emulation@freebsd.org>
List-Help: <mailto:freebsd-emulation-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-emulation>, 
 <mailto:freebsd-emulation-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2019 20:38:47 -0000

On 19. 10. 22., Jung-uk Kim wrote:
> On 19. 10. 22., Michael Butler wrote:
>> On 10/22/19 1:33 PM, pkg-fallout@FreeBSD.org wrote:
>>
>>  <snip>
>>
>>> /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/VBoxDD/vboxssdt_cpuhotplug.hex.pre1     29:  Processor (CPU1, 0x01, 0x0, 0x0 ) { Name (_HID, "ACPI0007") Name (_UID, "SCK1-CPU0") Name (_PXM, 0x00) 
>>> Warning  3168 -                                                                         Legacy Processor() keyword detected. Use Device() keyword instead. ^ 
>>>
>>> /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/VBoxDD/vboxssdt_cpuhotplug.hex.pre1     29:  Processor (CPU1, 0x01, 0x0, 0x0 ) { Name (_HID, "ACPI0007") Name (_UID, "SCK1-CPU0") Name (_PXM, 0x00) 
>>> Error    6167 -                                                                                                                                              _UID inside processor declaration must be an integer ^  (found a string)
>>
>> It seems that SVN r514730 update to sysutils/acpica-tools has broken
>> iasl's compatibility with VBox dsl sources :-(
> 
> Actually, we use iasl from base.  Therefore, head after r353764 is affected.
> 
> https://svnweb.freebsd.org/changeset/base/353764
> 
> It is a VirtualBox bug and I am working on it.

Please try the attached patch.

Jung-uk Kim