Opened 11 months ago

Closed 5 months ago

#68533 closed defect (fixed)

R-clock fails on 10.7–10.11: Symbol not found: __ZSt19uncaught_exceptionsv

Reported by: barracuda156 Owned by: barracuda156
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: lion, mountainlion, mavericks, yosemite, elcapitan Cc:
Port: R-clock

Description 

Error: package or namespace load failed for ‘clock’ in dyn.load(file, DLLpath = DLLpath, ...):
 unable to load shared object '/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_R_R-clock/R-clock/work/destroot/opt/local/Library/Frameworks/R.framework/Versions/4.3/Resources/library/00LOCK-clock-0.7.0/00new/clock/libs/clock.so':
  dlopen(/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_R_R-clock/R-clock/work/destroot/opt/local/Library/Frameworks/R.framework/Versions/4.3/Resources/library/00LOCK-clock-0.7.0/00new/clock/libs/clock.so, 6): Symbol not found: __ZSt19uncaught_exceptionsv
  Referenced from: /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_R_R-clock/R-clock/work/destroot/opt/local/Library/Frameworks/R.framework/Versions/4.3/Resources/library/00LOCK-clock-0.7.0/00new/clock/libs/clock.so
  Expected in: flat namespace
 in /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_R_R-clock/R-clock/work/destroot/opt/local/Library/Frameworks/R.framework/Versions/4.3/Resources/lib
Error: loading failed

Change History (4)

comment:1 Changed 5 months ago by ryandesign (Ryan Carsten Schmidt)

The failed 10.7–10.11 builds are using clang 16. It succeeds on 10.12 and later using clang 16 and on Snow Leopard using clang 11. That makes me think it might be a libc++ issue that might be solved by using the legacy support portgroup's feature of using a newer MacPorts libc++.

comment:2 in reply to:  1 Changed 5 months ago by barracuda156

Replying to ryandesign:

The failed 10.7–10.11 builds are using clang 16. It succeeds on 10.12 and later using clang 16 and on Snow Leopard using clang 11. That makes me think it might be a libc++ issue that might be solved by using the legacy support portgroup's feature of using a newer MacPorts libc++.

Same as in #67612

comment:3 Changed 5 months ago by barracuda156

I will try fixing this, got to an Intel machine with 10.8.

comment:4 Changed 5 months ago by barracuda156

Owner: set to barracuda156
Resolution: → fixed
Status: new → closed

In 75293ea653d4780c41ae8723da3f4ffd38ba31e7/macports-ports (master):

R-clock: fix for < 10.13 with clang

Fixes: #68533

Note: See TracTickets for help on using tickets.