On Apr 1, 2021, at 17:50, Artemio González López wrote:

> On 2 Apr 2021, at 00:43, Ryan Schmidt wrote:
> 
>> On Apr 1, 2021, at 17:05, Artemio González López wrote:
>> 
>>> When I tried to build the aom port in my MacBook Pro 13 M1 running Big Sur 
>>> 11.2.3 I got the following error:
>>> 
>>> make[1]: Leaving directory 
>>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_aom/aom/work/build'
>>> make: *** [all] Error 2
>>> make: Leaving directory 
>>> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_aom/aom/work/build'
>>> Command failed:  cd 
>>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_aom/aom/work/build"
>>>  && /usr/bin/make -j8 -w all VERBOSE=ON 
>>> Exit code: 2
>>> Error: Failed to build aom: command execution failed
>>> DEBUG: Error code: CHILDSTATUS 21399 2
>>> DEBUG: Backtrace: command execution failed
>>>    while executing
>>> "system {*}$notty {*}$nice $fullcmdstring"
>>>    invoked from within
>>> "command_exec build"
>>>    (procedure "portbuild::build_main" line 8)
>>>    invoked from within
>>> "$procedure $targetname"
>>> Error: See 
>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_aom/aom/main.log
>>>  for details.
>>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
>>> Error: Processing of port aom failed
>>> 
>>> Any clue as to what could be going on?
>> 
>> You didn't show the relevant part of the log which would have been earlier. 
>> However I did just fix one problem in aom [1] so please run `sudo port 
>> selfupdate` and then try again.
>> 
>> [1] 
>> https://github.com/macports/macports-ports/commit/b3032c313f268eb895a79f223143cb2c41909c17
> 
> Thanks a lot, Ryan. I tried to rebuild aom, but still failed with the 
> following error:

Ok, then please file a bug report attaching the full compressed main.log as 
usual.

Reply via email to