Changes between Initial Version and Version 1 of Ticket #55709, comment 7


Ignore:
Timestamp:
Jan 18, 2018, 2:43:22 PM (6 years ago)
Author:
kencu (Ken)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #55709, comment 7

    initial v1  
    55Jeremy uses the `buildit` scripts to prevent the requirement for `cmake` which is a circular dependency on older systems the way MacPorts is set up. You have found out that you can build `libcxx` using the `cmake` build. That works for you on linux because building gcc6+ does not depend on cmake, and going that route, there is no circular dependency issues. It would work for us on MacPorts too, should we decide to set up the build that way. But we are not going to do that on MacPorts for 100 reasons we all know well. We are going to use the `buildit` script, and the `buildit` script is not presently `gcc`-friendly.
    66
    7 So potmj can either go through tremendous hoops that probably only 5 or 6 of use would understand to make this work with gcc for no purpose at all, or he can simply change his universal_archs to `i386 x86_64` and then everything will be fine again (once he gets back on the train with his toolchain, and re-enables clang as his default compiler).
     7So potmj can either go through tremendous hoops that probably only 5 or 6 of us would understand to make this work with gcc for no purpose at all, or he can simply change his universal_archs to `i386 x86_64` and then everything will be fine again (once he gets back on the train with his toolchain, and re-enables clang as his default compiler).
    88
    99Just because his universal_archs are set to `i386 x86_64` doesn't mean he will have to '''build''' everything universal. There is no need to do that. However, when one of Jeremy's Portfiles forces universal, it will '''work''' instead of '''break'''.