Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Suppress -std=c++0x option for zOS #2553

Closed
wants to merge 1 commit into from
Closed

Conversation

joransiu
Copy link

@joransiu joransiu commented Dec 4, 2018

The njsc/c++ compiler used for Node.js on z/OS has C++11 support by
default. The -std=c++0x option currently triggers a FSUM3210 error,
hence, updating gyp files to suppress use of this option on the
platform (similar to what's currently done for Windows).

Signed-off-by: Joran Siu [email protected]

The njsc/c++ compiler used for Node.js on z/OS has C++11 support by
default.  The -std=c++0x option currently triggers a FSUM3210 error,
hence, updating gyp files to suppress use of this option on the
platform.

Signed-off-by: Joran Siu <[email protected]>
@nschonni
Copy link
Contributor

nschonni commented Dec 7, 2018

@xzyfer don't think this hurts (event if we don't support zOS), but I'm wondering about the upstream libsass change to swap this old flag for the newer c++11 version

@xzyfer
Copy link
Contributor

xzyfer commented Dec 7, 2018 via email

@saper
Copy link
Member

saper commented Oct 21, 2019

Around 3.5.0 (upgrade to node-gyp after 3.2.0) we have lost ability to build on CentOS 5.
I tried it for fun and there are a couple of things - to run tests, one needs to install git from non-official repositories; https://github.com links no longer work due to TLS issues; python 2.4.3 is the latest version, and gyp needs 2.5 in the version we are using as of 4.12.0

Therefore I believe we should drop this altogether, for all platforms.

saper added a commit to saper/node-sass that referenced this pull request Oct 21, 2019
@saper saper self-assigned this Oct 21, 2019
xzyfer pushed a commit that referenced this pull request Nov 8, 2019
@nschonni
Copy link
Contributor

These are dropped now for all platforms

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants