Re: Xcode update broke ports

[Ralph Castain]

Thanks Richard and Chris - downgrading Xcode as you described solved the 
problem! Much appreciate the assist.

Ralph


> On Sep 23, 2019, at 3:53 PM, Chris Janton  wrote:
> 
> 
>> On 23-Sep-2019, at 15:37, Richard L. Hamilton  wrote:
>> 
>> You might want to install it as something other than Xcode.app, like 
>> Xcode.10.3.app; you should be able to use xcode-select to pick which one has 
>> its command-line tools used.  There's another package there for the command 
>> line tools, too, I think.  Maybe someone else can better explain how to set 
>> it up so you can properly have what you need, without interfering with what 
>> you've already updated via the app store.
>> 
> 
> I discovered the problem too ;-)
> 
> I downloaded the Command Line Tools (mcOS 10.14) for Xcode 10.3, installed 
> the package, 'sudo port upgrade outdated' is working just fine again...
> 
> 8)
> --
> Chris Janton  - face at CentosPrime dot COM
> msgs: facej at me dot com
> 
> ‌
> ‌
> 

Re: Xcode update broke ports

[Ralph Castain]

I think it is port-dependent. Some ports worked fine with the symlink, but some 
(e.g., gcc) failed due to differences in the headers from what they were 
expecting.


> On Sep 23, 2019, at 9:53 PM, Vincent  wrote:
> 
> Hey,
> 
>> On 24 Sep 2019, at 00:12, Ralph Castain  wrote:
>> 
>> I tried uninstalling all ports and reinstalling them, but that didn't
>> help. Ditto for simply creating a MacOSX10.14.sdk symlink.
> 
> The symlink kludge worked with me, so I wonder what may be wrong in your case.
> 
> Vincent

Re: Xcode update broke ports

[Vincent]

Hey,

> On 24 Sep 2019, at 00:12, Ralph Castain  wrote:
> 
> I tried uninstalling all ports and reinstalling them, but that didn't
> help. Ditto for simply creating a MacOSX10.14.sdk symlink.

The symlink kludge worked with me, so I wonder what may be wrong in your case.

Vincent 

Re: Xcode update broke ports

[Chris Janton]

> On 23-Sep-2019, at 15:37, Richard L. Hamilton  wrote:
> 
> You might want to install it as something other than Xcode.app, like 
> Xcode.10.3.app; you should be able to use xcode-select to pick which one has 
> its command-line tools used.  There's another package there for the command 
> line tools, too, I think.  Maybe someone else can better explain how to set 
> it up so you can properly have what you need, without interfering with what 
> you've already updated via the app store.
> 

I discovered the problem too ;-)

I downloaded the Command Line Tools (mcOS 10.14) for Xcode 10.3, installed the 
package, 'sudo port upgrade outdated' is working just fine again...

8)
--
Chris Janton  - face at CentosPrime dot COM
msgs: facej at me dot com

‌
‌

Re: Xcode update broke ports

[Richard L. Hamilton]

You might want to install it as something other than Xcode.app, like 
Xcode.10.3.app; you should be able to use xcode-select to pick which one has 
its command-line tools used.  There's another package there for the command 
line tools, too, I think.  Maybe someone else can better explain how to set it 
up so you can properly have what you need, without interfering with what you've 
already updated via the app store.

> On Sep 23, 2019, at 18:35, Richard L. Hamilton  wrote:
> 
> Eventually MacPorts and/or Xcode will get fixed. I'm not involved except as 
> someone else that wants it to work (I was fortunate and asked before 
> installing it, and was warned that there might be problems). So I have no 
> idea when "eventually" might be. Hopefully those who know more will let us 
> know.
> 
> Until then, you can still download older Xcode versions outside of the app 
> store, and install them:
> https://developer.apple.com/download/more/ 
> 
> 
> 10.3 is the one you want, I think.
> 
> You may need an account, although it does not have to be a paid developer 
> account.
> 
>> On Sep 23, 2019, at 18:12, Ralph Castain > > wrote:
>> 
>> Apple apparently included an Xcode update in a recent maintenance release.
>> Since the update, I am unable to run many of the compiler ports (gcc,
>> python) due to errors stating that system headers and libraries cannot be
>> found. Investigation revealed that the ports were all configured with:
>> 
>> --with-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
>> 
>> However, the Xcode update apparently removed the MacOSX10.14.sdk in that 
>> directory and
>> replaced it with MacOSX10.15.sdk - even though I have NOT updated the OS
>> from Mojave!
>> 
>> I tried uninstalling all ports and reinstalling them, but that didn't
>> help. Ditto for simply creating a MacOSX10.14.sdk symlink.
>> 
>> Does anyone have a suggestion on how to get around this problem?
>> 
>> Ralph
>> 
>> 
> 

