Changes between Version 3 and Version 4 of Ticket #65561


Ignore:
Timestamp:
Jul 29, 2022, 12:21:27 AM (21 months ago)
Author:
RobK88
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #65561 – Description

    v3 v4  
    55But on older Mac systems, I get the dreaded `unalz is using libstdc++ (this installation is configured to use libc++)`.
    66
    7 I have patched the Makefile accordingly so the CFLAGS, CXXFLAGS and LDFLAGS set by Macports are honoured and appended to the flags in the Makefile.
     7I have patched the Makefile accordingly so the CFLAGS, CXXFLAGS and LDFLAGS set by Macports are honoured and appended to the flags in the Makefile. 
    88
    9 But it looks like the default compiler on old Macs (e.g. g++ 4.2 on Lion) does not understand the `-stdlib=libc++` flag.  e.g. `cc1plus: error: unrecognized command line option "-stdlib=libc++"`
     9I can tell that "-stdlib=libc++" command line option is being passed to the compiler.  But it looks like the default compiler on old Macs (e.g. g++ 4.2 on Lion) does not understand the `-stdlib=libc++` command line option.  e.g. `cc1plus: error: unrecognized command line option "-stdlib=libc++"`
    1010
    1111Of course, I can get around this by specifying `configure.compiler=macports-clang-9.0` when installing or upgrading this port using macports.
    … …  
    1414
    1515Any help would be greatly appreciated. 
    16 Is there a way to get the old Apple compilers to understand "-stdlib=libc++"?
     16Is there a way to get the old Apple compilers to understand the "-stdlib=libc++" command line option?
    1717Maybe I need to specify the compiler in the portfile. e.g. clang-9.0 or greater.  How would I do that?
    1818