diff options
author | William Hubbs <williamh@gentoo.org> | 2022-09-17 13:26:43 -0500 |
---|---|---|
committer | William Hubbs <williamh@gentoo.org> | 2022-09-17 13:38:51 -0500 |
commit | 23f1241fe1802ab3561c15f699d6b48b39a59471 (patch) | |
tree | 362eadb23872957610c6459d42e7467ef5474c7c /media-libs/libmpris2client | |
parent | net-misc/gnome-connections: Version bump to 43.0 (diff) | |
download | gentoo-23f1241fe1802ab3561c15f699d6b48b39a59471.tar.gz gentoo-23f1241fe1802ab3561c15f699d6b48b39a59471.tar.bz2 gentoo-23f1241fe1802ab3561c15f699d6b48b39a59471.zip |
net-libs/nodejs: force libgcc as support lib
Upstream behavior is correct wrt libatomic (unconditionally adding it)
due to their use of atomic_is_lock_free which is yet to be added to
compiler-rt (stuck in review hell at https://reviews.llvm.org/D85044).
This necessitates forcing libgcc as support lib. Linking to libatomic
from gcc is dynamic, so sys-devel/gcc has to go in RDEPEND. Clang can
be forced to use libgcc with --rtlib=libgcc, even with
USE=default-compiler-rt (which is the original cuase of the bug in
question).
This applies this pull request to 14.x and 16.x.
Closes: https://github.com/gentoo/gentoo/pull/27271
Signed-off-by: William Hubbs <williamh@gentoo.org>
Diffstat (limited to 'media-libs/libmpris2client')
0 files changed, 0 insertions, 0 deletions