[SOLVED] pdftk for Slackware64-current.

larryhaja · 11-12-2009, 09:46 AM

Quote:

Originally Posted by Martinezio

In Makefile.Generic You need to add -fPIC option into CPPFLAGS and CXXFLAGS vars, and run the make with LDFLAGS="-L/usr/lib64" envar

I forgot to mention that I did a couple extra things as well but just the gcc 4.3 patch alone worked for me. You can make use of the CFLAGS by adding a simple sed statement before or after the patches are applied and an additional patch to introduce LDFLAGS. I didn't think they were relevant.

Code:

# sed -i "s|-O2|$SLKCFLAGS|" pdftk/Makefile.Generic

Code:

# wget http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/app-text/pdftk/files/pdftk-1.41-honor-ldflags.patch

hemp4fuel · 11-12-2009, 08:38 PM

Quote:

Originally Posted by Martinezio

Disagree - works for me on x86_64 platform with small change

In Makefile.Generic You need to add -fPIC option into CPPFLAGS and CXXFLAGS vars, and run the make with LDFLAGS="-L/usr/lib64" envar

No more "Incorrect ABI version" issues, and pdftk is fully working now!
Thanks for the patches

It still won't build on x86_64 here. I will keep trying.

Martinezio · 11-13-2009, 02:32 AM

hemp4fuel: Hmm... You cannot build, or build is successful, but You have "Incorrect ABI version" issue while running pdftk tool?

Paste Your error messages, so We be able to help You a bit

Yalla-One · 11-16-2009, 07:31 AM

Thanks for looking after pdftk in my absense, since I've been the original maintainer. I've tried to get a few to inherit ownership in the past with no success.
Turns out I'm completely out of spare time at the moment between family and work, and thus would greatly appreciate if anyone volunteered to assume ownership over my orphan slackbuilds..

Thanks in advance!

Martinezio · 11-16-2009, 08:54 AM

Well, I'm also haven't spare time to manage of this SlackBuild, but I've been able to merge all the changes mentioned in this thread, and made a single patch file.
I also add some of my modification to support custom install prefixes, and path for packaging

Enjoy!

escaflown · 11-16-2009, 06:58 PM

Quote:

Originally Posted by Martinezio

Well, I'm also haven't spare time to manage of this SlackBuild, but I've been able to merge all the changes mentioned in this thread, and made a single patch file.
I also add some of my modification to support custom install prefixes, and path for packaging

Enjoy!

I wonder if Slackbuilds could be created out of patched source files. In the general slackbuild procedure, there is always a link for downloading the source and in our case, the source is going to be the patched version. So ...

Martinezio · 11-17-2009, 02:41 AM

Hmm... I think, that the very best way is to get the original source and apply patch by SlackBuild script.
You cannot rely on applying any changes by author of pdftk. This tool isn't mainained yet, AFAIK.

Yalla-One · 11-19-2009, 09:21 AM

Building with patch from Martinezio now - if all works and pdftk remains fully functional I'll send an update to SBo asap to get it official. Thanks for the patience.

-y1

Yalla-One · 11-19-2009, 09:42 AM

Works - update submitted - thanks again to Martinezio!

escaflown · 11-19-2009, 08:36 PM

Quote:

Originally Posted by Yalla-One

Works - update submitted - thanks again to Martinezio!

That's great.

Thursapr · 11-19-2009, 10:47 PM

Still don't see pdftk SlackBuild for slackware 13.

escaflown · 11-20-2009, 12:57 AM

Quote:

Originally Posted by Thursapr

Still don't see pdftk SlackBuild for slackware 13.

He said he submitted the update ... I guess it has to be approved before you can see it

Yalla-One · 11-20-2009, 04:17 AM

Quote:

Originally Posted by Thursapr

Still don't see pdftk SlackBuild for slackware 13.

It normally takes a while from a build is submitted until it's approved. Check out the slackbuilds.org documentation and faq for more information.

Meanwhile, if you cannot wait, you can get the SlackBuild and patch from here:
http://hiawata.com/linux/pdftk/

I'd wait for the officially sanctioned version by the SBo team though - the guys there do a terrific job and validate everything in every build carefully for errors etc.

-y1