I note the recently folly is upgrade by 3fabdf5. Seems it requires gcc version >=10.

@PHILO-HE Ok, looks like we have to move up gcc for Ubuntu 20.04 faster than expected. Recommended is using gcc11. We haven't run the recent upgraded folly with gcc9 so missed any potential issue.

@PHILO-HE In fact, Ubuntu 20.04 has a few problems right now independent of gcc11.

1. setup script is not installing CMake PkgConfig used by a few modules (RE2).
2. Improve duplicated key error message #9374 added Gtest features (Throws) only available in Gtest 1.11 while system default in Ubuntu 20.04 is 1.10. So we'd need to move to a build&install for Gtest.

This begs the question if we can discontinue supporting Ubuntu 20.04 as a build environment?

@PHILO-HE In fact, Ubuntu 20.04 has a few problems right now independent of gcc11.

1. setup script is not installing CMake PkgConfig used by a few modules (RE2).
2. Improve duplicated key error message #9374 added Gtest features (Throws) only available in Gtest 1.11 while system default in Ubuntu 20.04 is 1.10. So we'd need to move to a build&install for Gtest.

This begs the question if we can discontinue supporting Ubuntu 20.04 as a build environment?

@czentgr, thanks for your check! cc @majetideepak, @assignUser, @kgpai

This begs the question if we can discontinue supporting Ubuntu 20.04 as a build environment?

The first issue can be fixed by installing the missing package. I fixed the second issue by using VELOX_ASSERT_THROW #11270
The Ubuntu 20.04 end of standard support in April 2025. We should support it until then.

@majetideepak, I agree to keep supporting ubuntu 20.04. @czentgr, could you help upgrade gcc for this os?

@PHILO-HE Sure. I am working on a PR for that (where I found the additional issues).