J’essaye de rattraper le retard de ma suivie du développement du logiciel Duniter.
Je n’arrive pas à compiler neon-sys qui est en v0.4.0, bien qu’une v0.8.1 soit sortie.
Selon Cargo.{toml,lock}neon-sys/neon viennent de la crate duniteroxyde qui se trouve dans le dossier neon/native. J’ai tenté des les mettre à jour et d’installer gyp mais rien n’y fait, je n’y arrive pas encore.
Logs de compilation
cargo xtask build
Finished dev [unoptimized + debuginfo] target(s) in 0.56s
Running `target/debug/xtask build`
rustc 1.51.0 (Fedora 1.51.0-3.fc33)
cargo 1.51.0
Check node version …
Node v10.24.0 already installed ✔
npm WARN deprecated express-fileupload@0.0.5: Please upgrade express-fileupload to version 1.1.8+ due to a security vulnerability with the parseNested option
npm WARN deprecated node-pre-gyp@0.6.34: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated request-promise@4.2.0: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@4.2.1: this library is no longer supported
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN duniter-ui@1.7.14 requires a peer of duniter@1.7.x but none is installed. You must install peer dependencies yourself.
+ duniter-ui@1.7.14
updated 1 package and audited 987 packages in 8.41s
17 packages are looking for funding
run `npm fund` for details
found 108 vulnerabilities (39 low, 16 moderate, 48 high, 5 critical)
run `npm audit fix` to fix them, or `npm audit` for details
npm WARN prepare removing existing node_modules/ before installation
> sqlite3@4.1.1 install /home/gtest/duniter/node_modules/sqlite3
> node-pre-gyp install --fallback-to-build
node-pre-gyp WARN Using request for node-pre-gyp https download
[sqlite3] Success: "/home/gtest/duniter/node_modules/sqlite3/lib/binding/node-v64-linux-x64/node_sqlite3.node" is installed via remote
> leveldown@5.6.0 install /home/gtest/duniter/node_modules/leveldown
> node-gyp-build
> duniter@1.8.1 install /home/gtest/duniter
> ./neon/build.sh
neon info forcing rebuild for new build settings
neon info running cargo
Compiling neon-sys v0.4.0
Compiling headers v0.3.4
Compiling smallvec v1.6.1
Compiling serde_json v1.0.64
The following warnings were emitted during compilation:
warning: ar: /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build/Release/obj.target/neon/src/neon.o: Aucun fichier ou dossier de ce type
error: failed to run custom build command for `neon-sys v0.4.0`
Caused by:
process didn't exit successfully: `/home/gtest/duniter/target/release/build/neon-sys-8f2e21598f2f7093/build-script-build` (exit code: 1)
--- stdout
Skipping node-gyp installation as part of npm install.
audited 96 packages in 2.087s
found 7 vulnerabilities (3 low, 1 moderate, 3 high)
run `npm audit fix` to fix them, or `npm audit` for details
> @ build-release /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native
> node-gyp build
make : on entre dans le répertoire « /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build »
CXX(target) Release/obj.target/neon/src/neon.o
make : on quitte le répertoire « /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build »
TARGET = Some("x86_64-unknown-linux-gnu")
HOST = Some("x86_64-unknown-linux-gnu")
AR_x86_64-unknown-linux-gnu = None
AR_x86_64_unknown_linux_gnu = None
HOST_AR = None
AR = None
running: "ar" "cq" "/home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/libneon.a" "/home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build/Release/obj.target/neon/src/neon.o"
cargo:warning=ar: /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build/Release/obj.target/neon/src/neon.o: Aucun fichier ou dossier de ce type
exit code: 1
--- stderr
make: g++: Aucun fichier ou dossier de ce type
make: *** [neon.target.mk:103 : Release/obj.target/neon/src/neon.o] Erreur 127
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:191:23)
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 Linux 5.10.17-libre.200.fc33.gnu.x86_64
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build"
gyp ERR! cwd /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native
gyp ERR! node -v v10.24.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ build-release: `node-gyp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ build-release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/gtest/.npm/_cacache/_logs/2021-05-13T19_19_15_335Z-debug.log
error occurred: Command "ar" "cq" "/home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/libneon.a" "/home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build/Release/obj.target/neon/src/neon.o" with args "ar" did not execute successfully (status code exit code: 1).
warning: build failed, waiting for other jobs to finish...
The following warnings were emitted during compilation:
warning: ar: /home/gtest/duniter/target/release/build/neon-sys-58bfee087a698940/out/native/build/Release/obj.target/neon/src/neon.o: Aucun fichier ou dossier de ce type
error: build failed
neon ERR! cargo build failed
Error: cargo build failed
at Target.<anonymous> (/home/gtest/duniter/node_modules/neon-cli/lib/target.js:121:35)
at step (/home/gtest/duniter/node_modules/neon-cli/lib/target.js:32:23)
at Object.next (/home/gtest/duniter/node_modules/neon-cli/lib/target.js:13:53)
at fulfilled (/home/gtest/duniter/node_modules/neon-cli/lib/target.js:4:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! duniter@1.8.1 install: `./neon/build.sh`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the duniter@1.8.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/gtest/.npm/_logs/2021-05-13T19_19_16_905Z-debug.log
Je ne peux pas mettre à jour neon (et toutes ses sous-crates dont neon-sys), car j’utilise massivement neon-serde pour générer une grosse partie de mon code de binding et que neon-serde dépend encore de neon 0.4.x.
Finished dev [unoptimized + debuginfo] target(s) in 0.29s
Running `target/debug/xtask build`
rustc 1.51.0 (Fedora 1.51.0-3.fc33)
cargo 1.51.0
Check node version …
Node v10.24.0 already installed ✔
npm WARN deprecated express-fileupload@0.0.5: Please upgrade express-fileupload to version 1.1.8+ due to a security vulnerability with the parseNested option
npm WARN deprecated node-pre-gyp@0.6.34: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request-promise@4.2.0: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated har-validator@4.2.1: this library is no longer supported
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN duniter-ui@1.7.14 requires a peer of duniter@1.7.x but none is installed. You must install peer dependencies yourself.
+ duniter-ui@1.7.14
updated 1 package and audited 987 packages in 11.038s
17 packages are looking for funding
run `npm fund` for details
found 108 vulnerabilities (39 low, 16 moderate, 48 high, 5 critical)
run `npm audit fix` to fix them, or `npm audit` for details
npm WARN prepare removing existing node_modules/ before installation
> sqlite3@4.1.1 install /home/gtest/duniter/node_modules/sqlite3
> node-pre-gyp install --fallback-to-build
node-pre-gyp WARN Using request for node-pre-gyp https download
[sqlite3] Success: "/home/gtest/duniter/node_modules/sqlite3/lib/binding/node-v64-linux-x64/node_sqlite3.node" is installed via remote
> leveldown@5.6.0 install /home/gtest/duniter/node_modules/leveldown
> node-gyp-build
> duniter@1.8.1 install /home/gtest/duniter
> ./neon/build.sh
neon info forcing rebuild for new build settings
neon info running cargo
Compiling neon-sys v0.4.0
Compiling headers v0.3.4
Compiling smallvec v1.6.1
Compiling serde_json v1.0.64
The following warnings were emitted during compilation:
warning: ar: /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build/Release/obj.target/neon/src/neon.o: Aucun fichier ou dossier de ce type
error: failed to run custom build command for `neon-sys v0.4.0`
Caused by:
process didn't exit successfully: `/home/gtest/duniter/target/release/build/neon-sys-8f2e21598f2f7093/build-script-build` (exit code: 1)
--- stdout
Skipping node-gyp installation as part of npm install.
audited 96 packages in 1.64s
found 7 vulnerabilities (3 low, 1 moderate, 3 high)
run `npm audit fix` to fix them, or `npm audit` for details
> @ build-release /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native
> node-gyp build
make : on entre dans le répertoire « /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build »
CXX(target) Release/obj.target/neon/src/neon.o
make : on quitte le répertoire « /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build »
TARGET = Some("x86_64-unknown-linux-gnu")
HOST = Some("x86_64-unknown-linux-gnu")
AR_x86_64-unknown-linux-gnu = None
AR_x86_64_unknown_linux_gnu = None
HOST_AR = None
AR = None
running: "ar" "cq" "/home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/libneon.a" "/home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build/Release/obj.target/neon/src/neon.o"
cargo:warning=ar: /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build/Release/obj.target/neon/src/neon.o: Aucun fichier ou dossier de ce type
exit code: 1
--- stderr
make: g++: Aucun fichier ou dossier de ce type
make: *** [neon.target.mk:103 : Release/obj.target/neon/src/neon.o] Erreur 127
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:191:23)
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 Linux 5.10.17-libre.200.fc33.gnu.x86_64
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build"
gyp ERR! cwd /home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native
gyp ERR! node -v v10.24.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ build-release: `node-gyp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ build-release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/gtest/.npm/_cacache/_logs/2021-05-14T11_58_32_504Z-debug.log
error occurred: Command "ar" "cq" "/home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/libneon.a" "/home/gtest/duniter/target/release/build/neon-sys-0bba5929ea84a1ef/out/native/build/Release/obj.target/neon/src/neon.o" with args "ar" did not execute successfully (status code exit code: 1).
warning: build failed, waiting for other jobs to finish...
The following warnings were emitted during compilation:
warning: ar: /home/gtest/duniter/target/release/build/neon-sys-58bfee087a698940/out/native/build/Release/obj.target/neon/src/neon.o: Aucun fichier ou dossier de ce type
error: build failed
neon ERR! cargo build failed
Error: cargo build failed
at Target.<anonymous> (/home/gtest/duniter/node_modules/neon-cli/lib/target.js:121:35)
at step (/home/gtest/duniter/node_modules/neon-cli/lib/target.js:32:23)
at Object.next (/home/gtest/duniter/node_modules/neon-cli/lib/target.js:13:53)
at fulfilled (/home/gtest/duniter/node_modules/neon-cli/lib/target.js:4:58)
at process._tickCallback (internal/process/next_tick.js:68:7)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! duniter@1.8.1 install: `./neon/build.sh`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the duniter@1.8.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/gtest/.npm/_logs/2021-05-14T11_58_34_858Z-debug.log
Oui, si je n’y arrive pas je vais considérer utiliser l’image docker.
On dirait que j’ai trouvé la source en développant dans la partie Rust de Duniter :
Logs
cargo clippy --all --tests -- -D warnings --verbose
[…]
Checking url v2.2.1
error: failed to run custom build command for `leveldb-sys v2.0.8`
Caused by:
process didn't exit successfully: `/home/gtest/duniter/target/debug/build/leveldb-sys-298bf8982a9226b1/build-script-build` (exit code: 101)
--- stdout
[build] Started
[snappy] Building
running: "cmake" "/home/gtest/.cargo/registry/src/github.com-1ecc6299db9ec823/leveldb-sys-2.0.8/deps/snappy-1.1.7" "-DBUILD_SHARED_LIBS=OFF" "-DSNAPPY_BUILD_TESTS=OFF" "-DHAVE_LIBZ=OFF" "-DCMAKE_INSTALL_LIBDIR=/home/gtest/duniter/target/debug/build/leveldb-sys-e4705094a588dee0/out/lib" "-DCMAKE_INSTALL_PREFIX=/home/gtest/duniter/target/debug/build/leveldb-sys-e4705094a588dee0/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=c++" "-DCMAKE_ASM_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_ASM_COMPILER=/usr/bin/cc" "-DCMAKE_BUILD_TYPE=Debug"
-- The C compiler identification is GNU 10.3.1
-- The CXX compiler identification is unknown
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Configuring incomplete, errors occurred!
See also "/home/gtest/duniter/target/debug/build/leveldb-sys-e4705094a588dee0/out/build/CMakeFiles/CMakeOutput.log".
See also "/home/gtest/duniter/target/debug/build/leveldb-sys-e4705094a588dee0/out/build/CMakeFiles/CMakeError.log".
--- stderr
CMake Error at CMakeLists.txt:2 (project):
The CMAKE_CXX_COMPILER:
c++
is not a full path and was not found in the PATH.
Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.
thread 'main' panicked at '
command did not execute successfully, got: exit code: 1
build script failed, must exit now', /home/gtest/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.45/src/lib.rs:894:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed
g++ était nécessaire pour leveldb-sys et surement pour neon-sys comme indiqué dans les pré-requis :
Oui évidemment, je croyais que tu l’avais déjà, et c’est indiqué dans la doc de néon, c’est également indiqué dans la doc de compilation manuelle de Duniter, les « Build essential tools » comprenant un compilateur C++, mais apparemment ce n’est pas évident pour tout le monde
Tu veux bien faire une MR sur la doc pour rendre ça plus explicite ?
Je tente une compilation de la branche dev sous Fedora 38. J’ai une erreur Python2 :
logs
error: failed to run custom build command for `neon-sys v0.4.0`
Caused by:
process didn't exit successfully: `/home/moul/projects/ML/duniter/target/release/build/neon-sys-f809b557f4c0e76e/build-script-build` (exit status: 101)
--- stdout
Skipping node-gyp installation as part of npm install.
--- stderr
thread 'main' panicked at 'Failed to run "node-gyp configure" for neon-sys!
Out:
> configure-release
> node-gyp configure --verbose
Err: gyp info it worked if it ends with ok
gyp verb cli [
gyp verb cli '/usr/bin/node',
gyp verb cli '/home/moul/projects/ML/duniter/target/release/build/neon-sys-010b8545827c7d69/out/native/node_modules/.bin/node-gyp',
gyp verb cli 'configure',
gyp verb cli '--verbose'
gyp verb cli ]
gyp info using node-gyp@3.6.2
gyp info using node@16.18.1 | linux | x64
gyp verb command configure []
gyp verb check python checking for Python executable "/usr/bin/python3" in the PATH
gyp verb `which` succeeded /usr/bin/python3 /usr/bin/python3
gyp verb check python version `/usr/bin/python3 -c "import platform; print(platform.python_version());"` returned: "3.11.3\n"
gyp ERR! configure error
gyp ERR! stack Error: Python executable "/usr/bin/python3" is v3.11.3, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack at PythonFinder.failPythonVersion (/home/moul/projects/ML/duniter/target/release/build/neon-sys-010b8545827c7d69/out/native/node_modules/node-gyp/lib/configure.js:492:19)
gyp ERR! stack at PythonFinder.<anonymous> (/home/moul/projects/ML/duniter/target/release/build/neon-sys-010b8545827c7d69/out/native/node_modules/node-gyp/lib/configure.js:474:14)
gyp ERR! stack at ChildProcess.exithandler (node:child_process:394:7)
gyp ERR! stack at ChildProcess.emit (node:events:513:28)
gyp ERR! stack at maybeClose (node:internal/child_process:1100:16)
gyp ERR! stack at Socket.<anonymous> (node:internal/child_process:458:11)
gyp ERR! stack at Socket.emit (node:events:513:28)
gyp ERR! stack at Pipe.<anonymous> (node:net:301:12)
gyp ERR! System Linux 6.2.13-300.fc38.x86_64
gyp ERR! command "/usr/bin/node" "/home/moul/projects/ML/duniter/target/release/build/neon-sys-010b8545827c7d69/out/native/node_modules/.bin/node-gyp" "configure" "--verbose"
gyp ERR! cwd /home/moul/projects/ML/duniter/target/release/build/neon-sys-010b8545827c7d69/out/native
gyp ERR! node -v v16.18.1
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
', /home/moul/.cargo/registry/src/github.com-1ecc6299db9ec823/neon-sys-0.4.0/build.rs:159:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for `neon-sys v0.4.0`
Caused by:
process didn't exit successfully: `/home/moul/projects/ML/duniter/target/release/build/neon-sys-f809b557f4c0e76e/build-script-build` (exit status: 101)
--- stdout
Skipping node-gyp installation as part of npm install.
--- stderr
thread 'main' panicked at 'Failed to run "node-gyp configure" for neon-sys!
Out:
> configure-release
> node-gyp configure --verbose
Err: gyp info it worked if it ends with ok
gyp verb cli [
gyp verb cli '/usr/bin/node',
gyp verb cli '/home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native/node_modules/.bin/node-gyp',
gyp verb cli 'configure',
gyp verb cli '--verbose'
gyp verb cli ]
gyp info using node-gyp@3.6.2
gyp info using node@16.18.1 | linux | x64
gyp verb command configure []
gyp verb check python checking for Python executable "/usr/bin/python3" in the PATH
gyp verb `which` succeeded /usr/bin/python3 /usr/bin/python3
gyp verb check python version `/usr/bin/python3 -c "import platform; print(platform.python_version());"` returned: "3.11.3\n"
gyp ERR! configure error
gyp ERR! stack Error: Python executable "/usr/bin/python3" is v3.11.3, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack at PythonFinder.failPythonVersion (/home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native/node_modules/node-gyp/lib/configure.js:492:19)
gyp ERR! stack at PythonFinder.<anonymous> (/home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native/node_modules/node-gyp/lib/configure.js:474:14)
gyp ERR! stack at ChildProcess.exithandler (node:child_process:394:7)
gyp ERR! stack at ChildProcess.emit (node:events:513:28)
gyp ERR! stack at maybeClose (node:internal/child_process:1100:16)
gyp ERR! stack at Socket.<anonymous> (node:internal/child_process:458:11)
gyp ERR! stack at Socket.emit (node:events:513:28)
gyp ERR! stack at Pipe.<anonymous> (node:net:301:12)
gyp ERR! System Linux 6.2.13-300.fc38.x86_64
gyp ERR! command "/usr/bin/node" "/home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native/node_modules/.bin/node-gyp" "configure" "--verbose"
gyp ERR! cwd /home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native
gyp ERR! node -v v16.18.1
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
', /home/moul/.cargo/registry/src/github.com-1ecc6299db9ec823/neon-sys-0.4.0/build.rs:159:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
neon ERR! cargo build failed
Error: cargo build failed
at Target.<anonymous> (/home/moul/projects/ML/duniter/node_modules/neon-cli/lib/target.js:121:35)
at step (/home/moul/projects/ML/duniter/node_modules/neon-cli/lib/target.js:32:23)
at Object.next (/home/moul/projects/ML/duniter/node_modules/neon-cli/lib/target.js:13:53)
at fulfilled (/home/moul/projects/ML/duniter/node_modules/neon-cli/lib/target.js:4:58)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm ERR! code 1
npm ERR! path /home/moul/projects/ML/duniter
npm ERR! command failed
npm ERR! command sh -c -- ./neon/build.sh
npm ERR! A complete log of this run can be found in:
npm ERR! /home/moul/.npm/_logs/2023-05-26T15_56_48_316Z-debug-0.log
J’ai python2 gcc-c++ installés. Duniter v1.9 dépend de Python 2
Je passe python2 en option (pas nécessaire sur release/1.8), mais ça échoue encore :
logs
/usr/bin/node /home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native/node_modules/.bin/node-gyp configure --python python2
gyp info it worked if it ends with ok
gyp info using node-gyp@3.6.2
gyp info using node@16.18.1 | linux | x64
(node:2939479) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
(Use `node --trace-deprecation ...` to show where the warning was created)
gyp info spawn /usr/bin/python2
gyp info spawn args [
gyp info spawn args '/home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'make',
gyp info spawn args '-I',
gyp info spawn args '/home/moul/projects/ML/duniter/build/config.gypi',
gyp info spawn args '-I',
gyp info spawn args '/home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native/node_modules/node-gyp/addon.gypi',
gyp info spawn args '-I',
gyp info spawn args '/home/moul/.node-gyp/16.18.1/include/node/common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args '-Dnode_root_dir=/home/moul/.node-gyp/16.18.1',
gyp info spawn args '-Dnode_gyp_dir=/home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native/node_modules/node-gyp',
gyp info spawn args '-Dnode_lib_file=/home/moul/.node-gyp/16.18.1/<(target_arch)/node.lib',
gyp info spawn args '-Dmodule_root_dir=/home/moul/projects/ML/duniter',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.'
gyp info spawn args ]
gyp: binding.gyp not found (cwd: /home/moul/projects/ML/duniter) while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native/node_modules/node-gyp/lib/configure.js:336:16)
gyp ERR! stack at ChildProcess.emit (node:events:513:28)
gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)
gyp ERR! System Linux 6.2.13-300.fc38.x86_64
gyp ERR! command "/usr/bin/node" "/home/moul/projects/ML/duniter/target/release/build/neon-sys-19e910c4954b4598/out/native/node_modules/.bin/node-gyp" "configure" "--python" "python2"
gyp ERR! cwd /home/moul/projects/ML/duniter
gyp ERR! node -v v16.18.1
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
