Re: Seeming flaw in Xcode 10

> On Nov 11, 2018, at 3:07 PM, Perry E. Metzger wrote: > > No, that works if is in the system includes path, and > that's standards conformant. What I know about this, no doubt incomplete, comes from here:

Re: Seeming flaw in Xcode 10

On 2018-11-11 17:36, Perry E. Metzger wrote: > Does anyone know how to > get in touch with the Xcode team to inform them that this change of > behavior is apparently nonstandard, and breaks the expectations of > standards conforming C code? I don't want to be the devil's advocat, but reporting

Re: Seeming flaw in Xcode 10

On Sun, 11 Nov 2018 17:50:10 -0500 Mark Anderson wrote: > First thing I would do is file a radar. I know that's a terrible > solution, but it'll be the thing anyone at apple will tell us to do > first thing. I may be mistaken about the problem (see my response to Ken a few moments ago.) This is

Re: Seeming flaw in Xcode 10

On Sun, 11 Nov 2018 15:00:53 -0800 Ken Cunningham wrote: > > > > On Sun, Nov 11, 2018 at 5:36 PM Perry E. Metzger > > mailto:pe...@piermont.com>> wrote: As some > > of you are aware, XCode 10 no longer searches SDK include > > directories for C headers specified with " marks, as in > > And

Re: Seeming flaw in Xcode 10

> > On Sun, Nov 11, 2018 at 5:36 PM Perry E. Metzger > wrote: > As some of you are aware, XCode 10 no longer searches SDK include > directories for C headers specified with " marks, as in > And vice-versa — it will no longer search the source path for any files

Re: Seeming flaw in Xcode 10

I can file one against the betas as well. —Mark ___ Mark E. Anderson On Sun, Nov 11, 2018 at 5:50 PM Mark Anderson wrote: > First thing I would do is file a radar. I know that's a terrible solution, > but it'll be the thing anyone at apple will tell us to do first thing.

Re: Seeming flaw in Xcode 10

First thing I would do is file a radar. I know that's a terrible solution, but it'll be the thing anyone at apple will tell us to do first thing. —Mark ___ Mark E. Anderson On Sun, Nov 11, 2018 at 5:36 PM Perry E. Metzger wrote: > As some of you are aware, XCode 10 no

Seeming flaw in Xcode 10

As some of you are aware, XCode 10 no longer searches SDK include directories for C headers specified with " marks, as in #include "stdio.h" I happened to be reading the C standard (don't ask why) and I've discovered this new behavior is wrong and the original behavior was correct. To wit, in

Re: [GitHub] Subscribed to macports/macports-legacy-support notifications

On 07.11.18 22:31, Ryan Schmidt wrote: > > > On Nov 7, 2018, at 15:22, Rainer Müller wrote: > >> On 07.11.18 22:10, Rainer Müller wrote: >>> What is the plan? Should we also connect this new repository with Trac? >> >> Ah, just found the ticket: >> https://trac.macports.org/ticket/57537 The

isl, cctools, ... & cross-compilers

Hi, I noticed that at least one (but probably more) cross-compiler build is broken after isl update: https://github.com/macports/macports-ports/pull/2988 I suspect this means that we are missing at least a dependency on isl in our crossgcc portgroup? Other native gcc* ports depend on it,

Re: Xcode configuration woes

> On 10 Nov 2018, at 11:02 pm, Ryan Schmidt wrote: > > On Nov 10, 2018, at 02:53, Vincent Habchi wrote: > >> Ryan, >> >>> I don't know why Apple is doing this to us. This contradicts what we >>> previously knew about how SDKs were meant to function. The SDKs are >>> supposed to be the same