Opened 4 years ago

Closed 4 years ago

#62649 closed defect (fixed)

Alacritty @0.7.2: destroot error on Apple M1 Silicon

Reported by: jianli-github (Jian Li) Owned by: herbygillot (Herby Gillot)
Priority: Normal Milestone:
Component: ports Version: 2.6.4
Keywords: Cc:
Port: alacritty

Description

Hi!

I saw the following error when building alacritty for Apple M1 Mac Mini

:debug:destroot Executing org.macports.destroot (alacritty)
:error:destroot Failed to destroot alacritty: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_alacritty/alacritty/work/alacritty-0.7.2/target/arm64-apple-darwin/release/alacritty": no such file or directory
:debug:destroot Error code: NONE
:debug:destroot Backtrace: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_alacritty/alacritty/work/alacritty-0.7.2/target/arm64-apple-darwin/release/alacritty": no such file or directory
:debug:destroot     while executing
:debug:destroot "$procedure $targetname"
:error:destroot See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_alacritty/alacritty/main.log for details.

I double checked the build directory, and it turns out there is folder name mismatch for the target, it seems like the Porfile was expecting the ${build_arch} to be arm64, whereas the target folder from the build is actually aarch64. I manually hacked the Portfile with a hardcoded aarch64 in place of ${build_arch} and the build was successful.

Maybe either the Porfile or the build scripts need to agree on the architecture naming when building for Apple M1 Silicon for the desroot?

Thanks, Jian

Change History (5)

comment:1 Changed 4 years ago by mf2k (Frank Schima)

Cc: herby.gillot@… removed
Owner: set to herbygillot
Status: newassigned

comment:2 Changed 4 years ago by herbygillot (Herby Gillot)

In 83d64452682712ccdedd44fc11b4f5d7f06db620/macports-ports (master):

alacritty: set appropriate release dir as per architecture

See: #62649

comment:3 Changed 4 years ago by herbygillot (Herby Gillot)

OK, I've committed a change that should do the right thing across all architectures. It might take a while to propagate to the mirrors, but perhaps you can try seeing if this works in a few hours.

comment:4 Changed 4 years ago by jianli-github (Jian Li)

Thanks! I confirm the fix works now.

Portfile changed since last build; discarding previous state.
Warning: The macOS 11.2 SDK does not appear to be installed. Ports may not build correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.
--->  Computing dependencies for alacritty
--->  Fetching archive for alacritty
--->  Attempting to fetch alacritty-0.7.2_1.darwin_20.arm64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/alacritty
--->  Attempting to fetch alacritty-0.7.2_1.darwin_20.arm64.tbz2 from https://kmq.jp.packages.macports.org/alacritty
--->  Attempting to fetch alacritty-0.7.2_1.darwin_20.arm64.tbz2 from https://mse.uk.packages.macports.org/alacritty
--->  Fetching distfiles for alacritty
--->  Verifying checksums for alacritty
--->  Extracting alacritty
--->  Configuring alacritty
--->  Building alacritty
--->  Staging alacritty into destroot
--->  Installing alacritty @0.7.2_1
--->  Cleaning alacritty
Warning: The macOS 11.2 SDK does not appear to be installed. Ports may not build correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.
--->  Deactivating alacritty @0.7.2_0
--->  Cleaning alacritty
--->  Activating alacritty @0.7.2_1
--->  Cleaning alacritty
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.

This ticket could be closed if needed.

comment:5 Changed 4 years ago by herbygillot (Herby Gillot)

Resolution: fixed
Status: assignedclosed

OK excellent. Closing this out.

Note: See TracTickets for help on using tickets.