[SERVER-65893] Add 6.0 platform builders for v4 gcc and clang Created: 22/Apr/22  Updated: 29/Oct/23  Resolved: 10/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Daniel Moody
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-62994 Upgrade server build from v3 toolchai... Closed
Duplicate
Related
is related to SERVER-69590 libunwind warnings on clang arm platf... Closed
Backwards Compatibility: Fully Compatible
Sprint: Dev Platform 2022-05-16
Participants:

 Description   

While working on upgrading the toolchain from GCC 11.2 to 11.3, we found that we needed to advance the v4 validation commit to v6.1.0-alpha. Unfortunately, those builds failed with clang because the most recent upgrade to libunwind throws new errors on the ZAP platforms when built with clang. Amazon Linux 2022, Ubuntu 22.04, and RHEL 9 failed compiling Boost at src/third_party/boost/boost/thread/pthread/thread_data.hpp:61:19 due to a sign comparison warning whenever PTHREAD_MIN_STACK_SIZE is defined. Finally, we disabled LLVM builds on static hosts and SUSE 12 completely because of resource issues and timeouts in order to get a consistent toolchain deployment. We should lock in new builders for 6.0 with the v4 toolchain once we have these problems fixed.



 Comments   
Comment by Andrew Morrow (Inactive) [ 03/Nov/22 ]

The PTHREAD_MIN_STACK_SIZE errors were fixed in SERVER-60440 with the upgrade to boost 1.79.

Comment by Daniel Moody [ 03/Nov/22 ]

the libunwind warnings were fixed in SERVER-69590

Comment by Ryan Egesdahl (Inactive) [ 29/Sep/22 ]

andrew.morrow@mongodb.com Yes, the Boost errors looked like this:

In file included from src/third_party/boost/boost/thread/thread_only.hpp:17,
                 from src/third_party/boost/boost/thread/thread.hpp:12,
                 from src/third_party/boost/boost/log/sinks/async_frontend.hpp:38,
                 from src/third_party/boost/boost/log/sinks.hpp:25,
                 from src/mongo/shell/mongo_main.cpp:40:
src/third_party/boost/boost/thread/pthread/thread_data.hpp: In member function ‘void boost::thread_attributes::set_stack_size(std::size_t)’:
src/third_party/boost/boost/thread/pthread/thread_data.hpp:61:19: error: comparison of integer expressions of different signedness: ‘std::size_t’ {aka ‘long unsigned int’} and ‘long int’ [-Werror=sign-compare]
           if (size<PTHREAD_STACK_MIN) size=PTHREAD_STACK_MIN;

It only happens on the few platforms we have that define PTHREAD_STACK_MIN.

Comment by Andrew Morrow (Inactive) [ 29/Sep/22 ]

ryan.egesdahl@mongodb.com - Do you remember what sort of error you observed trying to build vendored boost on RHEL 9? Is there a log somewhere?

Comment by Ryan Egesdahl (Inactive) [ 23/Aug/22 ]

RHEL 9 is also failing to build our vendored Boost.

Comment by Ryan Egesdahl (Inactive) [ 10/Jul/22 ]

We also need to do the same for the Amazon Linux 2022 and Ubuntu 22.04 builders as well.

Comment by Andrew Morrow (Inactive) [ 25/Apr/22 ]

This ticket should include the work to fix the libunwind warnings thrown on ZAP with clang.

Generated at Thu Feb 08 06:03:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.