Re: official ruby33's rdoc build failed for main-arm64-default: ld-elf.so.1: /usr/local/lib/libunwind.so.8: Undefined symbol "__aarch64_ldadd4_acq_rel"
Mark Millard <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm,gmane.os.freebsd.devel.ports |
|---|---|
| Message-ID | <[email protected]> |
On Nov 10, 2025, at 07:14, Mark Millard <[email protected]> wrote: > I have submitted: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290928 > > reporting: > > QUOTE > The: > > https://pkg-status.freebsd.org/ampere2/data/main-arm64-default/p7c7045637357_s8fb17896120/logs/errors/ruby-3.3.9,1.log > > shows: > > . . . > --- ../../.ext/aarch64-freebsd16/openssl.so --- > linking shared-object openssl.so > --- ruby33 --- > --- ruby33 --- > linking ruby33 > --- main --- > --- rdoc --- > Generating RDoc documentation > ld-elf.so.1: /usr/local/lib/libunwind.so.8: Undefined symbol "__aarch64_ldadd4_acq_rel" > *** [rdoc] Error code 1 > > make: stopped making "all" in /wrkdirs/usr/ports/lang/ruby33/work/ruby-3.3.9 > make: 1 error > > make: stopped making "all" in /wrkdirs/usr/ports/lang/ruby33/work/ruby-3.3.9 > ===> Compilation failed unexpectedly. > > > That has lead to 4760 skipped port-package builds in: > > https://pkg-status.freebsd.org/ampere2/build.html?mastername=main-arm64-default&build=p7c7045637357_s8fb17896120 > > (At the time I'm writing this, the time the overall build > is still in progress.) > > ports tree at 7c7045637357 is from: 30 Oct 2025 00:59:23 UTC > src tree at 8fb17896120 is from: 30 Oct 2025 01:04:16 UTC > END QUOTE I have closed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290928 as overcome by events. The comments may prove of some interest relative to enabling outline-atomics being an issue for aarch64. It appears that a inline-atomics world can build a outline-atomics world but, then, that outline-atomics world can not build another outline-atomics world (leading to Continuous Integration main and other official 15.* build world failures). The new outline-atomics defaults for system clang/clang++ were reverted after those failures. And that leads to ruby33 not being a problem as things are. === Mark Millard marklmi at yahoo.com