And this is for something that is known not to
work upstream. If you see what I mean.
Thanks.
> On Mar 13, 2021, at 10:38, Todd Doucet wrote:
>
> > At some point I might try to determine whether I can get a useful python3
> > setup using Macports, but it is time-consuming an
To be super-clear, the problems I am describing all relate to the M1 version of
the python libraries.
> At some point I might try to determine whether I can get a useful python3
> setup using Macports, but it is time-consuming and the status pages do not
> help, as the comments indicate.
>
> W
At some point I might try to determine whether I can get a useful python3 setup
using Macports, but it is time-consuming and the status pages do not help, as
the comments indicate.
When I tried a few weeks ago, I could install either py38 or py39, and that is
fine if I want to write "hello worl
I think one can only get so far with purely qualitative analysis of the
characteristics of SSDs and HDs and then the end of that analysis will be
one-size-fits all advice, for example "recommended" or "not recommended" for
servers.
Surely the answer might vary depending on the particular server
Many new users, like me, might not know what the consequences of the build
servers being down are, exactly. I am speculating that this does not mean that
MacPorts is not available generally, but instead that if I ask for a port it
might build it on my machine instead of pulling a pre-built bina
> The rest of the contiguous United States shares either the east or west power
> grid, but most of Texas uses its own separate grid managed by ERCOT.
> Unfortunately right now most of Texas is very cold and everybody is using
> more electricity running their heaters. At the same time, the wea
Correction:
port install depof:whatever
(This is a new machine and I have not yet turned off the obnoxious autospelling
correction.
>
>
>>
>> On 14 Feb2021, at 2:12 AM, Ryan Schmidt wrote:
>>>
>>>
>>> On Feb 13, 2021, at 11:33, Murray Eisenberg wrote:
>>>
Without complaint, wxMaxi
>
> On 14 Feb2021, at 2:12 AM, Ryan Schmidt wrote:
>>
>>
>> On Feb 13, 2021, at 11:33, Murray Eisenberg wrote:
>>
>>> Without complaint, wxMaxima @20.04.0_0 installed (after maxima
>>> @5.43.2_12+xmaxima and gnuplot
>>> @5.4.1_2+aquaterm+luaterm+pangocairo+qt+wxwidgets+x11) under macOS Big
>
>
> On Feb 11, 2021, at 19:32, Todd Doucet wrote:
>
> > So I guess there is still a bit of a mystery. If I get some time I will
> > try to build the new MacPorts from source and see if there is still a
> > warning. (I presently do not rely on MacPor
> On Feb 11, 2021, at 18:47, Todd Doucet wrote:
>
> > You can see that there are two SDKs here, including the one that you
> > expect, and the name MacOSX.sdk links to it too:
> >
> > % ls -l /Library/Developer/CommandLineTools/SDKs
> >
> > l
It is a little odd that one of the package receipts is not named
com.apple.pkg.CLTools_SDK_macOS111
but instead is named
com.apple.pkg.CLTools_SDK_macOS110
>
>> MacPorts 2.6.4 was released before Apple released macOS 11.1. We did not yet
>> know how the version numbers of macOS and th
> MacPorts 2.6.4 was released before Apple released macOS 11.1. We did not yet
> know how the version numbers of macOS and the macOS SDK would progress under
> macOS 11. We made a guess based on what had happened in macOS 10.15 and
> earlier, and we guessed wrong. We have corrected the code alr
I have read everything I can about this warning, but none of it corresponds to
exactly my situation, hence this report.
I have a brand new Mac Mini M1, and a fresh MacPorts installation. This is not
an upgrade--I have never had MacPorts on this machine, ever.
I definitely have both Xcode 12.4
13 matches
Mail list logo
