Xu Meng
Xu Meng
> The `gyp/` changes are a duplicate of [nodejs/gyp-next#140](https://github.com/nodejs/gyp-next/pull/140). Ideally we'd merge in gyp-next and then update that here for those. > > Otherwise the node-gyp parts LGTM. Hello @richardlau...
> It looks like [nodejs/gyp-next#140](https://github.com/nodejs/gyp-next/pull/140) was released in [gyp-next v0.11.0](https://github.com/nodejs/gyp-next/releases/tag/v0.11.0) so the next step would be to update gyp-next here (e.g. similar to one of the previous gyp-next updates, #2521)....
Duplicated PR landed -- https://github.com/nodejs/node/commit/b99bb57416f5eabc9d8375b93e03de21d8ed29ee So I closed [feat(gyp): update gyp to v0.12.1](https://github.com/nodejs/node-gyp/pull/2642#)
> I used update-gyp.py to update to gpy-next v0.13.0 and rebased my changes. This should obsolete #2642. Closed issue [feat(gyp): update gyp to v0.12.1](https://github.com/nodejs/node-gyp/pull/2642#)
> LGTM. We could jump straight to gyp-next 0.12.1. Hello @richardlau , I have updated it to v0.12.1. But there are lots of ci failures.
Duplicated PR -- https://github.com/nodejs/node/commit/b99bb57416f5eabc9d8375b93e03de21d8ed29ee Close this.
Close this issue due to https://github.com/nodejs/node-gyp/pull/2626
> @dmabupt > > Any thoughts on what may be causing this issue? Seems to be an encoding issue. Need to reproduce it for debugging.
> Read through your references, but didn't got a clue how to proceed. > Maybe it's worth mentioning that our scripts run on the same IBM i system, where the...