Arch Linux User Repository

@ReStranger

seems you have a non default set of flags that turbobase64 doesn't seem to like, you can compile ueberzugpp without support for it, just edit the PKGBUILD.

I have this

100%] Linking C shared library libbase64.so
/usr/bin/ld: CMakeFiles/_b64_avx.dir/turbob64v128.c.o (symbol from plugin): в функции «tb64v128adec»:
(.text+0x0): повторное определение «tb64v128adec»; CMakeFiles/_b64_v128.dir/turbob64v128.c.o (symbol from plugin):(.text+0x0): здесь первое определение
/usr/bin/ld: CMakeFiles/_b64_avx.dir/turbob64v128.c.o (symbol from plugin): в функции «tb64v128adec»:
(.text+0x0): повторное определение «tb64v128aenc»; CMakeFiles/_b64_v128.dir/turbob64v128.c.o (symbol from plugin):(.text+0x0): здесь первое определение
collect2: ошибка: выполнение ld завершилось с кодом возврата 1
make[2]: *** [CMakeFiles/base64.dir/build.make:93: libbase64.so] Ошибка 1
make[1]: *** [CMakeFiles/Makefile2:227: CMakeFiles/base64.dir/all] Ошибка 2
make: *** [Makefile:136: all] Ошибка 2
==> ОШИБКА: Произошел сбой в build().
    Прерывание...
 -> Failed to install layer, rolling up to next layer.error:ошибка сборки: turbo-base64 - exit status 4

and this error

[100%] Linking C shared library libbase64.so
/usr/bin/ld: CMakeFiles/_b64_avx.dir/turbob64v128.c.o (symbol from plugin): в функции «tb64v128adec»:
(.text+0x0): повторное определение «tb64v128adec»; CMakeFiles/_b64_v128.dir/turbob64v128.c.o (symbol from plugin):(.text+0x0): здесь первое определение
/usr/bin/ld: CMakeFiles/_b64_avx.dir/turbob64v128.c.o (symbol from plugin): в функции «tb64v128adec»:
(.text+0x0): повторное определение «tb64v128aenc»; CMakeFiles/_b64_v128.dir/turbob64v128.c.o (symbol from plugin):(.text+0x0): здесь первое определение
collect2: ошибка: выполнение ld завершилось с кодом возврата 1
make[2]: *** [CMakeFiles/base64.dir/build.make:93: libbase64.so] Ошибка 1
make[1]: *** [CMakeFiles/Makefile2:227: CMakeFiles/base64.dir/all] Ошибка 2
make: *** [Makefile:136: all] Ошибка 2
==> ОШИБКА: Произошел сбой в build().
    Прерывание...
 -> ошибка сборки: turbo-base64-exit status 4
==> Сборка пакета ueberzugpp 2.9.5-1 (Вс 26 мая 2024 12:18:53)
==> Проверка зависимостей для запуска...
==> Недостающие зависимости:
  -> turbo-base64
==> Проверка зависимостей для сборки...
==> ОШИБКА: Не удалось разрешить все зависимости.
 -> ошибка сборки: ueberzugpp-exit status 8
 -> Failed to install the following packages. Manual intervention is required:
turbo-base64 - exit status 4
ueberzugpp - exit status 8

when i build ueberzugpp

my makepkg.conf

CARCH="x86_64"
CHOST="x86_64-pc-linux-gnu"

#-- Compiler and Linker Flags
#CPPFLAGS=""
CFLAGS="-march=znver2 -mtune=generic -O3 -pipe -fno-plt -fexceptions \
        -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security \
        -fstack-clash-protection -fcf-protection \
        -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"
CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now \
         -Wl,-z,pack-relative-relocs"
LTOFLAGS="-flto=auto"
RUSTFLAGS="-Cforce-frame-pointers=yes -C target-cpu=znver2 -C opt-level=3"
#-- Make Flags: change this for DistCC/SMP systems
#MAKEFLAGS="-j2"
#-- Debugging flags
DEBUG_CFLAGS="-g"
DEBUG_CXXFLAGS="$DEBUG_CFLAGS"
DEBUG_RUSTFLAGS="-C debuginfo=2"

@JamesArchibald, I deleted the mismatching '2023.08.tar.gz' file and re-downloaded, then the build was successful (for the 2023.08-2 version).

According to the recent change of the PKGBUILD, I suspect that the upstream repo has re-tagged a different commit with the same tag 2023.08, which results in a different '2023.08.tar.gz' file. If so, this is probably a bad practice, a new tag should be created.

Hi, I just tried installing this as a dep for ueberzugpp, but I run into

ERROR: One or more files did not pass the validity check!

Any ideas? I guess I can force it somehow, but this should probably be sorted out as part of the PKGBUILD?

Thanks

Thank you, that was it! I went ahead and removed some problematic custom flags and it compiled just fine. Sorry for the bother.

that shouldn't be possible, unless you have some weird flags or lto enabled idk. Builds fine on my end.

Hi again. For this package, similar to how it was with ueberzugpp, I'm getting the following error:

/usr/bin/ld: CMakeFiles/_b64_avx.dir/turbob64v128.c.o: in function `tb64v128adec':
turbob64v128.c:(.text+0x0): multiple definition of `tb64v128adec'; CMakeFiles/_b64_v128.dir/turbob64v128.c.o:turbob64v128.c:(.text+0x0): first defined here
/usr/bin/ld: CMakeFiles/_b64_avx.dir/turbob64v128.c.o: in function `tb64v128aenc':
turbob64v128.c:(.text+0x7c0): multiple definition of `tb64v128aenc'; CMakeFiles/_b64_v128.dir/turbob64v128.c.o:turbob64v128.c:(.text+0x7c0): first defined here
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/base64.dir/build.make:93: libbase64.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:227: CMakeFiles/base64.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

Thanks once more.