(moving to dev-builds) Background on our desire to use Node as part of the build can be found at https://groups.google.com/d/msg/mozilla.dev.builds/kuo6WycEcFk/jrdYydhHAQAJ and https://groups.google.com/d/msg/mozilla.dev.builds/L2Tp2uS1PGE/yiy30e1EAgAJ. The tl;dr is that not having access to the rich JavaScript tooling built on top of Node] burdens Firefox developers and hinders our ability to produce a high quality product efficiently.
Doing a little research, it appears that Node.js isn't supported on SPARC because V8 doesn't have a SPARC backend. That does seem like it will make it impossible to build Firefox on SPARC once the Node.js requirement is established :/ We knew some lesser-used platforms might run into problems like this. For Solaris, it should still be possible to cross-compile Firefox to SPARC from x86. So I don't believe the Node requirement will mean the end of Firefox on Solaris SPARC. On Mon, Aug 20, 2018 at 5:32 AM, <petr.sumb...@gmail.com> wrote: > Hi, > > I see now during configure following: > > 0:27.19 checking for nodejs... not found > 0:27.20 WARNING: could not find Node.js executable; ensure `node` or > `nodejs` is in PATH or set NODEJS in environment to point to an executable > 0:27.20 WARNING: (This will become a fatal error in the near future.) > > Is it necessary to make it hard requirement for Firefox build? It might be > quite problem to get Node.js for Solaris and mainly for sparc. > > Thanks, > > Petr > _______________________________________________ > tools mailing list > to...@lists.mozilla.org > https://lists.mozilla.org/listinfo/tools >
_______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
