Issue #20967 has been updated by ngoto (Naohisa Goto). Status changed from Open to Closed I think that it is difficult to add `-xatomic=studio` or `-xatomic=gcc` automatically to `cflags` or `CFLAGS` by `./configure` because it is difficult to determine which is appropriate or better option. I think installing users should determine this. Generally, I think `-xatomic=gcc` is preferred on system with GCC installed. So, closing this issue. ---------------------------------------- Bug #20967: Oracle Developer Studio 12.5 on Solaris 10 miniruby symbol referencing error: Undefined symbol: atomic_signal_fence https://bugs.ruby-lang.org/issues/20967#change-111079 * Author: ngoto (Naohisa Goto) * Status: Closed * Assignee: ngoto (Naohisa Goto) * ruby -v: ruby 3.3.5 (2024-11-05 revision 664bbbd0fd) [sparc64-solaris2.10] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- When compiling Ruby 3.3 or head by using Oracle Developer Studio 12.5 on Solaris 10, failed to make miniruby with the following error messages: ``` Undefined first referenced symbol in file atomic_signal_fence vm.o ld: fatal: symbol referencing errors. No output written to miniruby make: *** [miniruby] Error 2 ``` Ruby 3.3.4 or later may be affected. This error occurred because of improper selection of atomic library in Oracle Developer Studio. https://docs.oracle.com/cd/E77782_01/html/E77789/gqhbq.html Adding `cflags` to `-xatomic=studio` or `-xatomic=gcc` when running `./configure` solved the problem. For example, ``` ./configure --prefix=/opt/ruby340 cflags="-xatomic=gcc" ``` -- https://bugs.ruby-lang.org/