jam at tigger.ws
Sun May 1 07:06:27 UTC 2022
> On 1 May 2022, at 6:00 am, Craig Treleaven <ctreleaven at cogeco.ca> wrote:
>> On Apr 30, 2022, at 3:20 PM, James <jam at tigger.ws> wrote:
>>> sudo port clean libgcc11
>>> # Most folks run the following 2 commands on a regular basis (weekly, monthly)
>>> sudo port selfupdate
>>> sudo port upgrade outdated
>>> sudo port install libjpeg-turbo
>> [haycorn] /Users/jam % sudo port upgrade outdated
>> ---> Computing dependencies for libgcc11
>> ---> Fetching archive for libgcc11
>> ---> Attempting to fetch libgcc11-11.3.0_1.darwin_17.x86_64.tbz2 from http://packages.macports.org/libgcc11
>> ---> Attempting to fetch libgcc11-11.3.0_1.darwin_17.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/libgcc11
>> ---> Attempting to fetch libgcc11-11.3.0_1.darwin_17.x86_64.tbz2 from http://kmq.jp.packages.macports.org/libgcc11
>> ---> Building libgcc11
>> Error: Failed to build libgcc11: command execution failed
>> Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc11/libgcc11/main.log for details.
>> Error: Problem while installing libgcc11
>> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
> You didn’t say so I have to ask—did you do the 2 prior commands before the one you show above? Did they succeed?
> It is NOT expected that you should have to build libgcc from source. However, I’ve dug into it and it appears the MacPorts machine that builds the binary installer for your OS version did not run or didn’t finish. (The set of jobs to build for the various supported OS versions ran for over 8 hours!) Hopefully, that should fix itself on the next update to libgcc11.
> The log tail that you included doesn’t actually show the errors. Please put the full log on a pastebin somewhere and I’ll have a look at it.
> Depending on your hardware, building libgcc11 is going to take a LONG time. I believe you need to have several GB of free disk space. Obviously, the more RAM the machine has, the faster the process will go. If I were you, I’d restart the machine
> before letting it run overnight on the build.
> There is a chance we might be able to stick handle around the libgcc11 issue. Please check what version(s) you previously had installed with:
> port installed libgcc11
> Please let me know what the output is.
> BTW, is it possible for you to update to a more recent OS version? I believe the reason you need libgcc11 is that some dependency requires more-modern compiler features than Xcode on High Sierra can deliver. Plus, High Sierra hasn’t received security updates for a long time.
Craig thanks for the help!
I did do
sudo port selfupdate
The update bit worked fine. But thereafter chaos. I followed the wiki on migration but got trapped in
Error: we appear to be stuck, exiting...
invoked from within
"set operationList [sort_ports $portList]"
so I'll do a new macports, then build mythtv, then install *my* ports
I've an iMac27 stuck on High Sierra. I put 2T of flash instead of HD. It's a 4 core i5 with 16G ram so it's actually quite a nice machine. It does not run linux well (gets HOT) but is a wonderful farm for my linux VMs
BUT mythtv is nicer native than in a vm.
Lots of work ahead, but the way is clear. The alternative is to just live with fixes/31
More information about the mythtv-users