[libcoro] New Port

[chausner]

This adds libcoro 0.9 as a new port.

This library does not support Windows. Also, CI builds x64-osx are disabled because the GCC compiler version is too old.

• Changes comply with the maintainer guide
• The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
• Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
• The versioning scheme in vcpkg.json matches what upstream says.
• The license declaration in vcpkg.json matches what upstream says.
• The installed as the "copyright" file matches what upstream says.
• The source code of the component installed comes from an authoritative source.
• The generated "usage text" is accurate. See adding-usage for context.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is in the new port's versions file.
• Only one version is added to each modified port's versions file.

[chausner]

I am wondering if we should include !osx in supports given that Clang is not supported by the library and it is the default compiler on macOS? The library itself might be compatible to macOS, though, if a recent version of gcc is used.

[vicroms]

As it is, the library is not being tested in any way in CI.
We should wait to merge until a VM update allows us to test this (at least on Linux).

Upstream requirements

    g++10.2.1
    g++10.3.1

Track: microsoft/azure-pipelines-agent#3834

[FrankXie05]

Waiting for the vm to update, temporarily turning to draft status. Once the update is complete, it will be retested.

[dg0yt]

@chausner Could you please sync the branch master? :)

Done! But it seems some of the CI builds are stuck..

Just add an empty commit to restart them.

[chausner]

@chausner Could you please sync the branch master? :)

Done! But it seems some of the CI builds are stuck..

Just add an empty commit to restart them.

Done. The x64_linux pipeline failed due to some unrelated build error of llvm.

[FrankXie05]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[FrankXie05]

/usr/include/c++/11/atomic: In member function ‘bool std::atomic<_Tp>::compare_exchange_weak(_Tp&, _Tp, std::memory_order, std::memory_order)’:
/usr/include/c++/11/atomic:323:9: error: there are no arguments to ‘__is_valid_cmpexch_failure_order’ that depend on a template parameter, so a declaration of ‘__is_valid_cmpexch_failure_order’ must be available [-fpermissive]
  323 |         __glibcxx_assert(__is_valid_cmpexch_failure_order(__f));
      |         ^~~~~~~~~~~~~~~~

install-x64-linux-dbg-out.log

It seems that it is still due to the problem of gcc version. cc @BillyONeal @vicroms

[chausner]

@FrankXie05 Could you please have another look? I updated the library to 0.9 and it appears to succeed in CI now. The two errors in CI seem unrelated:

REGRESSION: pmdk:x64-linux is marked as fail but not supported for x64-linux.
REGRESSION: kf5kio:x64-linux failed with BUILD_FAILED. If expected, add kf5kio:x64-linux=fail to /mnt/vss/_work/1/s/scripts/azure-pipelines/../ci.baseline.txt.

[dg0yt]

REGRESSION: pmdk:x64-linux is marked as fail but not supported for x64-linux.

#33766 (comment)

[FrankXie05]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[vicroms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).