Search Criteria
Package Details: vapoursynth-editor r19_mod_6.8-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.000137 |
First Submitted: | 2014-08-21 20:02 (UTC) |
Last Updated: | 2024-07-14 12:45 (UTC) |
Latest Comments
1 2 Next › Last »
Rus commented on 2024-07-31 21:59 (UTC)
compiled and works without problems
but other necessary VS software does not compile because of ffmpeg7 (or other updates) >_<
Nocifer commented on 2024-07-20 16:06 (UTC)
When building in a chroot for testing purposes I too encountered a similar issue and my build also failed, but when I tried to reproduce it in my normal environment it built successfully, and then when I tried once more in a chroot it again built successfully.
This has been an issue for some time now (see the previous comments) and as it is rather intermittent, I've concluded that it's probably a bug in the upstream code itself (or maybe in Qt 6.7) that makes the linker fail.
My advice to you: try rebuilding the package a few times, and at some point it will probably succeed. And if you happen to find a solution, or even a hint to a possible solution, please do share it here.
Fifis commented on 2024-07-20 08:30 (UTC)
This fails on my machine:
Recently, I found out painfully that some parallel stuff (like
libcuba
for scientific computations) fails at the linking stage if the number of cores exceeds 7. However, here it does not seem to be the problem because the-git
version compiles with the samemakepkg.config
without a hindrance. It is either thePKGBUILD
or some GitHub-exclusive changes that seem to matter here.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! :)
1 2 Next › Last »