























It simply is enough to forcefully disable LTO by adding
options+=('!lto')
to the PKGBUILD. At least for me this fixes the mentioned build error.
Regards and thanks for maintaining!
P.S.: The license identifier should be made SPDX compliant.
I also ran into guglovich's error and traced it to the way the aws-lc library gets built on arch. Resolutions are either disabling injecting -flto=auto globally in makepkg.conf - or changing the PKGBUILD build() function:
build() {
cd "$pkgname-${pkgver}"
export CFLAGS="${CFLAGS/ -flto=auto/}"
export CFLAGS_x86_64_unknown_linux_gnu="$CFLAGS"
export RUSTUP_TOOLCHAIN=stable
export CARGO_TARGET_DIR=target
cargo build --frozen --release
}
@bksalman: i would suggest updating the PKGBUILD - unless users modified their stock makepkg.conf users will keep running into this with rust packages.
ld.lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors)
collect2: error: ld returned 1 exit status
error: could not compile ytdlp-gui (bin "ytdlp-gui") due to 1 previous error
@dreieck thank you for telling me, my automated process seems to not have done that, will look into it as soon as possible
Checksum verification fails after update of the PKGBUILD:
==> Validating source files with sha256sums...
ytdlp-gui-1.1.1.tar.gz ... FAILED
Regards and thanks for maintaining!
@sqfreak I have a symlink to the PKGBUILD on my machine, and I just edit that, but for some reason the sha256sum update didn't get passed? I'm really not sure what happened, anyways sorry for how messy this package is, I'm stupid
(will update it soon)
I think you may have missed updating the sha256sum for 0.3.0. The one I get from the file on Github is dee55b85f303b10dd9a3d922a9ec757a3b7c6c953da447e7e5effb2857f51d3f and the package has b7e1a8350dc69f583122df4bc43c6968ab1f11a3282472f1fc52b47630387f0c, which is the sha256sum for version 0.2.5 on Github.
@JisuWoniu oops, thanks for spotting it for me! will push a fix soon
You made a typo in build function. Should be --frozen instead of --forzen.
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。
I confirm that adding options=('!lto') is necessary. I hit the same aws-lc linking error today and this fixed it.