> >> On Jan 14, 2016, at 10:35 AM, Carl Hoefs >> <newsli...@autonomy.caltech.edu> wrote: >> >> In file included from >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/ncurses.h:141: >> /opt/local/include/unctrl.h:60:63: error: unknown type name 'SCREEN' >> NCURSES_EXPORT(NCURSES_CONST char *) NCURSES_SP_NAME(unctrl) (SCREEN*, >> chtype); > > > (tl;dr: Youâve installed headers for some different version of ncurses > in /opt, and the preprocessor is finding some of those headers in addition > to the standard ones and getting mixed up because theyâre not > compatible.) > > Looks like youâve got a header named unctrl.h in /opt/local/include that > is in the compilerâs header search path before the SDK header paths, so > when the standard ncurses.h includes unctrl.h it gets your local one > instead of the standard one. And then it appears that your local one is > not compatible â when I look at that header in the Mac OS SDK, there is > no declaration like the one quoted above. > >> Once failed it >> never recovers and I have to create a new "Command Line Tool" project >> and >> copy my source code over to it. > > That shouldnât be necessary. Have you tried Clean Build Folder? > (Cmd-Shift-Opt-K) > > âJens
Thx for the feedback. User paths can't get placed before the SDK header paths, can they? Odd that Clean Build Folder doesn't seem to affect this but copying the project to a new one does... for a while. Maybe there are too many people here doing things to the machine configurations. I just blew away all of Mac Ports and am now rebuilding it for El Cap. Hoping for the best... -Carl _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
