Package Details: pdftk 2.02-17

Git Clone URL: https://aur.archlinux.org/pdftk.git (read-only)
Package Base: pdftk
Description: Pdftk is a simple tool for doing everyday things with PDF documents
Upstream URL: http://www.pdfhacks.com/pdftk
Licenses: GPL
Submitter: Snowman
Maintainer: valandil
Last Packager: valandil
Votes: 400
Popularity: 2.186538
First Submitted: 2006-04-29 04:57
Last Updated: 2017-08-02 17:42

Pinned Comments

valandil commented on 2015-12-08 14:54

If you don't want to compile gcc-gcj, use pdftk-bin.

https://aur.archlinux.org/packages/pdftk-bin/

Latest Comments

valandil commented on 2017-07-05 19:08

After checking the manual (https://www.gnu.org/software/bash/manual/bash.html#Special-Parameters), I think I'll go for pdftk-bin "$@", as severach recommends.

Sorry for the incessant updates.

severach commented on 2017-07-05 19:05

Shouldn't it be pdftk-bin "$@"

mkoloberdin commented on 2017-07-05 18:54

valandil,

pdftk-bin should be called as

pdftk-bin $*

from the script to pass through all the arguments to the binary.

valandil commented on 2017-07-05 01:54

Good idea. It's now in the package.

mkoloberdin commented on 2017-07-04 23:42

valandil, on the other hand, a wrapper seems to be the most proper approach.
Here is the solution I am proposing (tested): https://pastebin.com/jCGAengd

mkoloberdin commented on 2017-07-04 23:21

valandil, no, prepending/appending does not make any difference, as the dynamic linker picks up whatever is in the LD_LIBRARY_PATH before its configuration (/etc/ld.so.conf[.d]).

Static compilation perhaps might be a solution in this case?

Quoting from http://xahlee.info/UnixResource_dir/_/ldpath.html
Canonical rules for handling LD_LIBRARY_PATH

1. Never ever set LD_LIBRARY_PATH globally.
2. If you must ship binaries that use shared libraries and want to allow your clients to install the program outside a 'standard' location, do one of the following:
Ship your binaries as .o files, and as part of the install process relink them with the correct installation library path.
Ship executables with a very long “dummy” run-time library path, and as part of the install process use a binary editor to substitute the correct install library path in the executable.
3. If you are forced to set LD_LIBRARY_PATH, do so only as part of a wrapper.

valandil commented on 2017-07-04 13:50

Hmm, okay. I'm not sure how to fix this without breaking stuff. Would prepending to LD_LIBRARY_PATH instead of appending change anything? Could you test it?

mkoloberdin commented on 2017-07-04 10:38

"Is that the result of my pdftk.sh"
Yes.

valandil commented on 2017-07-03 17:00

Is that the result of my pdftk.sh or your own change of LD_LIBRARY_PATH?

mkoloberdin commented on 2017-07-03 16:12

valandil, indeed, setting LD_LIBRARY_PATH globally breaks things:

bitcoin-qt: /lib/gcc/x86_64-pc-linux-gnu/6.3.1/libstdc++.so.6: version `CXXABI_1.3.11' not found (required by bitcoin-qt)

All comments