Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Сould not install on Mac OS Catalina #16

Closed
sashabeep opened this issue Oct 21, 2019 · 32 comments
Closed

Сould not install on Mac OS Catalina #16

sashabeep opened this issue Oct 21, 2019 · 32 comments

Comments

@sashabeep
Copy link

Full screen of errors, mainly due to permissions and so. Can't figure out how to install it.
Installation guide requires update

@DanielRuf
Copy link
Contributor

Hi @sashabeep,

can you provide some more info like your NodeJS version?

@DanielRuf DanielRuf added the bug label Oct 21, 2019
@sashabeep
Copy link
Author

sashabeep commented Oct 21, 2019

v10.16.3
Xcode command line tools installed as well
End of log file

12292 verbose stack Error: [email protected] postinstall: `node scripts/build.js`
12292 verbose stack Exit status 1
12292 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/no$
12292 verbose stack     at EventEmitter.emit (events.js:198:13)
12292 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/no$
12292 verbose stack     at ChildProcess.emit (events.js:198:13)
12292 verbose stack     at maybeClose (internal/child_process.js:982:16)
12292 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.$
12293 verbose pkgid [email protected]
12294 verbose cwd /Users/sashabeep/node-foundation-customizer
12295 verbose Darwin 19.0.0
12296 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
12297 verbose node v10.16.3
12298 verbose npm  v6.9.0
12299 error code ELIFECYCLE
12300 error errno 1
12301 error [email protected] postinstall: `node scripts/build.js`
12301 error Exit status 1
12302 error Failed at the [email protected] postinstall script.
12302 error This is probably not a problem with npm. There is likely additional logging$
12303 verbose exit [ 1, true ]

screen output
Снимок экрана 2019-10-21 в 17 32 40

@DanielRuf
Copy link
Contributor

You have to probably run xcode-select --install.

@sashabeep
Copy link
Author

It's already installed

xcode-select: error: command line tools are already installed, use "Software Update" to install updates

@DanielRuf
Copy link
Contributor

So Xcode is not installed / updated then?

@DanielRuf
Copy link
Contributor

In general this is a node-gyp issue with missing build deps on your system, not this project =)

@sashabeep
Copy link
Author

Xcode not installed, only command line tools. It was always enough...

@DanielRuf
Copy link
Contributor

xcode CLI does not work without Xcode ;-)

@sashabeep
Copy link
Author

xcode CLI does not work without Xcode ;-)
No, it's wrong.

@DanielRuf
Copy link
Contributor

Well, the terminal output says it =) And this is a node-gyp issue if it is one at all, not a foundation-* issue =)

@DanielRuf
Copy link
Contributor

See nodejs/node-gyp#569 and other relevant issues.

Closing as this is not an issue on our end and not specific to node-foundation-customizer.

@DanielRuf
Copy link
Contributor

Also relevant:

schnerd/d3-scale-cluster#7
tensorflow/tfjs#372
...

@sashabeep
Copy link
Author

npm ERR! Failed at the [email protected] postinstall script.

node-sass 4.5.3 does not supported by node 10x sass/node-sass#2672 (comment)

@DanielRuf
Copy link
Contributor

It will be built from source in this case.

I tried to install node-sass 4.5.3 on 10.16.3 on Mojave and it works:

➜  node-sass-test yarn init -y
yarn init v1.19.0
warning The yes flag has been set. This will automatically answer yes to all questions, which may have security implications.
success Saved package.json
✨  Done in 0.04s.
➜  node-sass-test node --version
v10.16.3
➜  node-sass-test yarn add [email protected]
yarn add v1.19.0
info No lockfile found.
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
success Saved lockfile.
success Saved 152 new dependencies.
info Direct dependencies
└─ [email protected]
info All dependencies
...
├─ [email protected]
...
✨  Done in 146.23s.
➜  node-sass-test 

Same for npm here:

➜  node-sass-test npm i
...
gyp info ok 
Installed to /Users/danielruf/projects/node-sass-test/node_modules/node-sass/vendor/darwin-x64-64/binding.node
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN [email protected] No description
npm WARN [email protected] No repository field.

added 176 packages from 139 contributors and audited 516 packages in 148.607s
found 0 vulnerabilities

➜  node-sass-test npm ls --depth=0
[email protected] /Users/danielruf/projects/node-sass-test
└── [email protected]

npm ERR! Failed at the [email protected] postinstall script.

Please provide the whole console output as I can not reproduce this.

@nfantone
Copy link

Same over here. I can confirm that installing xcode CLI only has always been enough - but after upgrading to macOS Catalina, node-gyp started complaining about gyp: No Xcode or CLT version detected!.

❯ xcode-select --install
xcode-select: error: command line tools are already installed, use "Software Update" to install updates

> yarn
[...]
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

gyp: No Xcode or CLT version detected!
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/Cellar/node@10/10.16.3/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:345:16)

@nfantone
Copy link

@DanielRuf

Well, the terminal output says it

