Re: [MacPorts] #72595: gunits @2.24: error: ‘DBL_DECIMAL_DIG’ undeclared (was: gunits 2.24 is broken: error: ‘DBL_DECIMAL_DIG’ undeclared)

[MacPorts]

#72595: gunits @2.24: error: ‘DBL_DECIMAL_DIG’ undeclared
-------------------------+-------------------------------------------------
  Reporter:              |      Owner:  (none)
  barracuda156           |
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.10.7
Resolution:              |   Keywords:  lion mountainlion mavericks
      Port:  gunits      |  yosemite elcapitan
-------------------------+-------------------------------------------------
Changes (by ryandesign):

 * keywords:   => lion mountainlion mavericks yosemite elcapitan


Comment:

 Replying to [comment:2 saj]:
 > https://ports.macports.org/port/gunits/details/
 >
 > Looks like it is broken on OS X 10.7 through 10.11.  (Though, oddly, not
 10.5 or 10.6.

 We haven't had a 10.5 build machine in years so any status information you
 see about that OS version on ports.macports.org is outdated.

 > It looks like MacPorts builds with a newer compiler on these platforms?)

 The clang on 10.6 is so old as to be useless so MacPorts does use a newer
 MacPorts clang on 10.6, but what compiler MacPorts defaults to subject to
 change. Write your ports to work regardless what compiler MacPorts picks
 by default, meaning if a port is incompatible with a particular compiler,
 express that using `compiler.blacklist` so that MacPorts will pick
 something else.

 However in this case there isn't necessarily a compiler incompatibility,
 just a missing compiler flag which can be added easily.

 > Is there a way to ask buildbot to build for these old releases prior to
 merge?

 Buildbot only does thing after a commit occurs on master.

 The CI system you access via pull requests runs on GitHub Actions, not
 Buildbot. The runners available to us with GitHub Actions are limited to
 OS versions supported by Apple.

 > {{{
 > DEBUG: Xcode 8.2.1, CLT 8.2.0.0.1.1480973914
 > }}}
 >
 > [[https://gist.github.com/yamaya/2924292|list of clangs in old Xcode
 releases]]

 No need to consult a third-party document; we maintain such a list at
 XcodeVersionInfo.

 > clang 8?

 Apple clang 8. Apple clang version numbers follow Xcode version numbers.
 Apple clang version numbers are different from llvm.org version numbers.

 >
 https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/293844/steps
 /install-port/logs/stdio
 >
 > {{{
 > checking for /usr/bin/clang option to enable C11 features... none needed
 > }}}
 >
 > https://releases.llvm.org/8.0.0/tools/clang/docs/UsersManual.html

 That's llvm.org clang 8, not Apple clang 8.

 A table matching Apple clang versions to llvm.org clang versions is at
 https://en.wikipedia.org/wiki/Xcode#Toolchain_versions where you see Apple
 clang 8.x is based on (but not identical to) llvm.org clang 3.9.

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