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

Build error on Windows 7 #133

Closed
jebej opened this issue Mar 17, 2018 · 7 comments
Closed

Build error on Windows 7 #133

jebej opened this issue Mar 17, 2018 · 7 comments

Comments

@jebej
Copy link

jebej commented Mar 17, 2018

INFO: Building MbedTLS                                                                                                                                    
Info: Downloading https://github.com/quinnj/MbedTLSBuilder/releases/download/v0.6/MbedTLS.x86_64-w64-mingw32.tar.gz to C:\Users\Jeremy\.julia\v0.6\MbedTLS
\deps\usr\downloads\MbedTLS.x86_64-w64-mingw32.tar.gz...                                                                                                  
Exception setting "SecurityProtocol": "Cannot convert null to type "System.Net.SecurityProtocolType" due to invalid enumeration values. Specify one of th 
e following enumeration values and try again. The possible enumeration values are "Ssl3, Tls"."                                                           
At line:1 char:35                                                                                                                                         
+ [System.Net.ServicePointManager]:: <<<< SecurityProtocol =                                                                                              
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException                                                                                  
    + FullyQualifiedErrorId : PropertyAssignmentException                                                                                                 
                                                                                                                                                          
Exception calling "DownloadFile" with "2" argument(s): "The underlying connection was closed: An unexpected error occurred on a send."                    
At line:4 char:24                                                                                                                                         
+ $webclient.DownloadFile <<<< ("https://github.com/quinnj/MbedTLSBuilder/releases/download/v0.6/MbedTLS.x86_64-w64-mingw32.tar.gz", "C:\Users\Jeremy\.ju 
lia\v0.6\MbedTLS\deps\usr\downloads\MbedTLS.x86_64-w64-mingw32.tar.gz")                                                                                   
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException                                                                             
    + FullyQualifiedErrorId : DotNetMethodException                                                                                                       
                                                                                                                                                          
====================================================================[ ERROR: MbedTLS ]====================================================================
                                                                                                                                                          
                                                                                                                                                          
LoadError: Could not download https://github.com/quinnj/MbedTLSBuilder/releases/download/v0.6/MbedTLS.x86_64-w64-mingw32.tar.gz to C:\Users\Jeremy\.julia\
v0.6\MbedTLS\deps\usr\downloads\MbedTLS.x86_64-w64-mingw32.tar.gz                                                                                         
while loading C:\Users\Jeremy\.julia\v0.6\MbedTLS\deps\build.jl, in expression starting on line 40
@quinnj
Copy link
Member

quinnj commented Mar 18, 2018

@staticfloat @Keno ^^

@staticfloat
Copy link
Member

You need to install Windows Management Framework 3 (that is the package that ships PowerShell) and .Net Framework 4.5. This will enable powershell to download files from websites that use newer TLS versions.

@jebej
Copy link
Author

jebej commented Mar 19, 2018

For whatever reason, management framework 3 did not install, but management frameword 4 did: https://www.microsoft.com/en-us/download/details.aspx?id=40855

@samoconnor
Copy link
Contributor

So, should this issue be closed?
Or, should the build script install this "management framework" dependancy automatically?
Or, prompt the user to do that?

@tkelman
Copy link
Contributor

tkelman commented Mar 20, 2018

Between this and #132, it's pretty clear to me that BinaryProvider causes way more problems than it solves, in its current state, for this package. For the time being it would be better for this package to go back to using BinDeps, since that was actually a no-op most of the time and worked well here, and let these problems be worked out elsewhere.

@quinnj
Copy link
Member

quinnj commented Mar 20, 2018

No way. BinDeps code is total obscure blackbox stuff and would revert the library back to outdated versions that ship w/ julia. I'd much rather spend my time pestering @staticfloat and @Keno to make BinaryProvider.jl as smooth as possible on every platform. I don't think it's particularly nice to make windows users install something or another, so if that can be automated or prompted for, that'd be great, or maybe BinaryProvider just needs to ship w/ its own curl or something. We're definitely not going back though; the future is bindeps2, even if we have to iron out a few wrinkles along the way.

@tkelman
Copy link
Contributor

tkelman commented Mar 20, 2018

The versions that ship with Julia aren't all that outdated, they're certainly more recent than the system packages that your current build.jl code allows to load. Keep using things that worked until their replacements actually work better. They don't at the moment, and your users are the ones who suffer for it.

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

No branches or pull requests

5 participants