Skip to content

Upgraded to .net core 1.0.0, changed versioning scheme #19

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

Merged
merged 1 commit into from
Jun 28, 2016

Conversation

SapientGuardian
Copy link
Owner

No description provided.

@eByte23
Copy link

eByte23 commented Jun 27, 2016

Looks good :D

@SapientGuardian
Copy link
Owner Author

Not quite. Having trouble getting the latest sdk on Travis.

@eByte23
Copy link

eByte23 commented Jun 28, 2016

Ahh right, looks like progress now though?

@eByte23
Copy link

eByte23 commented Jun 28, 2016

Failing on trying to get System.Security.Cryptography.Native now

@SapientGuardian
Copy link
Owner Author

I think we might need to trigger a brew install openssl on the osx build, per https://github.com/dotnet/coreclr/issues/1502. Not sure how we've escaped the problem thus far.

@eByte23
Copy link

eByte23 commented Jun 28, 2016

That's interesting have you tried building on linux your self if not I can now?

@SapientGuardian
Copy link
Owner Author

The linux build is fine, it's the osx build that has the problem. I don't have a mac to test with.

@eByte23
Copy link

eByte23 commented Jun 28, 2016

Ahh that explains things! luckily I do so I'll give it a shot and see what I get, well sorta.

@eByte23
Copy link

eByte23 commented Jun 28, 2016

Reproduced all steps got the exact same error, did brew install openssl still failed.
I will try downloading the offical mac package now

@eByte23
Copy link

eByte23 commented Jun 28, 2016

Okay we need to do

brew update
brew install openssl
brew link --force openssl

if you don't do the last link command it will still fail.

Now builds for me, still don't understand how we escaped it until now, unless they changed something

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

Successfully merging this pull request may close these issues.

2 participants