Arch Linux User Repository

@Mufflone: What is the format of that file, aka what does file say?

@DarkShadow44

I don't use this package but the build errors reported in the orphan request are still present. here's an extract from the build process:

   Compiling junction v1.2.0
error: linking with `cc` failed: exit status: 1
  |
  = note: LC_ALL="C" PATH="/usr/lib64/rustlib/x86_64-unknown-linux-gnu/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl" VSLANG="1033" "cc" "-m64" "/tmp/rustcFsJKLV/symbols.o" "<17 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/build/anki-git/src/anki/out/rust/release/deps/{libwhich-65f5ae34c6a87ea0.rlib,libhome-6ac2e8148a81f5f2.rlib,libzip-f47a094a2d1576db.rlib,libtime-d8aff71642f49234.rlib,libtime_core-0135dec28a096929.rlib,[...]
  = note: some arguments are omitted. use `--verbose` to show all linker arguments
  = note: /usr/bin/ld: /build/anki-git/src/anki/out/rust/release/deps/libzstd_sys-d724a5c76d50ba00.rlib: error adding symbols: file format not recognized
          collect2: error: ld returned 1 exit status


error: could not compile `runner` (bin "runner") due to 1 previous error
==> ERROR: A failure occurred in build().
    Aborting...

For those getting linker errors during the Rust build, like error adding symbols: file format not recognized: Try adding this to the build() section of the PKGBUILD, underneath the other compiler env var exports:

export RUSTFLAGS="-Clink-args=-fuse-ld=lld -Ctarget-cpu=native"

I have the same issue (as of 2024-05-24, up-to-date system). I found a thread here, and downgrading Linux to 6.8.9 helped.

Having trouble building this again lately. I don't think it is a python issue this time. I've tried clearing out the yarn and bazel caches with no luck. Asking here before opening a git issue in case the solution is bleedingly obvious.

FAILED: /tmp/makepkg/anki-git/src/anki/out/node_modules/.marker ... very long so redacted
yarn install v1.22.22
[1/4] Resolving packages...
[2/4] Fetching packages...
warning Pattern ["string-width@^4.1.0"] is trying to unpack in the same destination "/home/hearth/.cache/yarn/v6/npm-string-width-cjs-4.2.3-269c7117d27b05ad2e536830a8ec895ef9c6d010-integrity/node_modules/string-width-cjs" as pattern ["string-width-cjs@npm:string-width@^4.2.0"]. This could result in non-deterministic behavior, skipping.
warning svelte-preprocess@5.1.3: The engine "pnpm" appears to be invalid.
[3/4] Linking dependencies...
warning " > esbuild-sass-plugin@2.16.1" has incorrect peer dependency "esbuild@^0.19.4".
[4/4] Building fresh packages...
error /tmp/makepkg/anki-git/src/anki/node_modules/vite/node_modules/esbuild: Command failed.
Exit code: 126
Command: node install.js
Arguments: 
Directory: /tmp/makepkg/anki-git/src/anki/node_modules/vite/node_modules/esbuild
Output:
/bin/sh: /tmp/yarn--1716547874268-0.043145118609238864/node: /bin/sh: bad interpreter: Text file busy
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Failed with code Some(126): /tmp/makepkg/anki-git/src/anki/out/extracted/node/bin/yarn install

ninja: build stopped: subcommand failed.

Build failed.
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'anki-git-r10935.eb597475c-1': 
error: packages failed to build: anki-git-r10935.eb597475c-1

Seems the hard requirement of pip_system_certs was removed in Anki PR #3114, with the reasoning:

"This dependency usually doesn't benefit Linux distros with requests library configured to use system certificate already."

I didn't test yet building the latest commit without pip_system_certs, just saw the git log message. If the requests library is actually configured as described in the PR, then maybe the dependency can be removed.

Thanks, that's a dependency of python-pip-system-certs - I added that.

Maybe python-wrapt is also a dependency. After installation, anki failed to start with the error pip_system_certs: ERROR: could not register module: No module named 'wrapt'. Fixed after installing python-wrapt.

@hearth You have Python packages installed in ~/.local/lib/python3.11, which often breaks system packages. This is why normally it's not recommended to use pip to install local system packages except in virtual environments. For system packages you should always use pacman or the AUR. Admittedly, until earlier today pip_system_certs was not available in the AUR, so personally I had used pip install --break-system-packages ..., but I knew the risk and what to do if conflicts happen.

Now, python-pip-system-certs is in the AUR thanks to @hearth. You could install it from there but the latest version of anki-git requires it automatically, so there is nothing more you should do, except the following: My recommendation would be to uninstall all locally installed Python packages, either via

pip freeze | xargs pip uninstall -y

or just by nuking the local python directories:

# you can also use rm -rf, here I use mv so that you can revert the "deletion" 
mv ~/.local/lib/python3.11 ~/.local/lib/python3.11_to_delete

And then just install the latest version of anki-git from the AUR.

@elimik31 Thanks, pushed an update.

@hearth Sorry, I can't reproduce this. Is your system full up to date, and did you do a clean build of anki? If so, how exactly do you reproduce this issue?