nodejs13 (13.4.0) build fails due to incorrect version, issue finding Xcode information

[forrie (Forrest)]

The port update to this appears to have a typo or there is a file missing at packages.macports.org. Presently, the port build is failing as it cannot locate this file:

msg:archivefetch --->  Attempting to fetch nodejs13-13.4.0_0.darwin_19.x86_64.tbz2 from https://packages.macports.org/nodejs13 

The highest revision I see there is this:

​http://packages.macports.org/nodejs13/nodejs13-13.4.0_0.darwin_18.x86_64.tbz2

---

From the Log:

:debug:configure LIBRARY_PATH='/opt/local/lib'
:debug:configure MACOSX_DEPLOYMENT_TARGET='10.15'
:debug:configure OBJC='/usr/bin/clang'
:debug:configure OBJCFLAGS='-pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -arch x86_64'
:debug:configure OBJCXX='/usr/bin/clang++'
:debug:configure OBJCXXFLAGS='-pipe -Os -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -arch x86_64'
:debug:configure PYTHON='/opt/local/bin/python3.8'
:debug:configure SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk'
:info:configure Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_nodejs13/nodejs13/work/node-v13.5.0" && ./configure --prefix=/opt/local --without-npm --with-intl=system-icu --shared-openssl --shared-openssl-includes=/opt/local/include/openssl --shared-openssl-libpath=/opt/local/lib --dest-cpu=x64
:debug:configure system:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_nodejs13/nodejs13/work/node-v13.5.0" && ./configure --prefix=/opt/local --without-npm --with-intl=system-icu --shared-openssl --shared-openssl-includes=/opt/local/include/openssl --shared-openssl-libpath=/opt/local/lib --dest-cpu=x64
**:info:configure No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
:info:configure No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.
:info:configure No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.
:info:configure gyp: No Xcode or CLT version detected!
:info:configure Node.js configure: Found Python 3.8.0...
:info:configure Error running GYP
:info:configure Command failed:  cd** "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_nodejs13/nodejs13/work/node-v13.5.0" && ./configure --prefix=/opt/local --without-npm --with-intl=system-icu --shared-openssl --shared-openssl-includes=/opt/local/include/openssl --shared-openssl-libpath=/opt/local/lib --dest-cpu=x64
:info:configure Exit code: 1
:error:configure Failed to configure nodejs13: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure     while executing
:debug:configure "$procedure $targetname"
:error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_nodejs13/nodejs13/main.log for details.

[jmroot (Joshua Root)]

Binaries don't appear instantly for new versions, and when there's no binary, MacPorts can (and with default settings will) fall back to building from source.

[forrie (Forrest)]

Appended additional failure log output to ticket.

[mf2k (Frank Schima)]

Please use WikiFormatting.

[mf2k (Frank Schima)]

The available archives have nothing to do with your issue. The error is:

gyp: No Xcode or CLT version detected!

[jmroot (Joshua Root)]

And the archive for Catalina is now up, which should solve your immediate problem (though you should still sort out your Xcode and/or CLTs situation).

[kencu (Ken)]

see also #59490. It has a workaround that worked for one person.

It appears nodejsN does some kind of check for installed toolchain receipts and errors out if they are not found -- at least that is my guess, based on the errors exhibited.