[MacPorts] #53577: db60 @6.0.30_2 build fails with atomic_init error, clang-3.8 or clang-3.9, MacOSX 10.6.8/libc++ but builds correctly with clang-3.7

[MacPorts]

#53577: db60 @6.0.30_2 build fails with atomic_init error, clang-3.8 or clang-3.9,
MacOSX 10.6.8/libc++ but builds correctly with clang-3.7
---------------------+-------------------------
  Reporter:  kencu   |      Owner:  afb@…
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:
Resolution:          |   Keywords:  snowleopard
      Port:  db60    |
---------------------+-------------------------

Comment (by kencu):

 The atomic types were added to clang in version 3.8
 <http://releases.llvm.org/3.8.0/tools/clang/docs/ReleaseNotes.html#opencl-c
 -language-changes-in-clang> which would explain why clang-3.7 builds this
 but clang-3.8+ do not.

 I tried `--disable-atomicsupport` which certainly sounded promising, but
 that didn't fix the build with clang-3.8+ / libc++ either.

 If all the recent Apple clang's build this port, then they must not have
 the atomic name collision that the OSS clangs >= 3.8 have.

 For now, if you need to build this port with a macports-clang compiler and
 you are using `-stdlib=libc++`, it looks like it will need to be macports-
 clang-3.7. Until Oracle gets around to changing their naming scheme, or
 otherwise changes the name scope / visibility somehow. Unless someone else
 has a clever idea.

--
Ticket URL: <https://trac.macports.org/ticket/53577#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS