On Mar 15, 2020, at 09:13, Ken Cunningham wrote:
> on macports you pin a package using a personal repository.
>
> I explained it a few answers above. It's a very simple, 30 second, procedure.
But that is not what we want users to need to do. When a user encounters a
problem, we do not want
On Sat, Mar 14, 2020 at 11:24 AM Ryan Schmidt wrote:
>
> On Mar 14, 2020, at 00:39, Jeffrey Walton wrote:
>
> > My old PowerMac G5 cannot build the CMake being supplied with
> > MacPorts. I know CMake now requires C+11 or C++14, and the antique
> > tools on the Mac do not meet the requirements. I
On Mar 14, 2020, at 00:39, Jeffrey Walton wrote:
> My old PowerMac G5 cannot build the CMake being supplied with
> MacPorts. I know CMake now requires C+11 or C++14, and the antique
> tools on the Mac do not meet the requirements. I want to pin CMake to
> an older version for the Mac. For
you might be interested in this ticket re: cmake on 10.5 ppc
https://trac.macports.org/ticket/59832
tl;dr
it works if you activate libgcc7 7.4.0
My old PowerMac G5 cannot build the CMake being supplied with
MacPorts. I know CMake now requires C+11 or C++14, and the antique
tools on the Mac do not meet the requirements. I want to pin CMake to
an older version for the Mac. For example, 3.15.4 or 3.14.6.
How do I pin a package using
