Changes between Initial Version and Version 1 of Ticket #68962, comment 1


Ignore:
Timestamp:
Dec 25, 2023, 12:46:58 AM (5 months ago)
Author:
kencu (Ken)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #68962, comment 1

    initial v1  
    1 the build failure on the 10.6 buildbot is exposing a bug with legacysupport's newer libcxx forcing....it has nothing to do with this port specifically.
     1the build failure on the 10.6 buildbot is exposing a bug with legacysupport's newer libcxx forcing....
    22
    3 it looks like this "C" build line has a bunch of cxx-specific stuff on it, and no surprise I guess it ultimately fails running across cxx code.
     3it looks like this "C" build line has cxx-specific flags…
    44
    55Why are the cxx flags showing up on the "C" build?
    66
    7 Well, it's because  legacysupport is  putting all the cxx-specific modifications onto the CPP flags for some reason, instead of the CXX flags, and so the C builds are picking them up.
     7Well, it's likely because  legacysupport is  putting the cxx-specific modifications onto the CPP flags, instead of the CXX flags, and so the C builds are picking them up.
    88
    99{{{
    … …  
    1111}}}
    1212
    13 this is just wrong. It may not have showed up before because not many builds are mixing C and C++ code and also requiring legacysupport's newer libcxx.
     13they are not all on this build line…. but I suspect still being picked via env vars, etc.
    1414
    1515{{{