Not really, no. The terminal output, if it is to be trusted, explicitly says that is looks for DeveloperToolsCLILeo and DeveloperToolsCLI. No need for a full XCode installation.

@Vishesh-Gupta
Copy link

Vishesh-Gupta commented Oct 22, 2019

Having the exact same issue after updating to the latest release on macOS Catalina. It was working completely fine before the improvements and stability release for Cataline. Anything that can be used to fix this for now?

@DanielRuf
Copy link
Contributor

In general this is an issue with node-gyp I guess. Nothing that we can track or fix in this case here.

@sashabeep
Copy link
Author

sashabeep commented Oct 22, 2019

@DanielRuf That's pity, i think i will try this on VM with other OS later. Waiting for new version and online customizer wake-up. Using simple template with foundation-cli or "download everything" on the site i cannot uncheck various js plugins i don't use, and ZURB template is too complicated for me at this point

@jhwinter
Copy link

If you're having issues even after doing xcode-select --install, try sudo xcode-select --reset. Check the path variable before and after with xcode-select -print-path to make sure that it updates properly.

@meanmachin3
Copy link

I can confirm too. Tried sudo xcode-select --reset and xcode-select --install. Doesn't seem to be working

No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

gyp: No Xcode or CLT version detected!
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/Users/meanmachin3/github/meanmachin3.github.io/node_modules/node-gyp/lib/configure.js:345:16)
gyp ERR! stack     at ChildProcess.emit (events.js:209:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 19.0.0
gyp ERR! command "/usr/local/Cellar/node/12.10.0/bin/node" "/Users/meanmachin3/github/meanmachin3.github.io/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /Users/meanmachin3/github/meanmachin3.github.io/node_modules/node-sass
gyp ERR! node -v v12.10.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

@DanielRuf
Copy link
Contributor

Please see nodejs/node-gyp#1861, nodejs/node-gyp#1927 and the other issues and report this at node-gyp.

This is nothing that we can handle or fix as I already wrote and our issue tracker is not the right place for this thirdparty dependency which is part of NodeJS =)

@DanielRuf DanielRuf removed the bug label Oct 23, 2019
@DanielRuf
Copy link
Contributor

And also nodejs/node-gyp#1861 (comment) for some steps which you can try.

@kpalem
Copy link

kpalem commented Oct 24, 2019

If you're having issues even after doing xcode-select --install, try sudo xcode-select --reset. Check the path variable before and after with xcode-select -print-path to make sure that it updates properly.

This worked for me, Thank you!

@maxcbc
Copy link

maxcbc commented Oct 25, 2019

You might need to open Xcode, then in the menu go to
Xcode > Preferences > Locations > Command Line Tools
and then select a version.
This fixed it for me

@avega04
Copy link

avega04 commented Oct 25, 2019

Removing and reinstalling the command line tools does the trick:

  1. sudo rm -rf $(xcode-select -print-path) # Enter root password. No output is normal.
  2. xcode-select --install

(From https://github.com/nodejs/node-gyp/pull/1940/files)

@mdoghri
Copy link

mdoghri commented Oct 27, 2019

You might need to open Xcode, then in the menu go to
Xcode > Preferences > Locations > Command Line Tools
and then select a version.
This fixed it for me

Worked for me as well. Thanks!

@asfdasfsdfsfd
Copy link

Removing and reinstalling the command line tools does the trick:

  1. sudo rm -rf $(xcode-select -print-path) # Enter root password. No output is normal.
  2. xcode-select --install

(From https://github.com/nodejs/node-gyp/pull/1940/files)

This worked for me, Thank you

@sashabeep
Copy link
Author

@mlx-martin in my case still getting those errors, so i'll leave it for now

gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/Users/sashabeep/node-foundation-customizer/node_modules/node-gyp/lib/configure.js:305:16)
gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Darwin 19.0.0
gyp ERR! command "/usr/local/bin/node" "/Users/sashabeep/node-foundation-customizer/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /Users/sashabeep/node-foundation-customizer/node_modules/node-sass
gyp ERR! node -v v10.16.3
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 
Build failed with error code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

@DanielRuf
Copy link
Contributor

gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1

There is some error above this.

@dgonch5
Copy link

dgonch5 commented Nov 6, 2019

Removing and reinstalling the command line tools does the trick:

  1. sudo rm -rf $(xcode-select -print-path) # Enter root password. No output is normal.
  2. xcode-select --install

(From https://github.com/nodejs/node-gyp/pull/1940/files)

Worked for me! Thank you.

@DanielRuf
Copy link
Contributor

I'm locking this issue as it should be resolved and comments like "I have this too" and "thanks it works now" do not contribute any new things. This sends a notification to everyone in this issue.

Please use the linked node-gyp issue if you still face this problem.

Closing as resolved.

@foundation foundation locked as resolved and limited conversation to collaborators Nov 6, 2019
@DanielRuf DanielRuf pinned this issue Nov 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests