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
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
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
> 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
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
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
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:
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
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
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.
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
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
12 matches
Mail list logo
