Commit fff8eb2
doc: expand troubleshooting section
Update the troubleshooting section with regards to
memory requirements and potential errors. This error
specifically happened to me on an Ubuntu host with
2GB of RAM which wasn't enough and g++ error'ed
during Node.js compilation step.
PR-URL: #53808
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>1 parent 4021215 commit fff8eb2
1 file changed
Lines changed: 5 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -600,6 +600,11 @@ rebuild may take a lot more time than previous builds. Additionally, | |||
| 600 | 600 | ran `./configure` with non-default options (such as `--debug`), you will need | |
| 601 | 601 | to run it again before invoking `make -j4`. | |
| 602 | 602 | ||
| 603 | + If you received the error `nodejs g++ fatal error compilation terminated cc1plus` | ||
| 604 | + during compilation, this is likely a memory issue and you should either provide | ||
| 605 | + more RAM or create swap space to accommodate toolchain requirements or reduce | ||
| 606 | + the number of parallel build tasks (`-j<n>`). | ||
| 607 | + | ||
| 603 | 608 | ### Windows | |
| 604 | 609 | ||
| 605 | 610 | #### Tips | |
0 commit comments