Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 18, 2023

Backport of #92878 to release/8.0

/cc @vitek-karas

Customer Impact

None

Testing

Verified that I can build the repo on a machine with new VS

Risk

Basically none - it's just suppressing a warning caused by a new version of the C++ compiler. The official build won't use that.

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

The latest build of VS carries a C/C++ compiler which produces warning C5271:
```
src\native\corehost\test\ijw\ijw.cpp(6): warning C5271: consider replacing #using <System.Console.dll>  with command line argument /FU "F:\dotnet\runtime2\.dotnet\packs\Microsoft.NETCore.App.Ref\8.0.0-rc.1.23414.4\ref\net8.0\System.Console.dll"
src\native\corehost\test\ijw\ijw.cpp(7): warning C5271: consider replacing #using <System.Runtime.Loader.dll>  with command line argument /FU "F:\dotnet\runtime2\.dotnet\packs\Microsoft.NETCore.App.Ref\8.0.0-rc.1.23414.4\ref\net8.0\System.Runtime.Loader.dll"
```

This breaks the build on Windows. For now I'm disabling the warning as the real fix is more complex (we would need to calculate the path to the required assemblies in CMake somehow).
@ghost ghost added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Oct 18, 2023
@vitek-karas vitek-karas self-assigned this Oct 18, 2023
Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

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

approved. please get a code review. once ready we can merge as tell mode.

cc @carlossanlop

@jeffschwMSFT jeffschwMSFT added the Servicing-approved Approved for servicing release label Oct 18, 2023
@jeffschwMSFT jeffschwMSFT added this to the 8.0.0 milestone Oct 18, 2023
@jeffschwMSFT jeffschwMSFT added area-AssemblyLoader-coreclr and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Oct 18, 2023
@ghost
Copy link

ghost commented Oct 18, 2023

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

Issue Details

Backport of #92878 to release/8.0

/cc @vitek-karas

Customer Impact

None

Testing

Verified that I can build the repo on a machine with new VS

Risk

Basically none - it's just suppressing a warning caused by a new version of the C++ compiler. The official build won't use that.

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

Author: github-actions[bot]
Assignees: vitek-karas
Labels:

Servicing-approved, area-AssemblyLoader-coreclr, needs-area-label

Milestone: 8.0.0

@carlossanlop
Copy link
Contributor

@jkoritzinsky since you signed-off the main PR, can you also sign-off this backport?

@carlossanlop carlossanlop merged commit f897438 into release/8.0 Oct 18, 2023
@carlossanlop carlossanlop deleted the backport/pr-92878-to-release/8.0 branch October 18, 2023 17:07
@ghost ghost locked as resolved and limited conversation to collaborators Nov 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants