Skip to content

Fix singlefilehost build in non-portable mode - #42415

Merged
1 commit merged into
dotnet:masterfrom
omajid:singlefilehost-non-portable-ssl
Sep 23, 2020
Merged

Fix singlefilehost build in non-portable mode#42415
1 commit merged into
dotnet:masterfrom
omajid:singlefilehost-non-portable-ssl

Conversation

@omajid

@omajidomajid commented Sep 17, 2020

Copy link
Copy Markdown
Member

The singlefilehost needs to follow libraries build in terms of how it links to OpenSSL: if it's a non-portable build, the singlefilehost needs to link to OpenSSL via linker arguments.

The installer also needs to have FEATURE_DISTRO_AGNOSTIC_SSL defined just like it is defined for the libraries build.

Fixes: #41768

@ghost

Copy link
Copy Markdown

Tagging subscribers to this area: @vitek-karas, @agocke
See info in area-owners.md if you want to be subscribed.

@ghost

Copy link
Copy Markdown

Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @jeffhandley
See info in area-owners.md if you want to be subscribed.

@omajid

Copy link
Copy Markdown
MemberAuthor

Should I look into adding a CI configuration that exercises runtime build in non-portable mode to catch such regressions earlier for next time around?

@omajid
omajid marked this pull request as ready for review September 18, 2020 12:10
@dagood

Copy link
Copy Markdown
Member

Should I look into adding a CI configuration that exercises runtime build in non-portable mode to catch such regressions earlier for next time around?

We're planning to do this with arcade-powered source-build. The plan is end-to-end, even--so it also validates dotnet/installer being able to take in a non-portable RID, etc. There's a bit more info at dotnet/source-build#1722.

That said, getting a non-portable config into dotnet/runtime would still be useful in the short term, because we obviously don't have arcade-powered source-build yet. 🙂

@janvorlijanvorli left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A nit - can you please remove this message?

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

The singilefilehost needs to follow the libraries build in terms of how
it links to OpenSSL: if it's a non-portable build, the singlefilehost
needs to link to OpenSSL via linker arguments.
The installer also needs to have FEATURE_DISTRO_AGNOSTIC_SSL defined
just like it is defined for the libraries build.
Fixes: dotnet#41768
@omajid
omajidforce-pushed the singlefilehost-non-portable-ssl branch from 7b213c3 to 3d325d4CompareSeptember 21, 2020 15:09
@omajid

Copy link
Copy Markdown
MemberAuthor

Thanks for the quick review and merging this!

@janvorli

Copy link
Copy Markdown
Member

I have noticed that two test legs have failed. I have restarted them.

@ghost

Copy link
Copy Markdown

Hello @janvorli!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost
ghost merged commit eac3423 into dotnet:masterSep 23, 2020
omajid added a commit to omajid/dotnet-source-build that referenced this pull request Sep 23, 2020
omajid added a commit to omajid/dotnet-source-build that referenced this pull request Sep 23, 2020
@ghostghost locked as resolved and limited conversation to collaborators Dec 7, 2020
This pull request was closed.
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Source-build OpenSSL linker errors

5 participants

@omajid@dagood@janvorli@maryamariyan@Dotnet-GitSync-Bot