xar @ 494.81.1: Does not successfully build when using non-default prefix/non sudo

[lukaso (Lukas Oberhuber)]

--->  Computing dependencies for llvm-15..
--->  Dependencies to be installed: xar
--->  Applying patches to xar
--->  Applying xar-1.8-Add-OpenSSL-To-Configuration.patch
Executing:  cd "/Users/user/macports-gimp3-arm64/var/macports/build/_Users_user_macports-gimp3-arm64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_archivers_xar/xar/work/xar-494.81.1/xar" && /usr/bin/patch -p0 < '/Users/user/macports-gimp3-arm64/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/archivers/xar/files/xar-1.8-Add-OpenSSL-To-Configuration.patch'

ls -las /opt/local/var/macports/build/_Users_user_macports-gimp3-arm64_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_archivers_xar/xar/work/xar-494.81.1/xar

is empty.

And when I try to apply the stalled command I get a prompt:

File to patch:

which hangs indefinitely.

This is occurring on Ventura with the 11.3 SDK.

[ryandesign (Ryan Carsten Schmidt)]

This shouldn't be happening, regardless of your prefix or whether or not your MacPorts is configured to require root, although if you are using the default prefix and other values, you will get a binary from us and avoid trying to compile from source.

Please run sudo port selfupdate to ensure you have MacPorts 2.8.1 and the latest port definitions. This port, and many others, will now fail to build with errors like these using MacPorts 2.8.0 and earlier because the code path that handled those older MacPorts versions has been removed. See #67031.

The transcript you posted does not look like a clean build attempt. (The fetch, checksum, and extract phases are not shown, meaning they were completed earlier and possibly incorrectly, for example if they were completed with MacPorts 2.8.0 or earlier.) Please sudo port clean xar and try again and if it fails again then attach the main.log file.

There is a known problem with the version of the patch command on Ventura and later where it doesn't like applying patches that have fuzz. It doesn't sound like that's what's going on here, and we had successful builds of this port on our buildbot workers, including the Ventura ones, however I do see that one of the patches has fuzz (and many of them apply with offsets) so it may be a good idea (Marius) to rebase those patches anyway.

[lukaso (Lukas Oberhuber)]

You were absolutely right that I was running 2.8.0. I didn't realize because the MacPorts install was going through a different code path. Thank you!