yugabyte/yugabyte-db

build: gcc11 debug/release centos7 compilation failure

Open

#22,059 opened on Apr 18, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (1,003 forks)batch import
help wantedstatus/awaiting-triage

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

centos7 (docker), gcc11, debug build on recent master commit 42add04f180858aec8dad95315169f2c19697239 gets compilation failure

/-------------------------------------------------------------------------------
| COMPILATION FAILED
|-------------------------------------------------------------------------------
/opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: pgbench.o: in function `threadRun':
/home/yugabyte/yugabyte-db/src/postgres/src/bin/pgbench/../../../../../../src/postgres/src/bin/pgbench/pgbench.c:6997: undefined reference to `__atomic_feraiseexcept'
/opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: /home/yugabyte/yugabyte-db/src/postgres/src/bin/pgbench/../../../../../../src/postgres/src/bin/pgbench/pgbench.c:6998: undefined reference to `__atomic_feraiseexcept'
collect2: error: ld returned 1 exit status

Did not try other build types such as release.

Issue Type

kind/bug

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.

Contributor guide

Research direction
Investigate the undefined reference to ` atomic feraiseexcept` in pgbench.c. Check if the build system is missing the atomic library (libatomic) or if the linker flags need adjustment. Look at the CMake or Makefile to see how linking is configured.
Tech stack
c
Domain
databasebackend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitDockerGCC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70