#42506: sparsehash: configuration error -------------------------+------------------- Reporter: jwhowse4@… | Owner: hum@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: sparsehash | -------------------------+------------------- Comment (by jwhowse4@…): Replying to [comment:9 nicos@…]:

The issue seems to persist, and it seems to be a gcc vs. clang problem. Clang (apple-clang and macports-clang-3.{4, 5, 6} reduces to <functional>, while gcc-4.8, 4.9 and 5.0 reduce to <tr1/functional>

In the build log I attached it appears to me that sparsehash is being built with apple-clang. Am I reading the log wrong? If I am not misreading the log, would mind explaining how this is a gcc vs. clang issue when my clang built sparsehash reduces to <tr1/functional>? This may be a silly question, I am just trying to understand the issue. -- Ticket URL: <https://trac.macports.org/ticket/42506#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X