Arch Linux User Repository

@Rus The package builds fine on my end so this is either a configuration error/incompatibility on your system's part, or an upstream bug. Given the nature of the error, and adding @damian101's errors to the mix (which I at first suspected to be due to LTO, but it turns out the errors can also manifest with LTO disabled) I suspect it's probably an upstream bug. But if I were you I'd still try building in a clean chroot (if you haven't done so already) in order to completely rule out configuration errors/incompatibilities.

«VSC_TRANSFER_ST428» was not declared in this scope; did you mean «VSC_TRANSFER_ST2084»? <brace-enclosed initializer list>

Hmm, it's kind of weird because I just got a different but similar linker error when I tried to rebuild and reproduce your error:

undefined reference to `p2p::packed_to_planar<p2p::packed_v210_be>`

But I unintentionally discarded the failed build log before I read it thoroughly, so without changing anything in the PKGBUILD I tried to rebuild a second time, and this time there were no errors and the build completed successfully; and from then on it keeps building as successfully as ever. So... maybe try rebuilding and see if the issue has fixed itself automagically on your end as well?

EDIT: Just got another linker error which again went away after one rebuild. If I had to guess, I'd say it's an incompatibility with LTO.

Doesn't compile:

/usr/bin/ld: /tmp/ccMcuuYK.ltrans6.ltrans.o:(.debug_info+0x39): undefined reference to `scroll_navigator.cpp.393d9aff'
/usr/bin/ld: /tmp/ccMcuuYK.ltrans6.ltrans.o:(.debug_info+0x54): undefined reference to `scroll_navigator.cpp.393d9aff'
/usr/bin/ld: /tmp/ccMcuuYK.ltrans6.ltrans.o:(.debug_info+0x7c): undefined reference to `scroll_navigator.cpp.393d9aff'
/usr/bin/ld: /tmp/ccMcuuYK.ltrans6.ltrans.o:(.debug_info+0x97): undefined reference to `scroll_navigator.cpp.393d9aff'
/usr/bin/ld: /tmp/ccMcuuYK.ltrans6.ltrans.o:(.debug_info+0xa4): undefined reference to `scroll_navigator.cpp.393d9aff'
/usr/bin/ld: /tmp/ccMcuuYK.ltrans6.ltrans.o:(.debug_info+0xbe): more undefined references to `scroll_navigator.cpp.393d9aff' follow
g++ -c -pipe -O2 -fexpensive-optimizations -funit-at-a-time -std=c++17 -Wall -Wextra -Wredundant-decls -Wshadow -pedantic -march=native -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -g -ffile-prefix-map=/home/damian101/.cache/yay/vapoursynth-editor-git/src=/usr/src/debug/vapoursynth-editor-git -flto=auto -mno-direct-extern-access -D_REENTRANT -Wall -Wextra -DNDEBUG -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB -DQT_CORE5COMPAT_LIB -DQT_CORE_LIB -I. -I/usr/include/qt6 -I/usr/include/qt6/QtWidgets -I/usr/include/qt6/QtGui -I/usr/include/qt6/QtWebSockets -I/usr/include/qt6/QtNetwork -I/usr/include/qt6/QtCore5Compat -I/usr/include/qt6/QtCore -I../../vsedit-job-server-watcher/generated/moc -I../../vsedit-job-server-watcher/generated/ui -I/usr/lib/qt6/mkspecs/linux-g++ -o ../../vsedit-job-server-watcher/generated/obj-release-64bit-gcc/moc_connect_to_server_dialog.o ../../vsedit-job-server-watcher/generated/moc/moc_connect_to_server_dialog.cpp
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:566: ../../build/release-64bit-gcc/vsedit] Error 1
make[1]: Leaving directory '/home/damian101/.cache/yay/vapoursynth-editor-git/src/vapoursynth-editor/pro/vsedit'
make: *** [Makefile:50: sub-vsedit-vsedit-pro-make_first] Error 2

okey never mind, I just tried one of the other vsedit aur packages available: https://aur.archlinux.org/packages/vapoursynth-editor-git and that worked out of the box :)

Seems this doesn't work with current Vapoursynth versions, ran into this error: https://github.com/vapoursynth/vapoursynth/issues/845

User @DeadNews suggested to switch to fork https://github.com/YomikoR/VapourSynth-Editor which he says works with APIv4 which seems to be a must have for current versions.

Is there a ready AUR package for that (or a similar) fork or some easy to use instructions how to adapt the build script of this package to do that myself on the fly?

@compiler1413 Thank you!!! Your PKGBUILD works fine! :)

Edited PKGBUILD kinda sloppily but this builds fine with the suggested new upstream URL.

# Maintainer: Maxime Gauduin <alucryd@archlinux.org>
# Contributor: Gustavo Alvarez <sl1pkn07@gmail.com>

pkgname=vapoursynth-editor
pkgver=r19
pkgrel=4
pkgdesc='VapourSynth script editor'
arch=(x86_64)
url=https://github.com/YomikoR/VapourSynth-Editor
license=(
  CCPL
  MIT
)
depends=(
  qt5-base
  qt5-websockets
  vapoursynth
)
makedepends=(git)
source=(
  https://github.com/YomikoR/VapourSynth-Editor/archive/refs/tags/r19-mod-4.zip
  vsedit.desktop
)
sha256sums=(
  SKIP
  b6d24441cf5746ea4dc08ecf379c67695bac663deb394db4334ba6aba9474c0f
)

build() {
  cd VapourSynth-Editor-"$pkgver"-mod-"$pkgrel"/pro

  qmake-qt5
  make
}

package() {
  cd VapourSynth-Editor-"$pkgver"-mod-"$pkgrel"/build/release-64bit-gcc

  install -Dm 755 vsedit -t "${pkgdir}"/usr/bin/
  install -Dm 644 vsedit.svg -t "${pkgdir}"/usr/share/pixmaps/
  install -Dm 644 ../../../vsedit.desktop -t "${pkgdir}"/usr/share/applications/
  install -Dm 644 LICENSE -t "${pkgdir}"/usr/share/licenses/vapoursynth-editor/
}

# vim: ts=2 sw=2 et:

patch:

5,6c5,6
< pkgver=R19
< pkgrel=1
---
> pkgver=r19
> pkgrel=4
9c9
< url=https://bitbucket.org/mystery_keeper/vapoursynth-editor
---
> url=https://github.com/YomikoR/VapourSynth-Editor
21c21
<   git+https://bitbucket.org/mystery_keeper/vapoursynth-editor.git#tag=${pkgver,}
---
>   https://github.com/YomikoR/VapourSynth-Editor/archive/refs/tags/r19-mod-4.zip
30c30
<   cd vapoursynth-editor/pro
---
>   cd VapourSynth-Editor-"$pkgver"-mod-"$pkgrel"/pro
37c37
<   cd vapoursynth-editor/build/release-64bit-gcc
---
>   cd VapourSynth-Editor-"$pkgver"-mod-"$pkgrel"/build/release-64bit-gcc

Suggestion to switch to fork — https://github.com/YomikoR/VapourSynth-Editor — because it is compatible with the new versions of Vapoursynth (API 4).

Stop flagging this package, r19 is the last version, the r20 mentioned on the main page does not exist.