Arch Linux User Repository

I think like the -bin packages we should maintain separate packages: one that's the latest version, and one that's the latest compatible with immich. (The immich-server AUR package already has version requirements that should prevent accidental upgrading.)

That sounds reasonable. I've pushed vectorchord 1.0.0 and vectorchord-immich 0.5.3.

I think like the -bin packages we should maintain separate packages: one that's the latest version, and one that's the latest compatible with immich. (The immich-server AUR package already has version requirements that should prevent accidental upgrading.)

1. The undefined symbols in the dynamic library have been fixed.
2. This package will not be upgraded for now, until immich supports version 1.0.0. See also https://github.com/immich-app/immich/pull/23845.

Is there any chance of this being fixed with the comments from @usamoi? It's been broken for quite some time and obviously breaks things like immich that depend on it

Hi, @AlexBocken, upstream here. Thank you for maintaining the package! I have three notes below that might be useful.

• pgvector is not a build dependency of vectorchord.
• Even if C code of vectorchord is built with gcc, clang is still a build dependency of vectorchord. See also https://docs.vectorchord.ai/vectorchord/getting-started/installation.html.
• If C code of vectorchord is built with gcc, please add CFLAGS+=' -ffat-lto-objects' or options=(!lto) to PKGBUILD. Otherwise, C code and Rust code may fail to link correctly. Since the build artifact of vectorchord is a shared library, the error will only appear at runtime. It's not needed if C code of vectorchord is built with clang. See also https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/issues/20.

It worked for me with both clang and gcc installed and export CC=gcc removed.

Why did you add the force update for rustup package users and do not litter in ~ stuff? This is a non-issue in a chroot-build, and building outside a chroot shouldn't be supported.

Fails to build with gcc, still expects clang:

  thread '<unnamed>' (4601) panicked at /build/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/bindgen-0.71.1/lib.rs:604:27:
  Unable to find libclang: "couldn't find any valid shared libraries matching: ['libclang.so', 'libclang-*.so', 'libclang.so.*', 'libclang-*.so.*'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"

Fails to build with clang only (clang makedep added, removed export CC=gcc as noted in PKGBUILD):

error: linking with `cc` failed: exit status: 1
  |
  = note:  "cc" "-Wl,--version-script=/tmp/rustcNoVNVe/list" "-Wl,--no-undefined-version" "-m64" "/tmp/rustcNoVNVe/symbols.o" "<2 object files omitted>" "-Wl,--as-needed" "-Wl,-Bstatic" "/build/vectorchord/src/VectorChord-0.5.3/target/x86_64-unknown-linux-gnu/release/deps/ ...
  = note: some arguments are omitted. use `--verbose` to show all linker arguments
  = note: /usr/bin/ld: /build/vectorchord/src/VectorChord-0.5.3/target/x86_64-unknown-linux-gnu/release/deps/libsimd-197e0de9544d7e2c.rlib: error adding symbols: file format not recognized
          collect2: error: ld returned 1 exit status


error: could not compile `vchord` (lib) due to 1 previous error
Error: "Cargo build failed: exit status: 101"
make: *** [Makefile:12: build] Error 1

It builds if one only adds the clang makedep, don't remove export CC=gcc.

Alas, I kept running into some runtime error I didn't have with the prebuild binaries:

FATAL:  could not load library "/usr/lib/postgresql/vchord.so": /usr/lib/postgresql/vchord.so: undefined symbol: sqlite3_column_text

Needs clang in makedepends