Changes between Initial Version and Version 1 of Ticket #42506, comment 10


Ignore:
Timestamp:
Oct 18, 2015, 3:43:15 PM (9 years ago)
Author:
jwhowse4
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #42506, comment 10

    initial v1  
    22> 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>
    33
    4 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.
     4In 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 you 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.