Package Details: ctranslate2 4.7.1-1

Git Clone URL: https://aur.archlinux.org/ctranslate2.git (read-only, click to copy)
Package Base: ctranslate2
Description: A C++ library for efficient inference with Transformer models.
Upstream URL: https://github.com/OpenNMT/CTranslate2
Licenses: MIT
Submitter: yochananmarqos
Maintainer: lubosz
Last Packager: lubosz
Votes: 4
Popularity: 0.004221
First Submitted: 2023-12-10 15:32 (UTC)
Last Updated: 2026-03-07 13:47 (UTC)

Latest Comments

1 2 3 Next › Last »

gefyrotos commented on 2025-10-02 04:08 (UTC)

In case this helps someone else with an RTX 3060 who wants to use CUDA 13.0, here's my modified PKGBUILD:

@@ -14,7 +14,7 @@
 makedepends=(
   'cmake'
   'cuda'
-#  'cudnn'
+  'cudnn'
   'gcc14'
   'git'
   'intel-oneapi-mkl'
@@ -96,8 +96,9 @@
     -DOPENBLAS_INCLUDE_DIR='/usr/include/openblas' \
     -DWITH_RUY='ON' \
     -DWITH_CUDA='ON' \
+    -DWITH_CUDNN='ON' \
     -DCUDA_DYNAMIC_LOADING='ON' \
-    -DCUDA_ARCH_LIST='Common' \
+    -DCUDA_NVCC_FLAGS="-gencode arch=compute_86,code=sm_86" \
     -DCMAKE_POLICY_VERSION_MINIMUM='3.5' \
     -DENABLE_CPU_DISPATCH='OFF' \
     -Wno-dev

The arch=compute_86 refers to the compute capability of the 3060, which is 8.6.

xuhcc commented on 2025-07-18 13:15 (UTC)

ctranslate2 package currently depends on gcc13 from AUR. Is it still necessary? I tried to build the package with gcc14, that seems to work too.

yochananmarqos commented on 2025-07-18 00:49 (UTC)

@techmanwalker: First of all, English please. In the future, please prefix output with LC_ALL=C.

Do you have some sort of local environment variable that overrides the default linker? Notice this package neither uses mold nor lld.

lito commented on 2025-07-18 00:42 (UTC) 

ld.mold: /usr/src/debug/mold/mold/src/mold.h:3556: mold::i64 mold::Symbol<E>::get_output_sym_idx(mold::Context<E>&) const [with E = mold::X86_64; mold::i64 = long int]: Assertion `i != -1' failed.
collect2: error fatal: se terminó ld con la señal 6 [Abortado], core dumped
compilación terminada.
make[2]: *** [CMakeFiles/ctranslate2.dir/build.make:2191: libctranslate2.so.4.6.0] Error 1
make[1]: *** [CMakeFiles/Makefile2:391: CMakeFiles/ctranslate2.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

yochananmarqos commented on 2025-04-14 22:48 (UTC)

@taba: Can't reproduce. Make sure you're not mixing local and system Python packages.

taba commented on 2025-04-14 21:37 (UTC)

==> Starting package_python-ctranslate2()... usage: python -m installer [-h] [--destdir path] [--prefix path] [--compile-bytecode level] [--no-compile-bytecode] wheel python -m installer: error: unrecognized arguments: dist/ctranslate2-4.6.0-cp313-cp313-linux_x86_64.whl

yochananmarqos commented on 2025-04-08 20:17 (UTC)

@sashank: I think you misunderstand. Upstream originally tagged 4.6.0 and I updated the package. Then they decided to delete the tag and tag again it as v4.6.0.

Either way, no need to fiddle around with git commands, makepkg handles all of that. ;)

sashank commented on 2025-04-08 20:13 (UTC) (edited on 2025-04-08 20:15 (UTC) by sashank)

Setting git+https://github.com/OpenNMT/CTranslate2.git#tag=617405f4b050e994e829d527da6caa0e0030afe7

Allows the install to go forward.

I got the tag from running git rev-parse "v4.6.0" as suggested here:

https://wiki.archlinux.org/title/Arch_package_guidelines#Package_sources

Edit, well it works (and my changes might not have fixed this. Thanks anyways). It's rolling forward.

yochananmarqos commented on 2025-04-08 19:54 (UTC)

@sashank: Aargh... I hate it when upstream messes with tags like that..Fixed.

From https://github.com/OpenNMT/CTranslate2
 - [deleted]           (none)     -> 4.6.0
 * [new tag]           v4.6.0     -> v4.6.0

sashank commented on 2025-04-08 19:47 (UTC)

Setting source to "git+https://github.com/OpenNMT/CTranslate2.git#tag=$pkgver"

and sha256sums '78111a078f17b809274c3adf00ffa33c35c729f82bde17c64e091ebc5bd1b400'

gets me the following error at the stage: Validating source files with sha256sums... CTranslate2 ... fatal: not a valid object name: 4.6.0

Did you put in the right hash? They just set the commit tag 4.6.0 four hours ago.

1 2 3 Next › Last »