Description
Hi,
I'm part of a small group holding on to older Mac hardware limited to "ancient" OS releases, in my case OS X 10.9.5 .
There is a "backported" Firefox build for us (Firefox Dynasty) and so-called legacy-support in MacPorts allows to run most OSS normally - among which nodejs18, esbuild and a new enough rust toolchain that static-filepicker can be built.
I thus had some hope that I'd be able to build vdhcoapp from source to obtain a runnable version, but I'm blocked.
- the 1st
pkginvocation that (apparently - I know nothing about Node) buildsvdhcoappdownloads afetched-v18.5.0-macos-x64binary that requires a___tststk_darwinsymbol which is not supported by MacPorts legacy-support, and is thus aborted by the loader. I have been unable to figure out how to install that executable from source. I've tried adding--buildto thepkginvocation but that also triggers a rebuild of Node18 itself which is complete overkill and bound to fail.
Where/how do I tell the build to build this executable, or how do I build it manually? - using
Node10instead ofNode18the build completes, but I end up with a crippledvdhcoappexecutable.
Running npm install --build-from-source fetched only gives me a JS file, no executable.
As a side-note: it's quite annoying that the package*.json files aren't being tracked; it took me hours to figure out that a requirement on an obsolete pkg version had been registered which can't work with node18 and tells that via a misleading error message (v4.5.1, so not even the version used for building with Node10).