Well, I am familiar with the fall-back of fetching the distfiles.
In my case, it did NOT fetch the distfiles. Went straight to "staging...
to destroot".
Anyway, this problem seems fixed, Thanks much, Josh and all.
Uli
On 12/1/21 12:09 AM, Ryan Schmidt wrote:
On Nov 29, 2021, at 20:21,
On Nov 29, 2021, at 20:21, Uli Wienands wrote:
> Well, I wonder whether someone did something within the last day or two. I
> just tried it again, and lo-and-behold, perl5.26 installed just fine & now
> MacPorts is getting to work on the backlog of things that I could not update
> because
Well, I wonder whether someone did something within the last day or two.
I just tried it again, and lo-and-behold, perl5.26 installed just fine &
now MacPorts is getting to work on the backlog of things that I could
not update because of this problem.
This after I just found out (in debug
This looks as the same problem we have with MySQL57, where it's using
the system cctools instaead of the more modern cctools from macports.
The fix is described here :
https://trac.macports.org/ticket/59072#comment:1
declare usrBin='/usr/bin'
declare devBin="/Developer${usrBin}"
while read -u 9
Ulrich Wienands wrote:
The funny thing is that almost every Macports install seems to want to upgrade
this perl5.26; although as far as I can tell my perl5.26 is perfectly fine. So
I am forced to use -n for each install to get anything done, which I fond a bit
unsettling. Maybe I need to
> On Nov 27, 2021, at 8:09 PM, Ryan Schmidt wrote:
>
> On Nov 27, 2021, at 19:58, Ken Cunningham wrote:
>
>>> Ok... the significance of this is...??
>> Well in your case, the significance of appears overwhelming — in that it is
>> an excellent clue as to the cause of your problem, I
On Nov 27, 2021, at 19:58, Ken Cunningham wrote:
>> Ok... the significance of this is...??
> Well in your case, the significance of appears overwhelming — in that it is
> an excellent clue as to the cause of your problem, I believe.
>
> ie - there is nothing wrong on your system, it is nothing
> Ok... the significance of this is...??
Well in your case, the significance of appears overwhelming — in that it is an
excellent clue as to the cause of your problem, I believe.
ie - there is nothing wrong on your system, it is nothing you did, it is not
your fault, indeed something has
Ok... the significance of this is...??
The funny thing is that almost every Macports install seems to want to upgrade
this perl5.26; although as far as I can tell my perl5.26 is perfectly fine. So
I am forced to use -n for each install to get anything done, which I fond a bit
unsettling. Maybe
all the perl ports were specifically changed to use /usr/bin/cc in the
commit below, but something in this plan seems to be not working out:
On Nov 26, 2021, at 19:45, Uli Wienands wrote:
> A number of ports apparently want to install perl5.26. In this specific case
> it is fricas. For reasons I cannot fathom prl5.26 fails during the destroot
> phase on my system (SL, 10.6.8).
>
> So I try installing perl5.26 by itself; it fails
A number of ports apparently want to install perl5.26. In this specific
case it is fricas. For reasons I cannot fathom prl5.26 fails during the
destroot phase on my system (SL, 10.6.8).
So I try installing perl5.26 by itself; it fails with a message that
"clang-3.7" cannot be updated.
I try
12 matches
Mail list logo
