build_exe.bat hangs with "Building and testing IO-Socket-SSL-2.071 ..."

Open
#286 9 comments 0 reactions 1 assignee View on GitHub

@gilleslamiral is already working on this.

Since Jun 6, 2021.

Assessment

This issue has not been assessed yet.

Description

Build Windows

Hello, I just pulled the code and tried to build a Windows executable with build_exe.bat but it hangs:

...
Updating IO::Socket::INET 1.45                                                             
DOING cpanm IO::Socket::INET                                                               
IO::Socket::INET is up to date. (1.45)                                                     
DONE cpanm IO::Socket::INET                                                                
Updating IO::Socket::INET6 2.72                                                            
DOING cpanm IO::Socket::INET6                                                              
IO::Socket::INET6 is up to date. (2.72)                                                    
DONE cpanm IO::Socket::INET6                                                               
Updating IO::Socket::SSL 2.067                                                             
DOING cpanm IO::Socket::SSL                                                                
--> Working on IO::Socket::SSL                                                             
Fetching http://www.cpan.org/authors/id/S/SU/SULLR/IO-Socket-SSL-2.071.tar.gz ... OK       
Configuring IO-Socket-SSL-2.071 ... OK                                                     
Building and testing IO-Socket-SSL-2.071 ...                                               

Any idea what this might be caused by and how I can fix it?
I am using Strawberry Perl 5.30.2 on Windows 10.
Thanks!

Dominant language
Shell
Stars
4.2k
Forks
531
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from imapsync/imapsync

All issues in imapsync/imapsync

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.