Package Details: epub-tools 2.9-2

Git Clone URL: (read-only)
Package Base: epub-tools
Description: Command line utilities for working with epub files
Upstream URL:
Licenses: BSD3
Submitter: dno
Maintainer: dno
Last Packager: dno
Votes: 9
Popularity: 0.000087
First Submitted: 2013-02-02 13:59
Last Updated: 2016-10-27 00:52

Latest Comments

JohnRobson commented on 2017-10-24 19:17

/usr/sbin/ld: /home/us/.stack/programs/x86_64-linux/ghc-tinfo6-nopie-8.0.1/lib/ghc-8.0.1/rts/libCffi.a(ffi64.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
/usr/sbin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
`gcc' failed in phase `Linker'. (Exit code: 1)
Exit code ExitFailure 1 while running ["ghc","-rtsopts","-threaded","-clear-package-db","-global-package-db","-hide-all-packages","-package","base","-main-is","StackSetupShim.mainOverride","-package","Cabal-","/home/us/.stack/setup-exe-src/setup-mPHDZzAJ.hs","/home/us/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs","-o","/home/us/.stack/setup-exe-cache/x86_64-linux-tinfo6-nopie/tmp-Cabal-simple_mPHDZzAJ_1.24.0.0_ghc-8.0.1"] in /tmp/stack22297/
Can't continue because stack install failed
==> ERROR: A failure occurred in package().
==> ERROR: Makepkg was unable to build epub-tools.

dno commented on 2016-10-27 00:53

sikmir: Thank you for catching this and reporting.

sikmir commented on 2016-10-26 21:03

dno: Add ghc to dependencies.

No compiler found, expected minor version match with ghc-8.0.1 (x86_64-ncurses6) (based on resolver setting in /tmp/yaourt-tmp-sikmir/aur-epub-tools/src/epub-tools-2.9/stack.yaml).
Try running "stack setup" to install the correct GHC into /home/sikmir/.stack/programs/x86_64-linux/
==> ERROR: A failure occurred in package().
==> ERROR: Makepkg was unable to build epub-tools.

giddie commented on 2015-02-09 16:56

Thanks for mentioning the issue, though. I don't use Haskell myself, so cabal-install was pulled in as a dependence, and of course I ran into the same build issue. Maybe the PKGBUILD could catch the process failure and at least provide an error message to suggest update cabal?

dno commented on 2013-04-14 17:09

mikecr: You know, working on the latest, I had some other weirdness happen. Now not sure if what you're seeing wasn't part of that. For now I removed 'cabal-dev update' from the build() function. But everybody do 'cabal update' before building this, like you'd do a 'pacman -Sy' to freshen up, same idea.

dno commented on 2013-04-10 14:49

mikecr: If your cabal package list was old, this can happen. It's just like having stale pacman lists and needing to do an -Sy

Bearing that in mind, I'm not sure if it's appropriate for me to make the build do a `cabal update` automatically. We generally don't automate that part of these tools, I guess so as to not hammer servers with it unnecessarily.

What do you guys think?

mikecr commented on 2013-04-10 10:04

Howdy, if anyone is having troubles with this building this and is getting

You are using a version of cabal-install that has the --only-dependencies flag
to the install command. Invoking that instead...
Resolving dependencies...
cabal: Could not resolve dependencies:
trying: epub-tools-2.1.1
==> ERROR: A failure occurred in build().
==> ERROR: Makepkg was unable to build epub-tools.

I ran cabal update and then tried again and it was fine. I don't really know why this is... I was using cabal-dev-git from AUR.