Hacking:Problems and solutions
This page describes problems that hamper the developers work and their solution. It's a knowledge base for developers. Feel free to add your own findings and don't be shy. It makes the work easier for all of us.
Problem: Unit tests pass on one machine, but not on another - samely configured - machine. In this particular case the tests RGBA->HSLA and RGBA->HSVA passed on an amd64 platform, but failed on an i386 platform. Content of file tests/testsuite.log on the i386 machine:
babl 0.1.11: tests/test-suite.log
.. contents:: :depth: 2
rgba to hsla failed #0 got 0.166667 expected 0.000000
rgba to hsla failed #1 got 0.666667 expected 0.000000
rgba to hsva failed #0 got 0.166667 expected 0.000000
rgba to hsva failed #1 got 0.166667 expected 0.000000
Cause: The tested code doesn't take into account that strict equality comparisons (==) can lead to different results on different platforms.
Solution: The code must take this fact into account.
Make sure to have defined EPSILON first:
#define EPSILON 1.0e-10
Here are some examples:
See also Bugfix for RGBA->HSLA,HSVA conversions.
If you're unsure, ask Daniel_S, Massimo, Mitch or Téo Mazars.
Problem: Building GEGL master stops with failing assertions related to GLib. The stopped build can't be aborted with Ctrl+C. to enter new commands in that terminal session.
The following messages are shown at the screen:
CC gegl-matrix.lo CCLD libgegl-0.3.la GISCAN Gegl-0.3.gir GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init() GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion `G_TYPE_IS_INTERFACE (interface_type)' failed GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init() GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init() GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
Cause: You have an old GLib version in your prefix. (Don't be fooled by just looking at the libglib version in your package manager!)
- Close this terminal session and open a new one.
- Remove that old GLib version from your prefix and rebuild GEGL from scratch.
Problem: Building GIMP fails for instance in libgimpcolor with a message telling you, that some files in $ANOTHER_PREFIX/lib are missing and thus building libgimpcolor.la (or another *.la file) failed.
Cause: You switched over to another prefix. You already cleaned or removed that old prefix, but in your new prefix are some files referring to other files in that old prefix. In other words - there's an evil mixture of your new prefix and some old prefix zombies and libtool trips you up ;-)
Solution: Finding out the actually errorneous parts can take you hours, so it's better to make a clean sweep:
- Check your environment variables, especially the build environment variables. If they point to that old prefix, change them to point to the new prefix.
- Drop the contents of your new prefix.
- Rebuild from scratch. For BABL, GEGL and GIMP (and other libraries, if you use them):
- Change to their directory.
- Save your work (backup your working files or do git stash).
- Run git clean -xdf or drop the contents of the workspace except the .git folder or the source tarball.
- Run ./configure --prefix=$PREFIX (Git users: ./autogen.sh --prefix=$PREFIX).
- Run make && make install.
Some more information on building can be found at the building tutorials.
Problem: After checking out a particular branch, Git tells me, that I'm a few commits behind,
for example: 'Your branch is behind 'origin/gimp-2-8' by 2 commits, and can be fast-forwarded.'
Cause: On git pull Git didn't update the HEAD on your local branch for whatever reason.
Solution: Try git pull origin to update your local branch.
Problem: I'm translating on the current production branch of GIMP (2-8 etc.) and on master. I'd like to cherry-pick my changes from the production branch to the master branch. But I get lots of merge conflicts and changes I never introduced.
Cause: Cherry-picking translations from the production branch into the master branch doesn't work.
Solution: Commit your translation updates directly into the master branch or try to merge your translation branch into the master branch.
Template for investigated solutions
Template for workarounds
Anyway, this is just a workaround. If you know the cause and a proper solution, feel free to edit this posting.