If you have problems installing Nova on a previous Phantom system, see installation section, sticky, to upgrade your compilers to work for Nova.

Problems with the install.sh file

Started by tuvok, 02 Jan 2026, 21:47

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

tuvok

Hello,
i have the follow System

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.3 LTS"

---------------------------

i have change the follow on the script

NOVA_INSTALL_DIR_DEFAULT="/home/websdr/novaSDR"
NOVA_BIN_DIR_DEFAULT="/home/websdr/novaSDR"
NOVA_SRC_DIR_DEFAULT="/home/websdr/novasdr-src"

----------------------------

and than i have start the script
and get errors

Quote[OK] Install Vulkan + glslang + SPIRV-Tools (apt)
LIBCLANG_PATH set to: /usr/lib/llvm-18/lib
+ cargo build -p novasdr-server --release --features soapysdr,clfft,vkfft
error: failed to parse lock file at: /home/websdr/novasdr-src/Cargo.lock

Caused by:
  lock file version 4 requires `-Znext-lockfile-bump`

when i go to novasdr-src folder and i do this

cargo build -p novasdr-server --release -Znext-lockfile-bump --features soapysdr,clfft,vkfft

i get a other error

Quotewebsdr@wmk:~/novasdr-src$ cargo build -p novasdr-server --release -Znext-lockfile-bump --features soapysdr,clfft,vkfft
    Updating crates.io index
  Downloaded adler2 v2.0.1
  Downloaded anstyle-query v1.1.5
  Downloaded anstream v0.6.21
  Downloaded heck v0.5.0
  Downloaded hash32 v0.3.1
  Downloaded anstyle v1.0.13
  Downloaded generic-array v0.14.7
  Downloaded anstyle-parse v0.2.7
  Downloaded arrayvec v0.7.6
  Downloaded anyhow v1.0.100
  Downloaded crypto-common v0.1.7
  Downloaded sync_wrapper v1.0.2
  Downloaded clap_lex v0.7.6
  Downloaded colorchoice v1.0.4
  Downloaded futures-task v0.3.31
  Downloaded http-body v1.0.1
  Downloaded futures-io v0.3.31
  Downloaded atomic-waker v1.1.2
  Downloaded futures-executor v0.3.31
  Downloaded dyn-clone v1.0.20
  Downloaded darling_macro v0.21.3
  Downloaded httpdate v1.0.3
  Downloaded fnv v1.0.7
  Downloaded dlopen2_derive v0.4.3
error: failed to download replaced source registry `crates-io`

Caused by:
  failed to parse manifest at `/home/websdr/.cargo/registry/src/index.crates.io-6f17d22bba15001f/dlopen2_derive-0.4.3/Cargo.toml`

Caused by:
  feature `edition2024` is required

  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.75.0).
  Consider trying a more recent nightly release.
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.




PS: i can not Upload pictures.. the Uploadfolder is full ..

Lebe Lange und in Frieden

magicint1337

Your Rust version is to old, please update it using curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

And then restart the system and retry.

tuvok

what have i do .. i have do the follow

as normal user
1. git clone https://github.com/Steven9101/NovaSDR

as sudo user
2. sudo apt-get install rustup

as normal user
3. rustup default nightly
4. cd novaSDR
5. cargo build --release --features soapysdr,clfft,vkfft

QuoteCompiling ws_probe v0.2.0 (/home/websdr/NovaSDR/crates/ws_probe)
  Compiling novasdr-server v0.2.0 (/home/websdr/NovaSDR/crates/novasdr-server)
    Finished `release` profile [optimized] target(s) in 7m 34s

than you show in the frontend/ folder when this is empty than do the follow
6. rm -rf frontend
7. git clone https://github.com/Steven9101/frontend frontend
8. cd frontend
9. npm ci
10. npm run build

Quotenpm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE  package: '@vitejs/plugin-react@5.1.2',
npm WARN EBADENGINE  required: { node: '^20.19.0 || >=22.12.0' },
npm WARN EBADENGINE  current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE  package: 'vite@7.3.0',
npm WARN EBADENGINE  required: { node: '^20.19.0 || >=22.12.0' },
npm WARN EBADENGINE  current: { node: 'v18.19.1', npm: '9.2.0' }
npm WARN EBADENGINE }

11. you can cancel the building this will run in a error

as sudo user
12. sudo curl -fsSL https://deb.nodesource.com/setup_22.x | sudo bash -
13. sudo apt-get install -y nodejs

as normal user
14. run Part 9 and 10 again

Quotewebsdr@wmk:~/NovaSDR/frontend$ npm ci

added 315 packages, and audited 316 packages in 6s

69 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
websdr@wmk:~/NovaSDR/frontend$ npm run build

> frontend@0.0.0 build
> tsc -b && vite build

vite v7.3.0 building client environment for production...
✓ 2225 modules transformed.
dist/index.html                                0.73 kB │ gzip:  0.36 kB
dist/assets/ft8Worker-2h9zGY-k.js              7.19 kB
dist/assets/decode_ft8-BmAsUujb.wasm          42.52 kB │ gzip:  21.75 kB
dist/assets/phantomsdrdsp_bg-Bh04HLJe.wasm    333.48 kB │ gzip: 146.25 kB
dist/assets/index-DUR3lfxM.css                32.95 kB │ gzip:  6.79 kB
dist/assets/index-C-p1aCXj.js              1,089.03 kB │ gzip: 247.08 kB

(!) Some chunks are larger than 500 kB after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
✓ built in 11.64s

configure the sdr server
15. ./target/release/novasdr-server setup -c config/config.json -r config/receivers.json
start the sdr server
16. ./target/release/novasdr-server -c config/config.json -r config/receivers.json

i think this is a nightly and repo thing.. with a standard ubuntu we can not use it :)
Lebe Lange und in Frieden

Bas ON5HB

Few things, you probably had Phantom running before, so you needed to update npm and nvm engines to the latest.
Then the frontend will compile just fine.

The backend doesn't compile if you don't have a Vulkan GPU, as it's missing the Vulkan dependencies. You have selected NO on VKFFT.

I have reported this already to Steven. But he probably tested the beta on a NEW installation, not on excisting one.

tuvok

it run :) .. i have disabled it .. the main problem was the old node and rust .. but this is standard on a LTS Ubuntu version .. i have add the repo for node and add rust as a newer night build on the user account ..

It would be nice if it were developed on stable, then people might not have so many problems... Above all, you need to know a little bit about it to be able to do that.
Lebe Lange und in Frieden


Powered by EzPortal