Re: Xcode update broke ports

[Richard L. Hamilton]

Eventually MacPorts and/or Xcode will get fixed. I'm not involved except as 
someone else that wants it to work (I was fortunate and asked before installing 
it, and was warned that there might be problems). So I have no idea when 
"eventually" might be. Hopefully those who know more will let us know.

Until then, you can still download older Xcode versions outside of the app 
store, and install them:
https://developer.apple.com/download/more/ 


10.3 is the one you want, I think.

You may need an account, although it does not have to be a paid developer 
account.

> On Sep 23, 2019, at 18:12, Ralph Castain  wrote:
> 
> Apple apparently included an Xcode update in a recent maintenance release.
> Since the update, I am unable to run many of the compiler ports (gcc,
> python) due to errors stating that system headers and libraries cannot be
> found. Investigation revealed that the ports were all configured with:
> 
> --with-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
> 
> However, the Xcode update apparently removed the MacOSX10.14.sdk in that 
> directory and
> replaced it with MacOSX10.15.sdk - even though I have NOT updated the OS
> from Mojave!
> 
> I tried uninstalling all ports and reinstalling them, but that didn't
> help. Ditto for simply creating a MacOSX10.14.sdk symlink.
> 
> Does anyone have a suggestion on how to get around this problem?
> 
> Ralph
> 
> 

Xcode update broke ports

[Ralph Castain]

Apple apparently included an Xcode update in a recent maintenance release.
Since the update, I am unable to run many of the compiler ports (gcc,
python) due to errors stating that system headers and libraries cannot be
found. Investigation revealed that the ports were all configured with:

--with-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk

However, the Xcode update apparently removed the MacOSX10.14.sdk in that 
directory and
replaced it with MacOSX10.15.sdk - even though I have NOT updated the OS
from Mojave!

I tried uninstalling all ports and reinstalling them, but that didn't
help. Ditto for simply creating a MacOSX10.14.sdk symlink.

Does anyone have a suggestion on how to get around this problem?

Ralph

Re: Problems with MP 2.6.0 on Snow Leopard

[Joshua Root]

Hi Rob,

Rob Widdicombe wrote:
> I'm still resolutely running Snow Leopard and last night did a port 
> selfupdate to take me up to MP 2.6.0. So far so good.
> 
> However, when I then tried to do a port rev-upgrade, the problems began. It 
> fails on the first step, upgrading gmp. Looking at the log files, it seems 
> like it's expecting to find clang 8, and I have no idea why - I've never 
> installed it and so, not surprisingly, it's not there.
> 
> I'm using:
> 
> Xcode 3.2
> Component versions: DevToolsCore-1608.0; DevToolsSupport-1591.0
> BuildVersion: 10D575

It won't fix this problem, but it's recommended to update to Xcode 3.2.6.

> Here are the log files:

This seems to be an issue specific to gmp. It does some manipulation of
the selected compiler which relies on assumptions that are no longer
true in MacPorts 2.6. Please file a ticket.

- Josh

Re: Problems with MP 2.6.0 on Snow Leopard

[Ken Cunningham]

clang-8.0 is the new default compiler for 10.6.8, but it shouldn't be requiring 
it until it is installed.

This procedure is new, and we are just learning all the ways it might break :) 
I am thinking that the logic sees you libxx installed, and that is confusing it.

Once the buildbot is up to speed, you'll just download a prebuilt gnp and be on 
your way.

But I am curious what is doing this to you. If you get time, please post back 
the rsults of: 

port -v installed libcc
port -v installed cctools
port -v installed ld64
port -v installed | grep clang
port -v installed | grep llvm
port -v installed | grep bootstrap

Best, Ken

Re: Problems with MP 2.6.0 on Snow Leopard

[Rob Widdicombe]

Hi Mojca,

Many thanks for the reply.

That's fine - I'm happy to wait. The existing  binaries are still happy and it 
was just a fluke of timing that had me updating to the new MP as soon as it was 
out of the gate..

I'll keep an eye on the news and try again when things have settled down a bit. 

I'm just very grateful that my aged OS is still supported! :)

Rob


