Search Criteria
Package Details: vapoursynth-editor r19_mod_6.6-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/vapoursynth-editor.git (read-only, click to copy) |
---|---|
Package Base: | vapoursynth-editor |
Description: | Editor for VapourSynth scripts |
Upstream URL: | https://github.com/YomikoR/VapourSynth-Editor |
Licenses: | CC-BY-2.5 AND CC-BY-3.0 AND CC-BY-4.0 AND MIT |
Submitter: | alucryd |
Maintainer: | Nocifer |
Last Packager: | Nocifer |
Votes: | 15 |
Popularity: | 0.011169 |
First Submitted: | 2014-08-21 20:02 (UTC) |
Last Updated: | 2024-04-12 12:09 (UTC) |
Latest Comments
1 2 Next › Last »
Nocifer commented on 2024-04-13 10:02 (UTC)
@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.
Rus commented on 2024-04-12 23:17 (UTC)
«VSC_TRANSFER_ST428» was not declared in this scope; did you mean «VSC_TRANSFER_ST2084»? <brace-enclosed initializer list>
Nocifer commented on 2024-03-28 11:39 (UTC) (edited on 2024-03-28 11:58 (UTC) by Nocifer)
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:
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.
damian101 commented on 2024-03-28 08:14 (UTC)
Doesn't compile:
limokig421 commented on 2022-03-27 07:20 (UTC)
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 :)
limokig421 commented on 2022-03-27 07:18 (UTC)
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?
Win8Error commented on 2021-11-13 20:27 (UTC)
@compiler1413 Thank you!!! Your PKGBUILD works fine! :)
compiler1413 commented on 2021-11-01 20:34 (UTC) (edited on 2021-11-01 20:35 (UTC) by compiler1413)
Edited PKGBUILD kinda sloppily but this builds fine with the suggested new upstream URL.
patch:
DeadNews commented on 2021-10-09 11:38 (UTC)
Suggestion to switch to fork — https://github.com/YomikoR/VapourSynth-Editor — because it is compatible with the new versions of Vapoursynth (API 4).
alucryd commented on 2019-03-26 13:26 (UTC)
Stop flagging this package, r19 is the last version, the r20 mentioned on the main page does not exist.
1 2 Next › Last »