Opened 5 years ago

Closed 5 years ago

#49177 closed defect (duplicate)

clang-3.5: ld: library not found for -lc++

Reported by: csinz (Carsten Sinz) Owned by: jeremyhu (Jeremy Huddleston Sequoia)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: elcapitan Cc:
Port: clang-3.5

Description (last modified by ryandesign (Ryan Schmidt))

Trying to build clang-3.5 with Xcode 7.0.1 (Build version 7A1001) on OS X El Capitan 10.11 (15A284) fails:

$ sudo port install clang-3.5
--->  Computing dependencies for clang-3.5
...
--->  Building clang-3.5
Error: org.macports.build for port clang-3.5 returned: command execution failed
Please see the log file for port clang-3.5 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.5/clang-3.5/main.log
...
Error: Processing of port clang-3.5 failed

This seems to be a linker problem related to libc++, as the log file repeatedly contains the lines:

:info:build ld: library not found for -lc++
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)

BTW: Building clang-3.6 on the same system works without a problem.

Change History (4)

comment:1 Changed 5 years ago by csinz (Carsten Sinz)

This seems to be the same problem as that of Ticket #49171 for clang-3.8.

comment:2 Changed 5 years ago by csinz (Carsten Sinz)

I could solve the problem by using a suggestion from Ticket #48841:

   sudo port install ld64 +ld64_xcode

before installing clang-3.5 did the job.

So the ticket can be closed.

Last edited 5 years ago by ryandesign (Ryan Schmidt) (previous) (diff)

comment:3 Changed 5 years ago by ryandesign (Ryan Schmidt)

Description: modified (diff)
Keywords: elcapitan added
Owner: changed from macports-tickets@… to jeremyhu@…
Summary: clang-3.5 fails to build (Xcode 7.0.1, OS X El Capitan)clang-3.5: ld: library not found for -lc++

comment:4 Changed 5 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: duplicate
Status: newclosed
Note: See TracTickets for help on using tickets.