Opened 4 years ago

Closed 4 years ago

#52776 closed defect (invalid)

clang build fails due to __SWIFT_UNAVAILABLE_MSG used in the SDK but not defined for some reason

Reported by: murrayE Owned by: jeremyhu (Jeremy Huddleston Sequoia)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: larryv (Lawrence Velázquez)
Port: clang-3.8

Description

Upgrade clang-3.8 to 3.8.1_4 from 3.8.1_3 fails under El Capitan 10.11.6.

Attachments (1)

clang-3.8_upgrade_main.log.zip (26.6 KB) - added by murrayE 4 years ago.
zipped main.log

Download all attachments as: .zip

Change History (11)

comment:1 Changed 4 years ago by mf2k (Frank Schima)

Cc: larryv added
Owner: changed from macports-tickets@… to jeremyhu
Port: clang-3.8 added; clang_3.8 removed
Status: newassigned

In the future, please Cc the port maintainers (port info --maintainers clang-3.8), if any.

Changed 4 years ago by murrayE

zipped main.log

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

:info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.8/clang-3.8/work/llvm-3.8.1.src/projects/compiler-rt/lib/builtins/em
utls.c:10:
:info:build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h:423:25: error: expected parameter declarator
:info:build __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
:info:build                         ^
:info:build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h:423:25: error: expected ')'
:info:build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h:423:24: note: to match this '('
:info:build __SWIFT_UNAVAILABLE_MSG("Use lazily initialized globals instead")
:info:build                        ^
:info:build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h:424:51: error: expected ';' after top level declarator
:info:build __OSX_AVAILABLE_STARTING(__MAC_10_4, __IPHONE_2_0)
:info:build                                                   ^
:info:build 3 errors generated.
:info:build make[2]: *** [projects/compiler-rt/lib/builtins/CMakeFiles/clang_rt.builtins_x86_64_10.4.dir/emutls.c.o] Error 1

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

Did you muck you your Availability.h? __SWIFT_UNAVAILABLE_MSG is declared in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/Availability.h

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

Summary: clang-3.8 upgrade to 3.8.1_4 build failsclang build fails due to __SWIFT_UNAVAILABLE_MSG used in the SDK but not defined for some reason

comment:5 Changed 4 years ago by ken-cunningham-webuse

I believe this issue could relate to a rogue

 /opt/local/include/Availability.h

as per the mailing list discussion. If that is proven to be so, it could be closed.

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

What's the output of port provides /opt/local/include/Availability.h ?

comment:7 Changed 4 years ago by ken-cunningham-webuse

I don't have it on my system, but apparently some do -- at some point someone suggested modifying Availability.h as a fix to some issue, and at least a few people did that.

They would likely be the ones having the __SWIFT_UNAVAILABLE_MSG error now, I would postulate.

K

Last edited 4 years ago by ken-cunningham-webuse (previous) (diff)

comment:8 Changed 4 years ago by ken-cunningham-webuse

here's the ticket that got that started, I believe [ticket:48471}

comment:9 Changed 4 years ago by ken-cunningham-webuse

this ticket can be closed as "invalild"

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

Resolution: invalid
Status: assignedclosed

Thanks, Ken. I was still waiting for a response from murrayE to confirm that was the case, but that doesn't seem to be coming, so I'll close as invalid as you suggest.

Note: See TracTickets for help on using tickets.