Package Details: libpdfium-nojs 6778.r0.7a8409531f-1

Git Clone URL: https://aur.archlinux.org/libpdfium-nojs.git (read-only, click to copy)
Package Base: libpdfium-nojs
Description: Open-source PDF rendering engine.
Upstream URL: https://pdfium.googlesource.com/pdfium/
Keywords: pdf pdfium
Licenses: BSD
Conflicts: libpdfium-bin
Provides: libpdfium
Submitter: selmf
Maintainer: selmf
Last Packager: selmf
Votes: 23
Popularity: 0.85
First Submitted: 2017-07-30 18:14 (UTC)
Last Updated: 2024-11-19 08:21 (UTC)

Pinned Comments

selmf commented on 2021-05-24 11:20 (UTC)

Important: This package depends on libicuuc and needs to be rebuild if the icu package is updated on your system!

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 Next › Last »

selmf commented on 2020-11-02 12:16 (UTC)

The package does in fact not build from the newest git commit but the latest stable branch, which occasionally receives backports and security fixes during its lifetime. Git master is only pulled to keep track of those changes.

DDoSolitary commented on 2020-11-01 20:32 (UTC) (edited on 2020-11-01 20:32 (UTC) by DDoSolitary)

As the package is building from latest git commit, I think it's should be made libpdfium-nojs-git, according to VCS package guidelines

justicehunter commented on 2020-10-07 22:36 (UTC)

I am getting the following error:

line 52: cd: /home/oguz/.cache/yay/libpdfium-nojs/src/pdfium/build: No such file or directory

selmf commented on 2020-09-02 12:52 (UTC) (edited on 2020-09-07 12:01 (UTC) by selmf)

Due to a bug in ld (https://bugs.archlinux.org/task/67671) this package currently can't be build with binutils 2.35. You need to downgrade to binutils 2.34.

Edit: I have added a workaround so the build should work fine now.

STEELBAS commented on 2020-09-02 12:48 (UTC)

Same error as alex1a. Haven't been able to find a fix, so far.

alexjorgef commented on 2020-08-31 18:38 (UTC)

  • binutils 2.35-1
  • linux 5.8.5-arch1-1
  • yay v10.0.4
[487/487] SOLINK ./libpdfium.so
FAILED: libpdfium.so libpdfium.so.TOC 
/usr/bin/python2 "../../build/toolchain/gcc_solink_wrapper.py" --readelf="readelf" --nm="nm" --sofile="./libpdfium.so" --tocfile="./libpdfium.so.TOC" --output="./libpdfium.so" -- g++ -shared -Wl,-soname="libpdfium.so" -Wl,--fatal-warnings -Wl,--build-id -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,defs -Wl,--as-needed -fuse-ld=gold -Wl,--threads -Wl,--thread-count=4 -m64 -Wl,-O2 -Wl,--gc-sections -rdynamic -Wl,-rpath=\$ORIGIN -o "./libpdfium.so" @"./libpdfium.so.rsp"
collect2: fatal error: ld terminated with signal 11 [Segmentation fault], core dumped
compilation terminated.
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
    Aborting...
error making: libpdfium-nojs

kinoe commented on 2020-08-25 04:35 (UTC)

I was mistaken, after downgrading binutils libpdfium-nojs built fine as a dependency of megasync which wasn't built

selmf commented on 2020-08-24 23:14 (UTC)

In my case I was able to build again after the downgrade, but that was a different error from yours. Are you using any build chain components or dependencies that are non-standard variants (AUR, testing)?

kinoe commented on 2020-08-24 19:02 (UTC)

unfortunately build aborts even with binutils downgraded to 2.34

selmf commented on 2020-08-24 16:55 (UTC)

@kinoe: I can't reproduce your exact error but building with the latest binutils fails for me with a different (but similar) message.

My guess is a bug in binutils, likely: https://bugs.archlinux.org/task/67671 As a workaround you can try downgrading binutils to v2.34