Migration Errors after Sequoia

Lenore Horner lenorehorner at sbcglobal.net
Sun Sep 22 11:09:22 UTC 2024



> On Sep 22, 2024, at 05:49, Michael Newman via macports-users <macports-users at lists.macports.org> wrote:
> 
> I’m sorry, but this is way beyond my ability. I have many questions.
> 
> The guide to filing a ticket says "Clean and try again”
> 
> • Does “clean” mean I should run "sudo port -f clean --all all”
> • Does “try again” mean I should run "sudo port migrate” again, or try to install each failed port separately?
> • Since three of the failures were based on aom, should I try and install aom separately, or what?
Tickets should be filed for particular ports as far as I know which means you should clean that port that isn't installing (or in this case the port that's blocking other ports). 
run "sudo port clean --all aom"
run "sudo port install aom"
If it still fails, create a ticket and attach the log file to the ticket.
> 
> I ran clean as described above and got zillions of messages like: "Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option”
> 
> Note that the command line tools seem to be installed:
> 
> Fifteen:~ mnewman$ pkgutil --pkg-info=com.apple.pkg.{CLTools_Executables,CLTools_Base,DeveloperToolsCLI,DeveloperToolsCLILeo} 2>/dev/null | sed -n 's/^version: //p'
> 16.0.0.0.1.1724870825
> 
> As you can probably tell, I am neither knowledgeable nor very smart, so I’ll need step-by-step instructions as to what to do.
> 
> Sorry,
> 
> Mike Newman
> 
> 
>> On Sep 22, 2024, at 14:49, Christopher Jones <jonesc at hep.phy.cam.ac.uk> wrote:
>> 
>>> 
>>> That log file is extremely long; too long to include with this message. But, there is this:
>> 
>> you should never send attachments to this list anyway. See below.
>> 
>>> 
>>> :info:build Exit code: 2
>>> :error:build Failed to build aom: command execution failed
>>> :debug:build Error code: CHILDSTATUS 2671 2
>>> :debug:build Backtrace: command execution failed
>>> :debug:build     while executing
>>> :debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
>>> :debug:build     invoked from within
>>> :debug:build "command_exec -callback portprogress::target_progress_callback build"
>>> :debug:build     (procedure "portbuild::build_main" line 10)
>>> :debug:build     invoked from within
>>> :debug:build "$procedure $targetname"
>>> 
>>> I have no idea how to fix any of this. Everything else worked so I’m assuming that I did the right things with Xcode and the CL Tools.
>>> 
>>> Detailed instructions appreciated.
>> 
>> The above its pretty useless to help you, we need the full logs.
>> 
>> Follow the instructions at
>> 
>> https://trac.macports.org/wiki/Tickets
>> 
>> to first check if there is an existing ticket for your issue, and if not file a new one. Upload a complete (compressed) log from a clean build attempt there.
>> 
>> Chris
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20240922/03a50be2/attachment.htm>


More information about the macports-users mailing list