[Bug 34172] 64-bit MiKTeX 2.9 build 4503 fails to install

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=34172

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download, win64
                URL|                            |http://bay.uchicago.edu/tex
                   |                            |-archive/systems/win32/mikt
                   |                            |ex/setup/setup-2.9.4503-x64
                   |                            |.exe
                 CC|                            |focht at gmx.net
            Summary|Failure to install MiKTeX   |64-bit MiKTeX 2.9 build
                   |2.9                         |4503 fails to install

--- Comment #7 from Anastasius Focht <focht at gmx.net> ---
Hello folks,

--- quote ---
Yes, MiKTeX 2.9/32bit installed without errors using Wine 1.7.51 (under Xubuntu
14.04).  Successfully edited and compiled a document in WinEdt8.4 that called
to MiKTeX.
--- quote ---

please don't mix 32-bit and 64-bit installer issues together unless you can
prove that both suffer from the same issue.
The bug was targeting 64-bit (see initial backtrace).

You have to retest against the original 64-bit installer even if Austin asked
for 32-bit results which kind of lead to confusion here.

--- snip ---
C:\Program Files (x86)\MT2.9\setup-2.9.4503-x64.exe
--- snip ---

I'm also wondering why the 64-bit bootstrapper installer is living here?
Did you put it there? That's the one that is supposed to get manually
downloaded and run from some 'Downloads' directory.

Out of curiosity I went back in time and built myself a 64-bit Wine 1.6 (with
some post-fixes to repair 64-bit build breakage).

Well, the bootstrapper installer succeeded to install MiKTeX 2.9 without any
errors in clean 64-bit WINEPREFIX.

Unless you did something differently (that's why you always need to state
*exact* installer steps) you might have suffered from a broken WINEPREFIX or
broken Wine build (Ubuntu, yes) at that time.

There is a problem in post-install step (bug 35092):

--- snip ---
...
002b:Call KERNEL32.CreateProcessW(045ac4e0 L"C:\\Program Files\\MiKTeX
2.9\\miktex/bin/x64\\initexmf.exe",045ac0d0 L"\"C:\\Program Files\\MiKTeX
2.9\\miktex/bin/x64\\initexmf.exe\" --common-install=\"C:\\Program
Files\\MiKTeX 2.9\" --rmfndb --admin --log-file=\"C:\\Program Files\\MiKTeX
2.9\\miktex\\config\\uninst.log\"
--verbose",00000000,00000000,00000001,08000000,00000000,00000000,045abcd0,06e46bd0)
ret=1400acdc4 
...
0032:Call KERNEL32.__wine_kernel_init() ret=7f8b5b769db5
002b:Ret  KERNEL32.CreateProcessW() retval=00000001 ret=1400acdc4
...
0032:Call KERNEL32.SetEnvironmentVariableW(0023e390 L"MIKTEX_LOG_DIR",0023df80
L"C:\\users\\focht\\Local Settings\\Application
Data\\MiKTeX\\2.9\\miktex\\log") ret=7f8b53a3f65a
0032:Ret  KERNEL32.SetEnvironmentVariableW() retval=00000001 ret=7f8b53a3f65a
...
0032:Call KERNEL32.CreateFileW(002340f0 L"C:\\users\\focht\\Local
Settings\\Application
Data\\MiKTeX\\2.9\\miktex\\log\\initexmf.log",00000000,00000007,00000000,00000003,02000000,00000000)
ret=60039979
0032:Ret  KERNEL32.CreateFileW() retval=ffffffffffffffff ret=60039979
...
0032:Call KERNEL32.CreateFileW(00238320 L"C:\\users\\focht\\Local
Settings\\Application
Data\\MiKTeX\\2.9\\miktex\\log\\initexmf.log",40000000,00000007,00000000,00000004,7fff00000000,00000000)
ret=60039979
0032:Ret  KERNEL32.CreateFileW() retval=ffffffffffffffff ret=60039979
0032:Call KERNEL32.GetLastError() ret=60039988
0032:Ret  KERNEL32.GetLastError() retval=00000003 ret=60039988
...
0032:Call msvcr120._CxxThrowException(0023c3d0,628105f0) ret=626c9782
0032:Call KERNEL32.RaiseException(e06d7363,00000001,00000003,0023c2c0)
ret=7f8b53a33c5c
0032:trace:seh:raise_exception code=e06d7363 flags=1 addr=0x7b88c7f4
ip=7b88c7f4 tid=0032
0032:trace:seh:raise_exception  info[0]=0000000019930520
0032:trace:seh:raise_exception  info[1]=000000000023c3d0
0032:trace:seh:raise_exception  info[2]=00000000628105f0
0032:trace:seh:raise_exception  rax=000000007b8707f0 rbx=0000000000269850
rcx=000000000023c0c0 rdx=0000000000000018
0032:trace:seh:raise_exception  rsi=000000000023c2c0 rdi=000000000023c0e0
rbp=000000000023c210 rsp=000000000023c0a0
0032:trace:seh:raise_exception   r8=0000000000000003  r9=000000000023c2c0
r10=0000000000000001 r11=0000003cb618dad0
0032:trace:seh:raise_exception  r12=0000000000000001 r13=0000000062780f48
r14=000000000023d668 r15=0000000000269850 
...
0032:Call msvcr120._XcptFilter(e06d7363,0023abf0) ret=140023ac2
0032:trace:seh:_XcptFilter (e06d7363,0x23abf0)
0032:Ret  msvcr120._XcptFilter() retval=00000000 ret=140023ac2
0032:Ret  ntdll.__C_specific_handler() retval=00000001 ret=7f8b5b7a621c 
...
0032:Call KERNEL32.UnhandledExceptionFilter(0023ad50) ret=7f8b5b7d6339
wine: Unhandled exception 0xe06d7363 in thread 32 at address 0x7b88c7f4 (thread
0032), starting debugger... 
...
002b:Call KERNEL32.OutputDebugStringW(06f1b3c0 L"300275
[setup-2.9.4503-x64.setup]: Unhandled exception: C++ exception(object =
0x0023c3d0, type = 0x628105f0) in 64-bit code (0x000000007b88c7f4).\n")
ret=140067f63 
--- snip ---

This worked in Wine 1.6 because the bundled native VC++ 2013 runtime is used
('msvcr120') - corresponding Wine builtins were not present at that time.

$ sha1sum setup-2.9.4503-x64.exe 
399c34d42fd2c2e7e014ea40bfc1f52bc54a2535  setup-2.9.4503-x64.exe

$ du -sh setup-2.9.4503-x64.exe 
9.3M    setup-2.9.4503-x64.exe

$ wine --version
wine-1.7.52

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.