3rd party dependencies: Build against platform libraries instead of the embedded libraries

[dviererbe]

On Ubuntu we currently use mostly the embedded libraries included in the source, to build .NET. Optimally we want to use the library packages of the Ubuntu Archive.

A shallow investigation by @mirespace and me showed that there are:

1. mentioned 3rd party dependencies we could not find in the source; e.g. Slicing-by-8:
   • We downloaded the Slicing-by-8 source from https://sourceforge.net/projects/slicing-by-8/ as mentioned by https://github.com/dotnet/runtime/blob/main/THIRD-PARTY-NOTICES.TXT#L23
   • We could not find the crc.c, crc.h, 8x256_tables.c file
2. references to older versions of 3rd party dependencies; e.g. https://github.com/dotnet/runtime/blob/main/src/coreclr/pal/inc/rt/cpp/xmmintrin.h references llvm-3.9/clang-3.9.1

I have to correct my statement that brotli was modified. There is a diff between the files contained in the repository (here) and the released tarball (here). The release tarball does not contain the files:

• fuzz/*
• common/dictionary.bin
• common/dictionary.bin.br

But, if Microsoft is aware of modified 3rd party dependencies, we should look into getting them merged upstream.

This issue is not mission critical, but long-term we would like to patch the embedded libraries out; I will start a deeper investigation over the next weeks.

Also, @omajid you mentioned in this weeks meeting that there is a flag to enable using the platform libraries. Can you provide more details about that flag?

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[MichaelSimons]

[Triage] There are two parts to this issue. One is on the source-build side around documentation and possibly providing a single option to use the platform libraries. The second part is more specific to the runtime around the specific 3rd party dependencies.

[MichaelSimons]

Logged dotnet/source-build#3563 to track the source-build side of this. Transferring this to runtime to respond to the specific runtime questions.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

On Ubuntu we currently use mostly the embedded libraries included in the source, to build .NET. Optimally we want to use the library packages of the Ubuntu Archive.

A shallow investigation by @mirespace and me showed that there are:

1. mentioned 3rd party dependencies we could not find in the source; e.g. Slicing-by-8:
   • We downloaded the Slicing-by-8 source from https://sourceforge.net/projects/slicing-by-8/ as mentioned by https://github.com/dotnet/runtime/blob/main/THIRD-PARTY-NOTICES.TXT#L23
   • We could not find the crc.c, crc.h, 8x256_tables.c file
2. references to older versions of 3rd party dependencies; e.g. https://github.com/dotnet/runtime/blob/main/src/coreclr/pal/inc/rt/cpp/xmmintrin.h references llvm-3.9/clang-3.9.1

I have to correct my statement that brotli was modified. There is a diff between the files contained in the repository (here) and the released tarball (here). The release tarball does not contain the files:

• fuzz/*
• common/dictionary.bin
• common/dictionary.bin.br

But, if Microsoft is aware of modified 3rd party dependencies, we should look into getting them merged upstream.

This issue is not mission critical, but long-term we would like to patch the embedded libraries out; I will start a deeper investigation over the next weeks.

Also, @omajid you mentioned in this weeks meeting that there is a flag to enable using the platform libraries. Can you provide more details about that flag?

Author:	dviererbe
Assignees:	-
Labels:	area-Infrastructure, untriaged, needs-area-label
Milestone:	-