On 24 Feb 2020, at 21:07, Ken Cunningham wrote:
clang-5.0 is pretty close to what the current Xcode compilers are
like, in terms of strictness and severity, and indeed, clang-5.0 build
this software quite easily, but with a lot of warnings, of course.
For what it's worth...
Clang 8 is now th
:info:build ../include/Ptr.h:72:11: error: ISO C++11 does not allow access
declarations; use using declarations instead
:info:build Ptr::isNull;
clang-9.0 (the current 10.6.8 default) is incredibly strict. Far stricter than
any current Xcode compiler.
having said that, when I just tried, it
Trying to fix some (a lot of) broken ports. Running into a snag with
opensp, which fails to build.
This is surprising as I must have had at some point a working install of
it. Personally I don't care at all about opensp, but I guess one or more
ports do care.
Zipped Log attached.
Uli
<>
On 24.02.20 16:46 , Ryan Schmidt wrote:
On Feb 24, 2020, at 08:45, joerg van den hoff wrote:
after today's `selfupdate' and `upgrade outdated' hg errors out with
abort: No module named repo!
the proximal cause seems `hgsubversion'. if I avoid loading that extension in
my .hgrc, hg is back
On Feb 24, 2020, at 08:45, joerg van den hoff wrote:
> after today's `selfupdate' and `upgrade outdated' hg errors out with
>
> abort: No module named repo!
>
> the proximal cause seems `hgsubversion'. if I avoid loading that extension in
> my .hgrc, hg is back to normal. any ideas? new ticket
after today's `selfupdate' and `upgrade outdated' hg errors out with
abort: No module named repo!
the proximal cause seems `hgsubversion'. if I avoid loading that extension in my .hgrc, hg is back
to normal. any ideas? new ticket required?
seen on 10.15.2
thx/joerg
