This page lists the most common issues and errors (and their solutions) that you might encounter while trying to compile GNOME using JHBuild.

/!\ This page is not a bug tracker. If you run into a problem not listed here, please file a bug.
When entering a new problem, please enter it above the others, and follow the format of the JhbuildIssues/JhbuildIssueTemplate for new problems/modules.

Error - No package 'something' found

Stage: Configure

checking for something... configure: error: Package requirements (foo-2.0 >= 002) were not met:
No package 'foo-2.0' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Cause:

The module's configure.ac file uses pkg-config to check for the availability of some package (e.g. foo-2.0). This error is raised when pkg-config cannot find the missing package's corresponding .pc file (e.g. foo-2.0.pc ).

Solution:

1. Find which package provides the missing .pc file. If the missing package is foo-2.0, find and install the package that includes the file foo-2.0.pc:

  • For Debian-based systems (incl. Ubuntu):
    apt-file search "foo-2.0.pc"
    For Fedora-based systems:
    yum provides "*/foo-2.0.pc"
    Install the listed package and try configuring the module again.

2. Make sure the PKG_CONFIG_PATH environment variable is set correctly.

  • Find all the locations where .pc files are stored:

    for f in $(locate *.pc); do dirname $f; done | uniq

    For each location add it to your jhbuildrc like so:

    addpath('PKG_CONFIG_PATH', '/directory/to/pc/files')
    addpath('PKG_CONFIG_PATH', '/other/pc/files/live/here')

Module fails to build although it did in the past

If you have successfully built in the past, but it suddenly stops working, try:

jhbuild build -afc <module>

which will force it to rebuild everything from scratch.

Error - macro `XXXX' not found in library

Stage: configure

aclocal: configure.in: 153: macro `XXXX' not found in library

Cause: aclocal is not able to find a particular macro in the standard search path. See the .m4 files in this directory to get an idea.

The path to the directory containing an m4 macro needs to be specified by setting the environment variable ACLOCAL_FLAGS.

Solution:

You need to export the enviromment variable ACLOCAL_FLAGS to point to the directory with the .m4 file containing this macro as follows:

Add the path to the macro file to ACLOCAL_FLAGS in your .jhbuildrc file. For example if the macro is in the /usr/share/aclocal directory, you should then add:

addpath('ACLOCAL_FLAGS', '/usr/share/aclocal')

Error - GIT_DISCOVERY_ACROSS_FILESYSTEM not set

Stage: Checking out stage.

fatal: Not a git repository (or any parent up to mount parent /Volumes)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set)

Problem: Not sure, but seems like a directory was created for checking out a clone, and then the cloning process did not start for some reason.

Solution: Delete the empty directory created by jhbuild in the checkoutroot.

Error: macro APPSTREAM_XML is not defined

Solution:

Install the corresponding development package. On Fedora, this would be libappstream-glib-devel.

Module-Specific Issues

  1. Projects/Jhbuild/Issues/Bluez
  2. Projects/Jhbuild/Issues/GObjectIntrospection
  3. Projects/Jhbuild/Issues/JhbuildIssueTemplate
  4. Projects/Jhbuild/Issues/NetworkManager
  5. Projects/Jhbuild/Issues/cairo
  6. Projects/Jhbuild/Issues/dbus
  7. Projects/Jhbuild/Issues/dbus-glib
  8. Projects/Jhbuild/Issues/ekiga
  9. Projects/Jhbuild/Issues/evolution
  10. Projects/Jhbuild/Issues/evolution-exchange
  11. Projects/Jhbuild/Issues/fontconfig
  12. Projects/Jhbuild/Issues/glib
  13. Projects/Jhbuild/Issues/gnome-applets
  14. Projects/Jhbuild/Issues/gnome-desktop
  15. Projects/Jhbuild/Issues/gnome-doc-utils
  16. Projects/Jhbuild/Issues/gnome-icon-theme
  17. Projects/Jhbuild/Issues/gnome-keyring
  18. Projects/Jhbuild/Issues/gnome-music
  19. Projects/Jhbuild/Issues/gnome-power-manager
  20. Projects/Jhbuild/Issues/gnome-screensaver
  21. Projects/Jhbuild/Issues/gnome-shell
  22. Projects/Jhbuild/Issues/gnome-terminal
  23. Projects/Jhbuild/Issues/gnome-utils
  24. Projects/Jhbuild/Issues/gnutls
  25. Projects/Jhbuild/Issues/gtk+
  26. Projects/Jhbuild/Issues/gtk-doc
  27. Projects/Jhbuild/Issues/gtk-vnc
  28. Projects/Jhbuild/Issues/gtkhtml
  29. Projects/Jhbuild/Issues/icon-naming-utils
  30. Projects/Jhbuild/Issues/iso-codes
  31. Projects/Jhbuild/Issues/jhbuild
  32. Projects/Jhbuild/Issues/libcanberra
  33. Projects/Jhbuild/Issues/libgda
  34. Projects/Jhbuild/Issues/libproxy
  35. Projects/Jhbuild/Issues/libtool
  36. Projects/Jhbuild/Issues/libxklavier
  37. Projects/Jhbuild/Issues/mozilla
  38. Projects/Jhbuild/Issues/mutter
  39. Projects/Jhbuild/Issues/nautilus
  40. Projects/Jhbuild/Issues/nss
  41. Projects/Jhbuild/Issues/pango
  42. Projects/Jhbuild/Issues/perl-net-dbus
  43. Projects/Jhbuild/Issues/poppler
  44. Projects/Jhbuild/Issues/pycairo
  45. Projects/Jhbuild/Issues/rarian
  46. Projects/Jhbuild/Issues/sabayon
  47. Projects/Jhbuild/Issues/startup-notification
  48. Projects/Jhbuild/Issues/waf


Projects/Jhbuild/Issues (last edited 2016-11-25 15:53:25 by AndreKlapper)