Arch Linux User Repository

@3xploiton3 Your issue is caused by pnpm being out of date in the Arch repos. I was personally able to resolve that by installing yarn-pnpm-corepack (make sure to follow the post-installation instructions) which fullfills pnpm & yarn and instead lets corepack manage them.

I'm now instead getting stuck during build as prisma-cli doesn't seem to link using mold:

error: linking with `clang` failed: exit status: 1
  |
  = note: LC_ALL="C" (...) "-fuse-ld=mold"
  = note: mold: fatal: failed to load plugin : /usr/bin/ld.mold: undefined symbol: onload
          clang: error: linker command failed with exit code 1 (use -v to see invocation)


error: could not compile `prisma-cli` (bin "prisma") due to 1 previous error
 ELIFECYCLE  Command failed with exit code 101.
 ELIFECYCLE  Command failed with exit code 101.
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'spacedrive-git-r2297.8ad468b-5':
error: packages failed to build: spacedrive-git-r2297.8ad468b-5

Disabling the mold linker in the RUSTFLAGS variable in my /etc/makepkg.conf now makes it build all the way to sd-cloud-api, where it once again fails with another linking error:

   Compiling sd-cloud-api v0.1.0 (/home/dovah/.cache/paru/clone/spacedrive-git/src/spacedrive/crates/cloud-api)
warning: use of deprecated associated function `sd_core_indexer_rules::IndexerRule::apply_all`: Use `[IndexerRuler::apply_all]` instead
   --> core/src/location/indexer/old_walk.rs:499:41
    |
499 |         let Ok(rules_per_kind) = IndexerRule::apply_all(indexer_rules, &current_path)
    |                                               ^^^^^^^^^
    |
    = note: `#[warn(deprecated)]` on by default

warning: use of deprecated associated function `sd_core_indexer_rules::IndexerRule::apply_all`: Use `[IndexerRuler::apply_all]` instead
   --> core/src/location/non_indexed.rs:147:23
    |
147 |             match IndexerRule::apply_all(&rules, &entry_path).await {
    |                                ^^^^^^^^^

error: linking with `clang` failed: exit status: 1
  |
[ -------- 582 lines truncated -------- ]
          /usr/bin/ld: /home/dovah/.cache/paru/clone/spacedrive-git/src/spacedrive/target/debug/deps/sd_core-80873b906ed47337: hidden symbol `OPENSSL_cpuid_setup' isn't defined
          /usr/bin/ld: final link failed: bad value
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

  = note: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
  = note: use the `-l` flag to specify native libraries to link
  = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#rustc-link-lib)

warning: `sd-core` (lib test) generated 2 warnings
error: could not compile `sd-core` (lib test) due to 1 previous error; 2 warnings emitted
 ELIFECYCLE  Command failed with exit code 101.
 ELIFECYCLE  Command failed with exit code 101.
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'spacedrive-git-r2297.8ad468b-5':
error: packages failed to build: spacedrive-git-r2297.8ad468b-5

@3xploiton3 Thank you for your report. I have not enough time to update this package now, so I will fix the problem within the next month.

 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/home/user/.cache/yay/spacedrive-git/src/spacedrive".

Expected version: >=9.0.0
Got: 8.15.2

This is happening because the package's manifest has an engines.pnpm field specified.
To fix this issue, install the required pnpm version globally.

To install the latest version of pnpm, run "pnpm i -g pnpm".
To check your pnpm version, run "pnpm -v".
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: spacedrive-git-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
spacedrive-git - exit status 4

@yochananmarqos

You were right about switching to the nightly toolchain, however you're missing the export. Adding cargo-nightly to makedepends() isn't enough because all that does is use rustup instead of rust.

spacedrive has rust-toolchain.toml, and it specifies stable toolchain. Therefore, I assume that don't have to set RUSTUP_TOOLCHAIN implicitly.

@cheatsc: You were right about switching to the nightly toolchain, however you're missing the export. Adding cargo-nightly to makedepends() isn't enough because all that does is use rustup instead of rust.

export RUSTUP_TOOLCHAIN=nightly

See my WIP PKGBUILD

I still have no idea how you're using this as it still segfaults:

2023-12-02T19:27:03.599821Z  INFO sd_core: core/src/lib.rs:88: Starting core with data directory '/home/yochanan/.local/share/spacedrive'
2023-12-02T19:27:03.600427Z  INFO sd_core::util::version_manager: core/src/util/version_manager.rs:200: Running sd_core::node::config::NodeConfig migrator: V1 -> V2
2023-12-02T19:27:03.601724Z  INFO sd_core::p2p::p2p_manager: core/src/p2p/p2p_manager.rs:50: Node RemoteIdentity('qGOmcf5mkBW3jx7ZiUnGzN11Kwhn7xp95nto+uwlrYs') libp2p::PeerId('12D3KooWM9gnxRtBbDLcgVPF58yuDNQxEf12QN3ACKFCf6EPHLGz') is now online listening at addresses: {}
2023-12-02T19:27:03.610375Z  INFO sd_core: core/src/lib.rs:145: Spacedrive online.
2023-12-02T19:27:03.610532Z  INFO sd_desktop::tauri_plugins: apps/desktop/src-tauri/src/tauri_plugins.rs:62: Internal server listening on: http://127.0.0.1:35217
zsh: segmentation fault (core dumped)  spacedrive

@yochananmarqos

By the way, pnpm prep should be in the build() function as it performs compilation.

OK. I've move pnpm prep to build().

@cheatsc: You're right, protobuf is no longer required.

By the way, pnpm prep should be in the build() function as it performs compilation.

@yochananmarqos

This also requires clang and protobuf to build.

I could not confirm that protobuf is required to build, so I did not add it to build dependencies.

@FabioLolix

please add options=(!lto) to build with devtools

Sorry, I cannot make a sense. Could you explain the reason in detail?

@FabioLolix @yochananmarqos Thank you guys for your comment, and sorry for the delay in my reply. I will update the dependencies of this package within 3 weeks. I apologize for your inconvenience.

This also requires clang and protobuf to build. Here's my improved WIP PKGBUILD. However, it won't actually run yet. See #1678.