On 19. 10. 22., Jung-uk Kim wrote:
> On 19. 10. 22., Jung-uk Kim wrote:
>> On 19. 10. 22., Jung-uk Kim wrote:
>>> On 19. 10. 22., Jung-uk Kim wrote:
>>>> On 19. 10. 22., Michael Butler wrote:
>>>>> On 10/22/19 1:33 PM, pkg-fall...@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.
>>
>> Sorry, really attaching the patch.
> 
> Arg...  The attachment was stripped.  Trying again.

I went ahead and committed it.  Let me know if it still has issues.

Jung-uk Kim
_______________________________________________
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Reply via email to