Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 03 Sep 2022 07:13:40 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 266188] devel/electron18: Fails to build (after www/npm upgrade?)
Message-ID:  <bug-266188-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266188

            Bug ID: 266188
           Summary: devel/electron18: Fails to build (after www/npm
                    upgrade?)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: zirias@freebsd.org
                CC: sunpoet@FreeBSD.org, tagattie@FreeBSD.org
                CC: tagattie@FreeBSD.org

I'm getting this error message building electron18:

---
[  1% 578/42893] python3 ../../electron/build/npm-run.py --silent pre-fligh=
t --
--stamp
/wrkdirs/usr/ports/devel/electron18/work/electron-18.3.9/src/out/Release/ge=
n/electron/npm_pre_stamps/npm_pre_flight_build_electron_definitions.stamp
FAILED:
gen/electron/npm_pre_stamps/npm_pre_flight_build_electron_definitions.stamp=
=20
python3 ../../electron/build/npm-run.py --silent pre-flight -- --stamp
/wrkdirs/usr/ports/devel/electron18/work/electron-18.3.9/src/out/Release/ge=
n/electron/npm_pre_stamps/npm_pre_flight_build_electron_definitions.stamp
NPM script 'pre-flight' failed with code '127':
pre-flight --stamp
/wrkdirs/usr/ports/devel/electron18/work/electron-18.3.9/src/out/Release/ge=
n/electron/npm_pre_stamps/npm_pre_flight_build_electron_definitions.stamp:
--: not found

ninja: build stopped: subcommand failed.
*** Error code 1
---

This worked previously on the same builder machine with the same configurat=
ion,
so I assume it's a change in npm 8.18.0 causing this.

All I tried is patching out the '--' in the command line, which doesn't hav=
e a
visible effect, it still prints ': --: not found'.

CC @sunpoet hoping you might know what needs patching here ;)

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266188-7788>