-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Feature/openssl 1.0.1k #289
Conversation
Good news, they have finally fixed the EVP message! |
Another good news: keypress patch should be no longer floated, because it is included in 1.0.1k! |
@bnoordhuis: please check that your x32 changes are still in. I have used opensslconf from the origin/v1.x, so I assume - yes. |
Can you make the CI check this PR? I suspect it's going to break the Windows build because of the removal of (at least) x86_64-win32-masm.asm. |
@bnoordhuis: appears to be building fine on windows. |
This PR also seems to break parallel/test-https-foafssl on Windows. |
@bnoordhuis: pushed update for GYP. |
@bnoordhuis : regarding foafssl - it is not completely evident to me that this is caused by this PR. |
@indutny Would you mind also updating https://github.com/iojs/io.js/blob/v1.x/deps/openssl/asm/Makefile? I noticed some asm files er axed in this release. |
Building x64 on windows:
|
@piscisaureus could you please try it again with a new commit? |
Trying |
@piscisaureus do you want me to revert it? |
@indutny no, it works. That asm file I created was derived from the gcc asm implementation, but since that file has been updated since it seems safer to exclude my own version. Go ahead and land. |
Ok, any objections @bnoordhuis ? |
Well, I still don't get why parallel/test-https-foafssl is failing now when it was passing before. |
@bnoordhuis let's give it another spin on jenkins? https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/49/ |
@bnoordhuis seems to be timeout-ing anyway. @piscisaureus does it terminate when you run it outside of the test suite? ( |
That'd be |
brave enough to land this prior to 1.0.0 or should we hold off? |
@piscisaureus You mean it hangs with or without this PR applied? If it's without, then the failure is not a regression and this PR should be good to go. |
Going to see it myself. |
Original source: http://openssl.6102.n7.nabble.com/PATCH-s-client-Fix-keypress-requirement-with-redirected-input-on-Windows-td46787.html Reviewed-By: Fedor Indutny <fedor@indutny.com>
Stupid me, I thought that the patch was included, but it was the artifact of cherry-pick which has disappeared after |
jenkins is good with it now. @bnoordhuis could you please land it if it LGTY? |
I carefully scrutinized each and every one of those +1,984 −5,363 changed lines. LGTM! |
PR-URL: #289 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Backport of: openssl/openssl@5c5e7e Original commit message: Fix build failure on Windows due to undefined cflags identifier Reviewed-by: Tim Hudson <tjh@openssl.org> PR-URL: #289 Reviewed-By: Fedor Indutny <fedor@indutny.com>
PR-URL: #289 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: #289 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: nodejs/node#289 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Backport of: openssl/openssl@5c5e7e Original commit message: Fix build failure on Windows due to undefined cflags identifier Reviewed-by: Tim Hudson <tjh@openssl.org> PR-URL: nodejs/node#289 Reviewed-By: Fedor Indutny <fedor@indutny.com>
PR-URL: nodejs/node#289 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: nodejs/node#289 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: nodejs/node#289 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: nodejs/node#289 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: nodejs/node#289 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: nodejs/node#289 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
cc @bnoordhuis