GNOME Bugzilla – Bug 622031
Can't just skip a module when it fails
Last modified: 2010-09-29 07:19:55 UTC
I just want to skip a module when it fails, i.e.: checking for UUID... configure: error: Package requirements (uuid) were not met: No package 'uuid' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables UUID_CFLAGS and UUID_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. *** Error during phase configure of NetworkManager: ########## Error running ./autogen.sh --prefix /opt/gnome2 --libdir '/opt/gnome2/lib64' --disable-static --enable-maintainer-mode --disable-scrollkeeper --disable-gtk-doc --disable-docs *** [52/101] [1] Rerun phase configure [2] Ignore error and continue to configure [3] Give up on module [4] Start shell [5] Reload configuration [6] Go to phase "wipe directory and start over" [7] Go to phase "clean" [8] Go to phase "distclean" choice: I don't want to install libuuid-devel but I'm installing notwork-manager-devel on my system just right now. So I don't care about NetworkManager being built o not. Unfortunately, jhbuild doesn't offer me to ignore the error and continue with the next module. Note that "Ignore error and continue to configure" is not what I want. Not only because it doesn't work (I'm in the configure step right now anyway), but also because it installs files to my prefix if I was at compile stage (because it'd offer "ignore and go to install"). That is obviously harmful.
Does '[3] Give up on module' do what you want?
Nope. Sorry for not being clear on this. The [3] makes jhbuild remember that the module failed and it then doesn't build out the packets that depend on the failed module.
If you don't want this behaviour, you have to use -N, --no-poison don't poison modules on failure (or set nopoison in your .jhbuildrc). Or you could add NetworkManager to the list of modules to skip.
Are the solutions presented satisfactory? If not, reopen this bug and we can discuss further.