You are not logged in.
There is a newer version for about four month of gtkparasite, but maintainer doesn't updated it. I tried to build it but failed with error:
==> Validating source files with md5sums...
master ... Passed
==> Extracting Sources...
-> Extracting master with bsdtar
==> Starting build()...
Generating configuration files for gtkparasite, please wait...
libtoolize --copy --force
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: You should add the contents of the following files to `aclocal.m4':
libtoolize: `/usr/share/aclocal/libtool.m4'
libtoolize: `/usr/share/aclocal/ltoptions.m4'
libtoolize: `/usr/share/aclocal/ltversion.m4'
libtoolize: `/usr/share/aclocal/ltsugar.m4'
libtoolize: `/usr/share/aclocal/lt~obsolete.m4'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
aclocal
configure.ac:38: error: 'AM_CONFIG_HEADER': this macro is obsolete.
You should use the 'AC_CONFIG_HEADERS' macro instead.
/usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded from...
configure.ac:38: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
autoheader
autoheader: error: AC_CONFIG_HEADERS not found in configure.ac
automake --add-missing
configure.ac: error: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE,
configure.ac: that aclocal.m4 is present in the top-level directory,
configure.ac: and that aclocal.m4 was recently regenerated (using aclocal)
configure.ac:47: installing './install-sh'
src/Makefile.am:40: error: HAVE_X11 does not appear in AM_CONDITIONAL
src/Makefile.am:34: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
src/Makefile.am:31: error: Libtool library used but 'LIBTOOL' is undefined
src/Makefile.am:31: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
src/Makefile.am:31: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
src/Makefile.am:31: If 'LT_INIT' is in 'configure.ac', make sure
src/Makefile.am:31: its definition is in aclocal's search path.
src/Makefile.am: installing './depcomp'
/usr/share/automake-1.13/am/depend2.am: error: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.13/am/depend2.am: The usual way to define 'am__fastdepCC' is to add 'AC_PROG_CC'
/usr/share/automake-1.13/am/depend2.am: to 'configure.ac' and run 'aclocal' and 'autoconf' again
/usr/share/automake-1.13/am/depend2.am: error: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.13/am/depend2.am: The usual way to define 'AMDEP' is to add one of the compiler tests
/usr/share/automake-1.13/am/depend2.am: AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC, AC_PROG_OBJCXX,
/usr/share/automake-1.13/am/depend2.am: AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/share/automake-1.13/am/depend2.am: to 'configure.ac' and run 'aclocal' and 'autoconf' again
autoconf
configure.ac:20: error: possibly undefined macro: AC_SUBST
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:32: error: possibly undefined macro: AM_INIT_AUTOMAKE
configure.ac:38: error: possibly undefined macro: AM_CONFIG_HEADER
configure.ac:48: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
configure.ac:49: error: possibly undefined macro: AM_PROG_LIBTOOL
configure.ac:79: error: possibly undefined macro: AM_CONDITIONAL
configure.ac:81: error: possibly undefined macro: AM_PATH_PYTHON
configure.ac:82: error: possibly undefined macro: AC_PATH_PROG
configure.ac:108: error: possibly undefined macro: AC_DEFINE
I am going to run ./configure with no arguments - if you wish
to pass any to it, please specify them on the ./autogen.sh command line.
If you do not wish to run ./configure, press Ctrl-C now.
configure: error: cannot find sources (config.h.in) in . or ..
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build gtkparasite.
==> Restart building gtkparasite ? [y/N]
Could somebody to tell me what is wrong with this PKGBUILD?
Offline
The error tells you exactly what is wrong:
configure.ac:38: error: 'AM_CONFIG_HEADER': this macro is obsolete.
You should use the 'AC_CONFIG_HEADERS' macro instead.
The program's autotools script is using a macro that was depreciated in 2002 and removed from the latest version of automake.
As for what's wrong with the PKGBUILD, being a duplicate of gtkparasite-git would be the major one. Really, it's still a git PKGBUILD even if it's pulling a master tarball from github. I'll update gtkparasite-git.
Last edited by Scimmia (2013-03-24 07:09:23)
Offline
Offline
I have problem with this PKGBUILD again. It seams it build package with gtk3 support although there is no "--with-gtk=3.0" in PKGBUILD. Gtkparasite module is in /usr/lib/gtk-3.0/modules. When I run it with gtk2 application I get error:
Gtk-Message: Failed to load module "gtkparasite"
When I copy module to /usr/lib/gtk-2.0/modules I get error:
Gtk-WARNING **: GTK+ module /usr/lib/gtk-2.0/modules/libgtkparasite.so cannot be loaded.
GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Gtk-Message: Failed to load module "gtkparasite"
But it working well with gtk3 applications.
Offline
Looks like commit 118259743d308c6848e23bdbd8102974d5d85177 dropped support for GTK2 completely, as well as some other changes that require PKGBUILD changes. Contact the current maintainer.
Offline
Offline