On 23 Sep 2019, at 11:43, Mojca Miklavec wrote:

> On Mon, 23 Sep 2019 at 11:38, Rob Widdicombe wrote:
>> 
>> Hi,
>> 
>> Bear with me - I'm a musician, not a Unix expert, but I'm doing my best!
>> 
>> I'm still resolutely running Snow Leopard and last night did a port 
>> selfupdate to take me up to MP 2.6.0. So far so good.
>> 
>> However, when I then tried to do a port rev-upgrade, the problems began.
> 
> Without looking at the individual logs yet ... as Ryan mentioned, we
> would generally advice users of < 10.9 to wait a couple of more days
> before doing the actual update.
>
> https://lists.macports.org/pipermail/macports-users/2019-September/047381.html
> 
> This is something that we should probably write with some big warning
> sign to both the homepage (download section) as well as under github
> release.
> 
> Some pretty big fundamental changes were done for these old systems
> and there were two options:
> - put an extensive amount of effort and horsepower to run both
> configurations in parallel for an extended period of time
> - switch the default and cope with some issues for a limited period of
> time, hoping that not too many users will be affected (too much)
> 
> Due to lack of manpower we went for the second option.
> 
> According to https://build.macports.org/waterfall?tag=10.6 the
> buildbot workers were not even re-started yet, and I would expect a
> couple of days (or weeks) for them to catch up. Ideally you would want
> to wait at least until some basic binaries get built on the server. I
> assume that your existing binaries still work?
> 
> Arjun: we should check in case the web app needs any adjustments. We
> will probably no longer have the "legacy" workers.
> 
> Mojca

Re: Problems with MP 2.6.0 on Snow Leopard

[Mojca Miklavec]

On Mon, 23 Sep 2019 at 11:38, Rob Widdicombe wrote:
>
> Hi,
>
> Bear with me - I'm a musician, not a Unix expert, but I'm doing my best!
>
> I'm still resolutely running Snow Leopard and last night did a port 
> selfupdate to take me up to MP 2.6.0. So far so good.
>
> However, when I then tried to do a port rev-upgrade, the problems began.

Without looking at the individual logs yet ... as Ryan mentioned, we
would generally advice users of < 10.9 to wait a couple of more days
before doing the actual update.

https://lists.macports.org/pipermail/macports-users/2019-September/047381.html

This is something that we should probably write with some big warning
sign to both the homepage (download section) as well as under github
release.

Some pretty big fundamental changes were done for these old systems
and there were two options:
- put an extensive amount of effort and horsepower to run both
configurations in parallel for an extended period of time
- switch the default and cope with some issues for a limited period of
time, hoping that not too many users will be affected (too much)

Due to lack of manpower we went for the second option.

According to https://build.macports.org/waterfall?tag=10.6 the
buildbot workers were not even re-started yet, and I would expect a
couple of days (or weeks) for them to catch up. Ideally you would want
to wait at least until some basic binaries get built on the server. I
assume that your existing binaries still work?

Arjun: we should check in case the web app needs any adjustments. We
will probably no longer have the "legacy" workers.

Mojca

Problems with MP 2.6.0 on Snow Leopard

[Rob Widdicombe]

Hi,

Bear with me - I'm a musician, not a Unix expert, but I'm doing my best!

I'm still resolutely running Snow Leopard and last night did a port selfupdate 
to take me up to MP 2.6.0. So far so good.

However, when I then tried to do a port rev-upgrade, the problems began. It 
fails on the first step, upgrading gmp. Looking at the log files, it seems like 
it's expecting to find clang 8, and I have no idea why - I've never installed 
it and so, not surprisingly, it's not there.

I'm using:

Xcode 3.2
Component versions: DevToolsCore-1608.0; DevToolsSupport-1591.0
BuildVersion: 10D575

Here are the log files:



config.log
Description: Binary data


main.log
Description: Binary data


Just on the offchance that it would help I tried to install clang 8 but that 
failed, as I sort of expected it would.

I don't know if this is relevant but I did some time ago install the libcxx 
port, but this was to try to fool mainstream OSX programs that were designed 
for Lion and above (it didn't work!) rather than for any Macports-related 
stuff. Therefore I didn't mess with any of the Macports configuration as 
described in LibcxxOnOlderSystems. Nevertheless I've had a look at the 
macports.conf file to make sure that there's nothing untoward in there and, 
sure enough, everything is set to the defaults.

Any help will be gratefully received!

Many thanks,
Rob