Arch Linux User Repository

@EUA The package obviously fails to build at the current time since it was not yet updated to reflect the changes in version 3, as it requires an unsupported rocm.

I got such an error on test phase.

==> Starting check()...                                                        
warning: The package `zluda_dump` provides no linkable target. The compiler might raise an error while compiling `inject`. Consider adding 'dylib' or 'rlib' to key `crate-type` in `zluda_dump`'s Cargo.toml. This warning might turn into a hard error in the future.
   Compiling zluda_inject v0.0.0 (/tmp/yaourt-tmp-death/aur-zluda-git/src/ZLUDA/zluda_inject)
   Compiling zluda_lib v0.0.0 (/tmp/yaourt-tmp-death/aur-zluda-git/src/ZLUDA/zluda_lib)
error: environment variable `CARGO_BIN_EXE_zluda_with` not defined at compile time
  --> zluda_inject/tests/inject.rs:53:40
   |                                                                           
53 |     let zluda_with_exe = PathBuf::from(env!("CARGO_BIN_EXE_zluda_with"));
   |                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |                                                                           
   = help: Cargo sets build script variables at run time. Use `std::env::var("CARGO_BIN_EXE_zluda_with")` instead
   = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: environment variable `HELPERS_OUT_DIR` not defined at compile time
  --> zluda_inject/tests/inject.rs:56:23
   |                                                                           
56 |     let helpers_dir = env!("HELPERS_OUT_DIR");
   |                       ^^^^^^^^^^^^^^^^^^^^^^^
   |                                                                           
   = help: use `std::env::var("HELPERS_OUT_DIR")` to read the variable at run time
   = note: this error originates in the macro `env` (in Nightly builds, run with -Z macro-backtrace for more info)

error: could not compile `zluda_inject` (test "inject") due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in check().
    Aborting...

@acidunit This package is not a drop-in replacement of the cuda toolkit. It also does not ship the same basic files as the cuda package, like cuda libraries and cuda headers. So, adding 'cuda' to 'provides' does not apply here.

@dbermond

They mean the cuda package.

@dreieck Sorry, but I could not understand what you mean. This package already provides the base package (zluda). What do you suggest to be added to the provides array?

When it is a drop-in replacement, I think something should be added to the provides array (i.e. that stuff that it really replaces in a drop-in fashion).