This was updated with a recent push. Glib recently deprecated that function which glib now runs 'automagically'.
The error is because I've been strict with the compiler flags using -Werror. I could remove that from the distributed makefile, but having it does ensure that someone will tell me if anything is wrong ;)
Without -Werror it would compile fine with only a warning, but the better solution was to remove the g_type_init call.
Search Criteria
Package Details: leela-git 12.fe7a35a-1
Git Clone URL: | https://aur.archlinux.org/leela-git.git (read-only) |
---|---|
Package Base: | leela-git |
Description: | CLI frontend to poppler-glib of PDF tools |
Upstream URL: | http://github.com/TrilbyWhite/Leela |
Licenses: | |
Submitter: | Trilby |
Maintainer: | Trilby |
Last Packager: | Trilby |
Votes: | 4 |
Popularity: | 0.000000 |
First Submitted: | 2012-06-05 06:39 |
Last Updated: | 2015-06-08 23:04 |
Dependencies (3)
Required by (0)
Sources (1)
Latest Comments
skanky commented on 2013-05-21 19:07
Trilby commented on 2013-05-21 18:14
skanky commented on 2013-05-18 12:24
Many thanks for that. I'm now getting a build error (I probably didn't need to rebuild, but thought I'd test the new PKGBUILD):
==> Starting build()...
leela.c: In function ‘main’:
leela.c:323:2: error: ‘g_type_init’ is deprecated (declared at /usr/include/glib-2.0/gobject/gtype.h:669) [-Werror=deprecated-declarations]
g_type_init();
^
cc1: all warnings being treated as errors
make: *** [leela] Error 1
==> ERROR: A failure occurred in build().
Aborting...
Trilby commented on 2013-05-18 11:30
Doh. Sorry, I had added and commited my whole working directory at some point without first cleaning the binary. That is fixed now.
skanky commented on 2013-04-04 16:14
Sorry, I deleted previous comment as I messed up what I was writing.
Okay, when building this using makepkg -i on a 64 bit machine, the "leela" source gets pulled with a compiled 32bit executable. When that dir gets cloned to leela-build and make is executed in there, it says that leela is up to date and does nothing. Thus the package gets built with a 32bit executable.
skanky commented on 2013-04-04 16:05
Hi, when I try and build this with makepkg on my 64bit machine, it builds it as a 32bit application. This is the first time I've seen this so I'm guessing it's package specific. I'll start digging, but just though I'd check here first.
Trilby commented on 2012-06-05 06:40
Package announcement here:
https://bbs.archlinux.org/viewtopic.php?pid=1107930#p1107930
I did think it might compile without -Werror, but also know it's normally included for a reason, so didn't want to mess.
Many thanks for the update. Compiled no problem.
And thanks for the very useful application.