I'm getting linking errors because my C/C++ objects are targeting x86_64-pc-linux-gnu
and rust is targeting x86_64-unknown-linux-gnu
. rustc doesn't even seem to support x86_64-pc-linux-gnu
as valid target. See example below.
ld.lld: error: Linking two modules of different target triples: 'obj/base/nodebug_assertion/nodebug_assertion.o' is 'x86_64-pc-linux-gnu' whereas 'obj/components/qr_code_generator/libcomponents_sqr_ucode_ugenerator_cqr_ucode_ugenerator_uffi_uglue.rlib(libcomponents_sqr_ucode_ugenerator_cqr_ucode_ugenerator_uffi_uglue.components_sqr_ucode_ugenerator_cqr_ucode_ugenerator_uffi_uglue.93cc98de3648a0e9-cgu.0.rcgu.o at 8722)' is 'x86_64-unknown-linux-gnu'
Pinned Comments
JstKddng commented on 2022-05-06 14:37 (UTC) (edited on 2022-06-27 13:48 (UTC) by JstKddng)
A new va-api patch for wayland has been added. Required flags for it to work are the following, thanks to @acidunit
JstKddng commented on 2020-07-19 06:34 (UTC)
You can get prebuilt binaries here:
https://github.com/ungoogled-software/ungoogled-chromium-archlinux#binary-downloads
seppia commented on 2018-12-12 21:34 (UTC)
Please do NOT flag this package as out of date in relation to official chromium releases.
This is NOT Google Chromium and new releases come after additional work of the ungoogled-chromium contributors, so they may not be ready, nor available for days or even weeks after a new version of official chromium is released.
Please refer to https://github.com/Eloston/ungoogled-chromium/tags for ungoogled-chromium releases. Use those and please flag this package as out of date only if a newer release is present there. I will update the PKGBUILD as soon as I can every time a new release comes out.
Thanks