Re: Xcode 11 on Mojave

2019-10-12 Thread Chris Jones
> On 12 Oct 2019, at 3:28 am, Ryan Schmidt wrote: > > On Oct 11, 2019, at 09:57, Joshua Root wrote: > >> Xcode itself only contains a 10.15 SDK, but the Command Line Tools have >> a 10.14 one. You should be mostly fine with them installed, though there >> are some exceptions. Our

Re: compiler warning

2019-10-12 Thread Andrew Hartung via macports-users
> On Oct 12, 2019, at 10:10 AM, Ryan Schmidt wrote: > > On Oct 11, 2019, at 23:11, Andrew Hartung wrote: > >> On Oct 11, 2019, at 9:39 PM, Ryan Schmidt wrote: > >>> On Oct 10, 2019, at 22:58, Andrew Hartung wrote: >>> Warning: All compilers are either blacklisted or unavailable;

Re: compiler warning

2019-10-12 Thread Ryan Schmidt
Remember to Reply All so the conversation stays on the list. On Oct 11, 2019, at 23:11, Andrew Hartung wrote: > On Oct 11, 2019, at 9:39 PM, Ryan Schmidt wrote: >> On Oct 10, 2019, at 22:58, Andrew Hartung wrote: >> >>> >>> Warning: All compilers are either blacklisted or unavailable;

All compilers are either blacklisted or unavailable (was: compiler warning)

2019-10-12 Thread Joshua Root
Ryan Schmidt wrote: > On Oct 11, 2019, at 23:11, Andrew Hartung wrote: > >> On Oct 11, 2019, at 9:39 PM, Ryan Schmidt wrote: > >>> On Oct 10, 2019, at 22:58, Andrew Hartung wrote: >>> Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback

Re: compiler warning

2019-10-12 Thread Andrew Hartung via macports-users
I found the problem. Somehow xcode got updated to 11 automatically two days ago. I just upgraded to Mojave a couple of weeks ago and missed a setting in the app store to turn off automatic upgrades. Downgrading now, sorry to waste everyones time. > On Oct 12, 2019, at 10:10 AM, Ryan Schmidt

Re: Xcode 11 on Mojave

2019-10-12 Thread Ken Cunningham
> > But the CLT has the SDK in a different path than Xcode does, of course. And > > if Xcode-based SDK paths got baked into various ports on our Xcode-10-using > > Mojave build worker, then that will be a problem for any users that have > > Xcode 11, whether or not they have the CLT. > > Does

Re: Xcode 11 on Mojave

2019-10-12 Thread Ryan Schmidt
On Oct 12, 2019, at 03:36, Chris Jones wrote: > On 12 Oct 2019, at 3:28 am, Ryan Schmidt wrote: > >> On Oct 11, 2019, at 09:57, Joshua Root wrote: >> >>> Xcode itself only contains a 10.15 SDK, but the Command Line Tools have >>> a 10.14 one. You should be mostly fine with them installed,

Re: Xcode 11 on Mojave

2019-10-12 Thread Joshua Root
On 2019-10-13 02:06 , Ryan Schmidt wrote: > > > On Oct 12, 2019, at 03:36, Chris Jones wrote: > >> On 12 Oct 2019, at 3:28 am, Ryan Schmidt wrote: >> >>> On Oct 11, 2019, at 09:57, Joshua Root wrote: >>> Xcode itself only contains a 10.15 SDK, but the Command Line Tools have a 10.14

Re: MacPorts activation relating to bsdtar

2019-10-12 Thread Chris Jones
> On 12 Oct 2019, at 3:26 am, Ryan Schmidt wrote: > >  > >> On Oct 11, 2019, at 10:49, Steven Esser wrote: >> >> On a fresh Catalina (10.15) install with Xcode 11.1 and the latest CLI tools >> I cannot seem to activate any ports. Most seem to configure and build >> correctly, but fail

Re: MacPorts activation relating to bsdtar

2019-10-12 Thread Steven
Home directory installations have worked fine for me for years in the past. I understand some ports will not work, but everything I need to use works fine. That being said, I will try a few different things out to see if that fixes my problems. > On Oct 12, 2019, at 05:20, Chris Jones wrote:

Re: compiler warning

2019-10-12 Thread Andrew Hartung via macports-users
> On Oct 12, 2019, at 4:48 PM, Ryan Schmidt wrote: > > > > On Oct 12, 2019, at 12:30, Andrew Hartung wrote: > >> I found the problem. Somehow xcode got updated to 11 automatically two days >> ago. I just upgraded to Mojave a couple of weeks ago and missed a setting in >> the app store to

Re: compiler warning

2019-10-12 Thread Ryan Schmidt
On Oct 12, 2019, at 12:30, Andrew Hartung wrote: > I found the problem. Somehow xcode got updated to 11 automatically two days > ago. I just upgraded to Mojave a couple of weeks ago and missed a setting in > the app store to turn off automatic upgrades. Downgrading now, sorry to waste >

Xfce4 Won't Launch in macOS Catalina

2019-10-12 Thread Emily Jackson
I recently upgraded from Mojave to Catalina and redid my MacPorts installation. I used Xfce4 as a WM under Mojave, but now I can’t get it to launch while running Catalina. I have attached screen shots of the errors I get. I can use quartz-wm with X11, but I would like to get Xfce4 working.

Re: compiler warning

2019-10-12 Thread Al Varnell via macports-users
I feel certain that could be configured to be the default setting for this list. It is the only one of over a dozen that I subscribe to where it’s not. Could that be checked into? Sent from my iPad -Al- > On Oct 12, 2019, at 08:10, Ryan Schmidt wrote: > > Remember to Reply All so the

Re: Xfce4 Won't Launch in macOS Catalina

2019-10-12 Thread Chris Jones
Hi, I am not sure you have provided enough information for anyone to really be able to help. Most likely some command that previously worked is now failing to run, and you need to first figure out what that is. Are there any crash reports, in Console, that might help ? Have you checked to see