Click failing to build in Archlinux due to packagekit-plugin package not found
When I attempt to build click 0.4.45.
configure: error: Package requirements (
gio-2.0
glib-2.0 >= 2.34
gobject-2.0 >= 2.28
json-glib-1.0 >= 0.10
packagekit-plugin >= 0.8.10
) were not met:
No package 'packagekit-plugin' found
I have been looking for packagekit-plugin for quite some time, but I cannot seem to find a package with that name on Launchpad or when I do a Google search for it. Is there another package that provides this?
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Ubuntu click Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
![]() |
#1 |
1. This is a question area for Ubuntu, We cannot support Archlinux here.
2. As far as I can see, on Ubuntu the click package does NOT show a dependency on packagekit-plugin.
3. in the build log of the Ubuntu packages I see some special flags and options like
-Npackagekit-
Maybe that is something what you also have to add
Revision history for this message
![]() |
#2 |
I am trying to build Unity for Archlinux, and the Yakkety version of indicator-datetime requires ubuntu-
https:/
I have built most of the packages off the master branch, owned by Chenxiaolong.
I looked at the dependency list, and it does not show a dependency on packagekit-plugin. I have used the special option --disable-
Revision history for this message
![]() |
#3 |
What is the error that yo get with --disable-
Revision history for this message
![]() |
#4 |
Sorry it took me so long to reply. Here's the entire output with --disable-
==> Making package: click 0.4.45.
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found click_0.
-> Found 0001-Fix-
==> Validating source files with sha512sums...
click_
0001-
==> Extracting sources...
-> Extracting click_0.
==> Starting prepare()...
patching file configure.ac
==> Removing existing $pkgdir/ directory...
==> Starting build()...
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-
libtoolize: putting macros in AC_CONFIG_
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:9: installing 'build-aux/compile'
configure.ac:7: installing 'build-aux/missing'
lib/click/
autoreconf: Leaving directory `.'
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking build system type... x86_64-
checking host system type... x86_64-
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-
checking how to convert x86_64-
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether NLS is requested... yes
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^(.*)\${ <-- HERE ?([A-Z_]+)}?(.*)$/ at /usr/bin/
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ?AC_PACKAGE_NAME}?/ at /usr/bin/
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ?PACKAGE}?/ at /usr/bin/
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ?AC_PACKAGE_
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ?VERSION}?/ at /usr/bin/
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ?AC_PACKAGE_NAME}?/ at /usr/bin/
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ?PACKAGE}?/ at /usr/bin/
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ?AC_PACKAGE_
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ?VERSION}?/ at /usr/bin/
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ?\w+}?/ at /usr/bin/
checking for intltool-update... /usr/bin/
checking for intltool-merge... /usr/bin/
checking for intltool-extract... /usr/bin/
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.24.0
checking for XML::Parser... ok
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking for library containing dlopen... -ldl
checking for Perl vendor library directory... /usr/share/
checking for valac... /usr/bin/valac
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBCLICK... yes
checking for gobject-
checking for systemd system unit directory... /usr/lib/
checking for systemd user unit directory... /usr/lib/
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating click/Makefile
config.status: creating click/tests/
config.status: creating click/tests/
config.status: creating conf/Makefile
config.status: creating conf/databases/
config.status: creating conf/databases/
config.status: creating debhelper/Makefile
config.status: creating init/Makefile
config.status: creating init/systemd/
config.status: creating init/upstart/
config.status: creating lib/Makefile
config.status: creating lib/click/Makefile
config.status: creating lib/click/
config.status: creating pk-plugin/Makefile
config.status: error: cannot find input file: `po/Makefile.in.in'
==> ERROR: A failure occurred in build().
Aborting...
Here's my PKGBUILD:
# Maintainer: Michael Healy <email address hidden>
# vercheck-pkgbuild: auto
# vercheck-ubuntu: name=${pkgname}, repo=yakkety
# vercheck-launchpad: name=${pkgname}
pkgname=click
_actual_
_extra_
pkgver=
pkgrel=1
pkgdesc=
arch=(i686 x86_64)
url="https:/
license=(GPL)
depends=()
groups=(unity)
source=("https:/
0001-Fix-
sha512sums=
prepare() {
patch -p1 -i ../0001-
}
build() {
autoreconf -vfi
./configure --prefix=/usr --libexecdir=
make
}
package() {
make DESTDIR=
}
Revision history for this message
![]() |
#5 |
I checked in the po folder in the source files, and there is a Makefile.in, but not a Makefile.in.in. Thanks for your reply and your help!
Revision history for this message
![]() |
#6 |
Is there anyone in the Launchpad group that supports building Unity for other distros? It would be great to have a resource I could turn to for help building Unity.
Revision history for this message
![]() |
#7 |
1. On Launchpad there are two areas, one for the click project as such, and one for click on Ubuntu. The only problem is that the click project informs to file bug in the area of click for Ubuntu. So I assume there is no better address for your questions than this one.
You might consider contacting someone one the "click hackers" group https:/
They are registered as the maintainers for the click project
2. A web search for Makefile.in.in brings up https:/
Maybe this helps (try running intltoolize between autoreconf and configure).
Can you help with this problem?
Provide an answer of your own, or ask Michael Healy for more information if necessary.