-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Building Node.js broken when using ccache #40542
Comments
I'm running ccache on a Mac and have no problems, but I don't have the environment variables set. Instead, |
I'm also using an older version of ccache (3.4.2, whereas current is 4.4.2). |
Looking at https://github.com/ccache/ccache/blob/5243c21f4c7a8e048ac214bb5a1d78ddd769fbd1/doc/INSTALL.md, it appears that I've done the "use ccache for everything" method whereas our docs use the "try it out" method. That's probably what we want to suggest to users so that we don't affect compilation of other things. |
On the Jenkins CI we set e.g. https://ci.nodejs.org/job/node-test-commit-osx/42467/nodes=osx11-x64/consoleFull
|
This comment has been minimized.
This comment has been minimized.
Here's the relevant code in Lines 1444 to 1455 in f233cb2
What's the output when you run (EDIT: I get llvm_version 12.0 and xcode_version 12.0.) (EDIT 2: I guess you could just run |
I've replicated this issue. 👀 |
Using |
Line 32 of configure.py indicates that MacOS should use cc and everywhere else should use gcc. |
macOS requires `cc` and `c++` rather than `gcc` and `g++`. Closes: nodejs#40542
macOS requires `cc` and `c++` rather than `gcc` and `g++`. Closes: nodejs#40542
macOS requires `cc` and `c++` rather than `gcc` and `g++`. Closes: nodejs#40542
macOS requires `cc` and `c++` rather than `gcc` and `g++`. Closes: nodejs#40542
`ccache` has reasonable defaults for `max_size` and `cache_dir` so remove instructions to set those things explicitly. Change fenced code from `console` to `bash` for easier copy/paste. PR-URL: nodejs#40550 Fixes: nodejs#40542 Reviewed-By: Geoffrey Booth <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
macOS requires `cc` and `c++` rather than `gcc` and `g++`. Closes: #40542 PR-URL: #40550 Fixes: #40542 Reviewed-By: Geoffrey Booth <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
`ccache` has reasonable defaults for `max_size` and `cache_dir` so remove instructions to set those things explicitly. Change fenced code from `console` to `bash` for easier copy/paste. PR-URL: #40550 Fixes: #40542 Reviewed-By: Geoffrey Booth <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
macOS requires `cc` and `c++` rather than `gcc` and `g++`. Closes: #40542 PR-URL: #40550 Fixes: #40542 Reviewed-By: Geoffrey Booth <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
`ccache` has reasonable defaults for `max_size` and `cache_dir` so remove instructions to set those things explicitly. Change fenced code from `console` to `bash` for easier copy/paste. PR-URL: #40550 Fixes: #40542 Reviewed-By: Geoffrey Booth <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Version
master
@ f233cb2Platform
Darwin Geoffreys-MacBook-Pro.local 20.6.0 Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64 x86_64
What steps will reproduce the bug?
Follow the instructions in https://github.com/nodejs/node/blob/master/BUILDING.md#speeding-up-frequent-rebuilds-when-developing to install and configure
ccache
. (I’m on a Mac, so I didbrew install ccache
). In particular, don’t skip the steps toexport CC
andexport CXX
.Run
./configure
. I see this error:Run
unset CC GCC
. Then when I run./configure
the command completes successfully.How often does it reproduce? Is there a required condition?
Every time.
Additional information
cc @nodejs/build-files
The text was updated successfully, but these errors were encountered: