Comments (9)
Is this specific to that docker container (or Debian), or can these reproduce on other Linux versions / containers?
from node.
Judging from the linked issue it's not specific to containers. With Alpine Linux there are other issues. Not this specific one.
from node.
FWIW I'm able to build fine on Kali Linux (which is based on Debian)
from node.
@RedYetiDev And which version of the compiler/library do you have there? In my case it must be this I guess:
$ dpkg -l | grep stdc++\\\|g++
ii g++ 4:12.2.0-3 amd64 GNU C++ compiler
ii g++-12 12.2.0-14 amd64 GNU C++ compiler
ii libstdc++-12-dev:amd64 12.2.0-14 amd64 GNU Standard C++ Library v3 (development files)
ii libstdc++6:amd64 12.2.0-14 amd64 GNU Standard C++ Library v3
from node.
I have a lot more:
ii g++ 4:13.2.0-7 amd64 GNU C++ compiler
ii g++-12 12.3.0-17 amd64 GNU C++ compiler
ii g++-13 13.2.0-25 amd64 GNU C++ compiler
ii g++-13-x86-64-linux-gnu 13.2.0-25 amd64 GNU C++ compiler for x86_64-linux-gnu architecture
ii g++-mingw-w64 13.2.0-19+26.3 all GNU C++ compiler for MinGW-w64
ii g++-mingw-w64-i686 13.2.0-19+26.3 all GNU C++ compiler for MinGW-w64 targeting Win32
ii g++-mingw-w64-i686-posix 13.2.0-19+26.3 amd64 GNU C++ compiler for MinGW-w64, Win32/POSIX
ii g++-mingw-w64-i686-win32 13.2.0-19+26.3 amd64 GNU C++ compiler for MinGW-w64, Win32/Win32
ii g++-mingw-w64-x86-64 13.2.0-19+26.3 all GNU C++ compiler for MinGW-w64 targeting Win64
ii g++-mingw-w64-x86-64-posix 13.2.0-19+26.3 amd64 GNU C++ compiler for MinGW-w64, Win64/POSIX
ii g++-mingw-w64-x86-64-win32 13.2.0-19+26.3 amd64 GNU C++ compiler for MinGW-w64, Win64/Win32
ii g++-x86-64-linux-gnu 4:13.2.0-7 amd64 GNU C++ compiler for the amd64 architecture
ii lib32stdc++6 14-20240330-1 amd64 GNU Standard C++ Library v3 (32 bit Version)
ii libconfig++9v5:amd64 1.5-0.4+b1 amd64 parsing/manipulation of structured configuration files (C++ binding)
ii libstdc++-12-dev:amd64 12.3.0-17 amd64 GNU Standard C++ Library v3 (development files)
ii libstdc++-13-dev:amd64 13.2.0-25 amd64 GNU Standard C++ Library v3 (development files)
ii libstdc++6:amd64 14-20240330-1 amd64 GNU Standard C++ Library v3
from node.
I meant the compiler/library you used to build NodeJS. Because it may have something to do with versions.
Anyway, I'll probably try to reconfirm it, but it seems to start to fail in this commit.
from node.
There's a bug in GCC 12 that causes these errors. We use GCC 11 in CI on Debian 12 to avoid it.
from node.
Indeed. With GCC 11 it succeeds:
docker run --rm debian:bookworm-slim bash -euxc '
apt-get update
apt-get install -y git python3 g++-11 make
git clone https://github.com/nodejs/node
cd node
CXX=g++-11 CC=gcc-11 ./configure
make
'
With GCC 12 it starts to fail in e4b187433d. If that's bug in GCC 12, case closed then I guess?
from node.
Closing as the issue seems to be with GCC12, if you disagree, reopen.
from node.
Related Issues (20)
- `napi_create_external_buffer` is super slow HOT 1
- FinalizationRegistry is not working for Timeout Object correctly, but WeakRef works fine HOT 4
- Erronous import failure message HOT 12
- test_runner: using module mocking confuses all future esm imports to use cjs path resolution HOT 3
- fetch failed with TypeError: Class extends value #<newConstructor> is not a constructor or null HOT 3
- v22.4.1 C++ addon incurs segmentation faults HOT 5
- Security question: Why are data: URIs and file: URIs treated differently in your security policy? HOT 5
- `ReadableStream.from({})` returns confusing error HOT 7
- `fsPromises.glob` doesn't call `exclude` with dirent when called `withFileTypes: true` HOT 2
- Web change HOT 2
- Add `--root-directory` optional flag for `node --run` HOT 4
- Easier MultiDimensional Array's HOT 2
- Support for running bin scripts using `node --run` HOT 3
- test: parallel/test-worker-node-options fails on IBM i HOT 1
- Got failure message - "FailureMessage Object: 0x7fedbceff920" HOT 1
- When `ReadableStream` read fails, stack trace does not include the line responsible HOT 6
- test_runner: do not read from `process.argv` and `process.cwd()` in run()
- test_runner: remove global event handlers after run is completed HOT 4
- doc: clarify Web Storage behavior HOT 3
- https://stackblitz.com/connect/70dbe416
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node.