nodejs10 @10.18.1: build fails on Catalina with error related to assembler

[6aKa]

:info:configure creating config.gypi
:info:configure creating config.status
:info:configure creating config.mk
:info:configure running:
:info:configure     python tools/gyp_node.py --no-parallel -f make-mac
:info:configure Error running GYP
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_nodejs10/nodejs10/work/node-v10.16.3" && ./configure --prefix=/opt/local --without-npm --with-intl=small-icu --dest-cpu=x64
:info:configure Exit code: 1
:error:configure Failed to configure nodejs10: 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_macports_release_tarballs_ports_devel_nodejs10/nodejs10/main.log for details.

[mf2k (Frank Schima)]

In the future, please fill in the Port field and add the port maintainer(s) to Cc (port info --maintainers nodejs10), if any.

[kieranhood (Kieran Hood)]

I'm getting the same error. The output from the configure command that it is failing on in main.log is related to the assembler, any ideas for a solution on this?

cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_nodejs10/nodejs10/work/node-v10.16.3" && ./configure --prefix=/opt/local --without-npm --with-intl=small-icu --dest-cpu=x64

ERROR: Did not find a new enough assembler, install one or build with
       --openssl-no-asm.
       Please refer to BUILDING.md

[6aKa]

One of solution:

1. Add nasm (lang) as build dependency.
2. Fix regexp match in def get_nasm_version in configure.py change re.match(r"NASM version ([2-9]\.[0-9][0-9]+)" to re.match(r"NASM version ([2-9](\.[0-9][0-9]+){1,2})"

[pturley0]

While waiting for the fix to be applied and published, is there anything I can do locally to get the installation working on my machine? (I'm dead in the water)

I've manually installed nasm but, of course, that doesn't solve the other problem outlined above.

I would be able to answer this for myself if I were intimately familiar with the MacPorts build process, but that's a bridge I've never needed to cross before.

[murrayE]

Is there any hope of getting nodejs10 fixed soon?

[kencu (Ken)]

<​https://build.macports.org/builders/ports-10.15_x86_64-builder/builds/20320/steps/install-port/logs/stdio>

[kencu (Ken)]

This might prove helpful for Catalina users <​https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md>.

[murrayE]

The reference to ​https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md#Solutions seems to be of no use to me whatsoever.My macOS 10.15.2 system fails both "acid tests". However: I already installed the Xcode Command Line Tools; xcode-select -- install says they're already installed; and I cannot access the tools separately from developer.apple.com/download.

Command xcode-select -version gives output "xcode-select version 2373.".

Command softwareupdate -l finds "No new software available."

Command xcode-select -print-path gives /Applications/Xcode.app/Contents/Developer and NOT /Library/Developer/CommandLineTools !!

Finally, I tried the "I did all that and the acid test still does not pass". So I ran:

sudo rm -rf $(xcode-select -print-path) xcode-select --install

I get output again, "xcode-select: error: command line tools are already installed, use "Software Update" to install updates:.

So I'm at an impasse.

Again I ask: can we expect a fix to the nodejs10 port any time soon?

That port was OK prior to 10.15.2, or at least prior to 10.15.

[kencu (Ken)]

I cannot access the tools separately from developer.apple.com/download.

why not?

[murrayE]

I cannot see any separate entry for the Xcode command line tools at developer.apple.com/download ! I do see, on the Release tab, Xcoce 11.3.1, which I previously downloaded and installed from the App Store. And when I installed it, I was prompted to install "additional components".

I already have the CLT installed for this version of Xcode.

[kencu (Ken)]

You don't see <​https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_11.3/Command_Line_Tools_for_Xcode_11.3.dmg>?

Maybe that link will help you find them.

Perhaps with those, and the directions in <​​https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md> you might make some headway.

[murrayE]

No, I cannot see the cited URL for Command_Line_Tools_for-Xcode_11.3.dmg ! If I try to go there, it says: "Sorry, you cannot view this page. The Apple ID you signed in with does not have permission to view this page."

I currently do not have a paid Apple developer account.

[ryandesign (Ryan Carsten Schmidt)]

You do not need a paid Apple developer account in order to log in and download files. A free account is sufficient.

[murrayE]

Got it now, after renewing paid Developer account. However, the download is Command LIne Tools for Xcode 11.3, whereas the current released version of Xcode, which I have installed, is 11.3.1. Will that be a mismatch?

In any case, all the usual commands say that the command-line tools are already installed!

There seems to have been some change in the nodejs10 port that is not recognizing the location of those tools.

[murrayE]

I found CLT 11.3.1 finally, downloaded and installed. Now nodejs10 built successfully.