Changes between Version 5 and Version 6 of Ticket #55709, comment 7


Ignore:
Timestamp:
Jan 18, 2018, 6:01:56 PM (3 years ago)
Author:
kencu (Ken)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #55709, comment 7

    v5 v6  
    77So 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
    9 Just 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'''.
     9Just 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.