diff options
| author | nagachika <nagachika@ruby-lang.org> | 2021-03-20 13:33:52 +0900 |
|---|---|---|
| committer | nagachika <nagachika@ruby-lang.org> | 2021-03-20 13:33:52 +0900 |
| commit | ba6f0879448ebc80c7a595c369c59b6d8dfbdf3e (patch) | |
| tree | 565c771c9725cf866e7ab618fb64ffcc046b8ea1 /include/ruby | |
| parent | c98aa2db60f43e839d7a82897c22b5ceecbed417 (diff) | |
merge revision(s) abe2e7de4d1f2d5861d7c9ab9c7e778f2ee1dcd2: [Backport #16774]
Don't require sub-word atomics
On some architectures (like RISC-V) sub-word atomics are only available
when linking against -latomic, but the configure script doesn't do that,
causing the atomic checks to fail and the resulting ruby binary is
non-functional. Ruby does not use sub-word atomic operations, rb_atomic_t
is defined to unsigned int, so use unsigned int when checking for atomic
operations.
---
configure.ac | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Diffstat (limited to 'include/ruby')
0 files changed, 0 insertions, 0 deletions
