Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows builds are missing libwinpthread-1.dll #36

Closed
xyzz opened this issue Dec 9, 2016 · 5 comments · Fixed by #45
Closed

Windows builds are missing libwinpthread-1.dll #36

xyzz opened this issue Dec 9, 2016 · 5 comments · Fixed by #45
Labels

Comments

@xyzz
Copy link
Contributor

xyzz commented Dec 9, 2016

As a result, they don't work at all.

---------------------------
arm-vita-eabi-gcc-6.2.0.exe - System Error
---------------------------
The program can't start because libwinpthread-1.dll is missing from your computer. Try reinstalling the program to fix this problem. 
---------------------------
OK   
---------------------------

Worked around on msys2 by using mingw64 and installing the mingw64/mingw-w64-x86_64-libwinpthread-git package.

@devnoname120
Copy link
Member

@codestation How can we statically link these libraries for the Windows build?

@codestation
Copy link
Contributor

codestation commented Jun 30, 2017

libwinpthread-1.dll isn't linked when built using Ubuntu Xenial (16.04 LTS). It is possible switch to the xenial image on travis?

I built the sdk twice on a trusty and xenial docker image to confirm, ldd output below:

Built using ubuntu:xenial

$ ldd xenial/bin/arm-vita-eabi-gcc-6.2.0.exe
        ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x76fd0000)
        kernel32.dll => /c/Windows/system32/kernel32.dll (0x76eb0000)
        KERNELBASE.dll => /c/Windows/system32/KERNELBASE.dll (0x7fefcd50000)
        ADVAPI32.dll => /c/Windows/system32/ADVAPI32.dll (0x7fefe940000)
        msvcrt.dll => /c/Windows/system32/msvcrt.dll (0x7feff240000)
        sechost.dll => /c/Windows/SYSTEM32/sechost.dll (0x7fefe770000)
        RPCRT4.dll => /c/Windows/system32/RPCRT4.dll (0x7fefea20000)
        USER32.dll => /c/Windows/system32/USER32.dll (0x76db0000)
        GDI32.dll => /c/Windows/system32/GDI32.dll (0x7fefe790000)
        LPK.dll => /c/Windows/system32/LPK.dll (0x7fefd600000)
        USP10.dll => /c/Windows/system32/USP10.dll (0x7fefe5c0000)

Built using ubuntu:trusty

$ ldd trusty/bin/arm-vita-eabi-gcc-6.2.0.exe
        ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x76fd0000)
        kernel32.dll => /c/Windows/system32/kernel32.dll (0x76eb0000)
        KERNELBASE.dll => /c/Windows/system32/KERNELBASE.dll (0x7fefcd50000)
        ADVAPI32.dll => /c/Windows/system32/ADVAPI32.dll (0x7fefe940000)
        msvcrt.dll => /c/Windows/system32/msvcrt.dll (0x7feff240000)
        sechost.dll => /c/Windows/SYSTEM32/sechost.dll (0x7fefe770000)
        RPCRT4.dll => /c/Windows/system32/RPCRT4.dll (0x7fefea20000)
        libwinpthread-1.dll => /mingw64/bin/libwinpthread-1.dll (0x64940000)
        USER32.dll => /c/Windows/system32/USER32.dll (0x76db0000)
        GDI32.dll => /c/Windows/system32/GDI32.dll (0x7fefe790000)
        LPK.dll => /c/Windows/system32/LPK.dll (0x7fefd600000)
        USP10.dll => /c/Windows/system32/USP10.dll (0x7fefe5c0000)

@devnoname120
Copy link
Member

Unfortunately, Travis doesn't support Ubuntu Xenial. We could use a Docker container but in addition to the increased complexity for maintenance, our builds are already often timing out so it would be even worse with Docker.

I wonder if there is another way to avoid this dependency.

@devnoname120
Copy link
Member

@codestation Note that since then Travis-CI has increased the maximum running time of vitasdk/autobuilds to 90 minutes. Building in a Ubuntu Xenial container should not time out.

@devnoname120
Copy link
Member

Note that Travis-CI now supports Ubuntu Xenial. Statically linking pthread and removing the DLLs would fix issues such as #63.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants