Skip to content

Commit 49a9ba4

Browse files
authored
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 f212674 commit 49a9ba4

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

BUILDING.md

+5
Original file line numberDiff line numberDiff line change
@@ -593,6 +593,11 @@ rebuild may take a lot more time than previous builds. Additionally,
593593
ran `./configure` with non-default options (such as `--debug`), you will need
594594
to run it again before invoking `make -j4`.
595595

596+
If you received the error `nodejs g++ fatal error compilation terminated cc1plus`
597+
during compilation, this is likely a memory issue and you should either provide
598+
more RAM or create swap space to accommodate toolchain requirements or reduce
599+
the number of parallel build tasks (`-j<n>`).
600+
596601
### Windows
597602

598603
#### Tips

0 commit comments

Comments
 (0)