Package Details: libpdfium-nojs 4183.r0.6069b8345e-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: 14
Popularity: 1.69
First Submitted: 2017-07-30 18:14
Last Updated: 2020-09-07 11:54

Latest Comments

1 2 3 4 Next › Last »

selmf commented on 2020-09-02 12:52

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

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

alex1a commented on 2020-08-31 18:38

  • 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

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

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

unfortunately build aborts even with binutils downgraded to 2.34

selmf commented on 2020-08-24 16:55

@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

kinoe commented on 2020-08-24 16:05

build stopped

[485/485] 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 -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"
malloc(): smallbin double linked list corrupted
collect2: fatal error: ld terminated with signal 6 [Aborted], core dumped
compilation terminated.
ninja: build stopped: subcommand failed.

selmf commented on 2020-05-27 15:41

@WonderCaT_007: Thanks for reporting. I don't think you need to be concerned. The files in question are part of Pdfium's test corpus and they probably are present to test if Pdfium is vulnerable to the exploits contained.

None of these files are being installed or run by the package and as the package comes with javascript support disabled many exploits won't work anyway.

While I still wouldn't recommend opening these with a pdf reader I don't think they contain malicious code (probably the exploit only, no payload). But that is just my assumption, upstream can probably tell you more.

WonderCaT_007 commented on 2020-05-27 15:27

The package was creation was successful. However, I did a clamav scan of the build directory and it detected two files as malicious or contains some kind of exploit code. To confirm the detection, I just checked those files with online virustotal, and one of them were detected by 18 anti virus engines. Should we be concerned?

Here are the files: libpdfium-nojs/src/pdfium/testing/resources/js.pdf: Pdf.Dropper.Agent-7158272-0 FOUND < Detected by 18 av engines in Virustotal

libpdfium-nojs/src/pdfium/testing/resources/pixel/bug_867501.pdf: Pdf.Exploit.TALOS_2018_0639-6680787-0 FOUND < Detected just by clamav