After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 654231 - gtkmm-2.24.1 always needs mm-common at build time
gtkmm-2.24.1 always needs mm-common at build time
Status: RESOLVED FIXED
Product: gtkmm
Classification: Bindings
Component: build
2.24.x
Other Linux
: Normal normal
: ---
Assigned To: gtkmm-forge
gtkmm-forge
: 648742 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-07-08 10:53 UTC by Pacho Ramos
Modified: 2011-07-19 09:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
config.log (34.48 KB, text/plain)
2011-07-08 10:53 UTC, Pacho Ramos 		Details

Description Pacho Ramos 2011-07-08 10:53:23 UTC 
Created attachment 191512 [details]
config.log

2.24.0 only needed it for building documentation but, now, it's always required:

checking for GDKMM... yes
checking for GTKMM... yes
checking for GTHREAD_CFLAGS... -pthread  
checking for GTHREAD_LIBS... -pthread -lgthread-2.0 -lrt -lglib-2.0  
checking for GMMPROC_DIR... /usr/lib64/glibmm-2.4/proc
checking for GMMPROC_EXTRA_M4_DIR... /usr/lib64/pangomm-1.4/proc/m4 /usr/lib64/atkmm-1.6/proc/m4
configure: Deprecated API will be built, for backwards-compatibility.
checking location of documentation utilities... configure: error: not found
The required module mm-common-util could not be found on this system.  If you
are running a binary distribution and the mm-common package is installed,
make sure that any separate development package for mm-common is installed
as well.  If you built mm-common yourself, it may be necessary to adjust
the PKG_CONFIG_PATH environment variable for pkg-config to find it.

But I don't understand why it checks for documentation utilities even passing "--disable-documentation", is this normal?

Thanks for your help
Comment 1 Murray Cumming 2011-07-08 10:56:28 UTC 
Sorry. I think I have a fix for this, as in gtkmm 3, but I'm just checking it before doing a new release. Thanks.
Comment 2 Pacho Ramos 2011-07-08 11:18:34 UTC 
Will it also make it to NOT depend on mm-common even building documentation? With 2.24.0 we needed it in that case, but looks like not many other packages behave in the same way :-/

Thanks a lot :)
Comment 3 Murray Cumming 2011-07-08 11:24:35 UTC 
No, it should not need mm-common ever when building from a tarball.
Comment 4 Murray Cumming 2011-07-08 11:46:36 UTC 
This commit should fix it:
http://git.gnome.org/browse/gtkmm/commit/?h=gtkmm-2-24&id=917dada8c3603daf98e79d035b90a566bd4f057d

I have just released gtkmm 2.24.2, so please let me know if it didn't fix it properly.
Comment 5 Krzesimir Nowak 2011-07-08 11:49:50 UTC 
Probably for sake of completness MM_PREREQ should have 0.9.5 as a parameter - this is the version of mm-common doing copying docutils to directory from MM_CONFIG_DOCTOOL_DIR.
Comment 6 Murray Cumming 2011-07-08 20:24:04 UTC 
Yes, thanks. Done.
Comment 7 Murray Cumming 2011-07-19 09:53:37 UTC 
*** Bug 648742 has been marked as a duplicate of this bug. ***