Error Compiling on Linux

[adsicks]

Compiled with the command:

cargo build --release --no-default-features

Line 159-166 in the file /crates/larq-cli/src/commands/primary/bench_cmd.rs

Did not compile on linux. I changed the line as a workaround to:

let backend: Box<dyn larql_compute::ComputeBackend> = if metal {

/* let b = larql_compute::metal::MetalBackend::new()
.ok_or("Metal backend unavailable — rebuild with --features metal on an M-series Mac")?;
Box::new(b) */
Box::new(larql_compute::CpuBackend)
} else {
Box::new(larql_compute::CpuBackend)
};

as a workaround since I am not using a Mac. I don't know enough about Rust to create a proper workaround for this structure.

Have successfully run:

./larql --version

I saw your YouTube video explaining this and I am really excited about getting this running. I had the same thought as you, isn't LLM just running on a database? Thank you for putting in the hard work to show us this is possible!

[CronoBandit]

I don't have a solution to suggest - only confirmin @adsicks has already pointed-out --> not able to compile this project on Linux due to a missing metal crate. I'm on a Debian Proxmox LXC, kernel 7.0.0. My rustc & cargo versions are 1.95.0 presently. All dependencies compiled fine, but bailed on larql_compute crate:

$ cargo build --release --no-default-features

...

error[E0433]: cannot find metal in larql_compute
--> crates/larql-cli/src/commands/primary/bench_cmd.rs:160:32
|
160 | let b = larql_compute::metal::MetalBackend::new()
| ^^^^^ could not find metal in larql_compute

Metal libs - seems very Mac-dependent. Open to any other ideas to get this working for the Linux community ... excluding features, crates etc.... ideas ??

Heart-break ... being a long-time DBA by profession, I was super-excited about giving this a go on my home-lab ... but I own no Apple products :(
I only hope this LARQL project evolves to be less hard-wired to Macs, or at least inspires other projects, because I'd like to see this concept of LLM nodes/edges DB concepts gain more momentum !

[virtadpt]

I'm seeing this as well (Arch Linux, rust 1.95.0-1). If I do a plain old cargo build --release I get a slew of "unresolved import metal" errors. I've been seeing this in the last couple of clones of the repository (most recently commit ae93375).

If I use the above cargo build --release --no-default-features build I get slightly different errors:

error[E0583]: file not found for module `build`
--> crates/larql-vindex/src/extract/mod.rs:3:1
  |
3 | pub mod build;
  | ^^^^^^^^^^^^^^
  |
  = help: to create the module `build`, create file "crates/larql-vindex/src/extract/build.rs" or "crates/larql-vindex/src/extract/build/mod.rs"

Also on commit ae93375.

[deem0n]

Probably fixed by #46 ?

I saw error about pub mod build on Mac and fixed it.

[virtadpt]

I cut my repo over to PR #46 and gave it a try.

cargo build --release - Failed, "error[E0432]: unresolved import metal"

cargo build --release --no-default-features - Also failed, "error[E0433]: cannot find metal in larql_compute"