[Bug 275619] emulators/wine: Cannot create new win64 WINEPREFIX

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275619

            Bug ID: 275619
           Summary: emulators/wine: Cannot create new win64 WINEPREFIX
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: gerald@FreeBSD.org
          Reporter: dmk@ncf.ca
             Flags: maintainer-feedback?(gerald@FreeBSD.org)
          Assignee: gerald@FreeBSD.org

Created attachment 246890
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=246890&action=edit
WINEDEBUG=all winecfg and directory listing of new prefix

I just upgraded to FreeBSD 14.0-RELEASE-p1 & wine-8.0.2,1. I couldn't get any
of my 64bit wine programs to run. So, I decided to start with fresh prefixes.
When I try to create a new prefix, I get this:

WINEPREFIX=~/.local/share/wineprefixes/magic winecfg
wine: created the configuration directory
'/home/dwayne/.local/share/wineprefixes/magic'
0024:fixme:ntdll:create_logical_proc_info stub
0024:fixme:ntdll:init_cpu_info Failed to get logical processor information,
status 0xc0000002.
002c:fixme:ntdll:create_logical_proc_info stub
002c:fixme:ntdll:init_cpu_info Failed to get logical processor information,
status 0xc0000002.
wine: failed to open L"C:\\windows\\system32\\wineboot.exe": c0000135
0024:err:environ:run_wineboot failed to start wineboot c0000135
wine: could not load kernel32.dll, status c0000135

I've added an attachment with a WINEDEBUG=all run. I also did a directory
listing; the new WINEPREFIX isn't fully populated. I thought that would be
worth noting. It's all in the attached text.

I have 32bit (i386) wine installed to my local user using pkg32.sh, and all of
my 32bit windows apps still run just fine (such as Acrobat Reader). I am also
able to create new win32 prefixes using WINEPREFIX=<NEWPREFIX> WINEARCH=win32
winecfg .

-- 
You are receiving this mail because:
You are the assignee for the bug.