Changes between Version 1 and Version 2 of Ticket #59992, comment 26


Ignore:
Timestamp:
Mar 28, 2020, 1:05:14 AM (4 years ago)
Author:
kencu (Ken)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #59992, comment 26

    v1 v2  
    1 Anything that uses Xcode clang and modules is broken in MacPorts by ncurses. Modules are a newer feature, so penetrance is evolving. I manually delete the libtapi tests that use modules, so you wouldn't see it. Proper clang-devel builds now want modules, and fail in MacPorts because of ncurses. Sure, perhaps I could disable modules project-by-project. I'm just not going to do that.
     1Anything that uses Xcode clang and modules is currently not functional in MacPorts by ncurses. Modules are a newer feature, so penetrance is evolving.
    22
    3 google this "error: unknown type name 'SCREEN'" for hits on other projects. Those hits usually lead to a suggestion much like you did "disable macports headers".or "uninstall macports". That's not a great solution.
     3I manually delete the libtapi tests that use modules, so you wouldn't see it.  Proper clang-devel builds now want modules, and fail in MacPorts because of ncurses.
    44
    5 I have tweaked my MacPorts unctrl.h to work around this, as at present that is the only solution I know of, other than disabling MacPorts, that generally works.
     5google "error: unknown type name 'SCREEN'" for hits on other projects.
    66
    7 We can talk about the purity of working around a clang issue by tweaking ncurses --- it's not a pure fix, I know .
     7I have tweaked my MacPorts unctrl.h to work around this, as at present that is the only solution I know of that generally works --- it's not a pure fix, I know .
    88
    9 But neither is unsetting CPATH and the library path, or disabling module support, or the parts of projects that require modules. We'll have to go back and undo all those hacks when clang is fixed too, and IMHO those are much more impactful than tweaking unctrl.h until Apple figures this out.
     9But neither is unsetting CPATH and the library path, or disabling module support, or the parts of projects that require modules. We'll have to go back and undo all those when clang is fixed too, and IMHO those are more impactful than tweaking unctrl.h until Apple figures this out.
    1010
    11 Or perhaps you can fix the clang issue, Marcus. If we could do that, all this would go away in a proper fashion.
     11Or perhaps we can fix the clang issue -- if we could do that, all this would go away in a proper fashion.