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 622029 - gmime apparently depends on gtk-sharp but that's not modelled
gmime apparently depends on gtk-sharp but that's not modelled
Product: jhbuild
Classification: Infrastructure
Component: module sets
Other Linux
: Normal normal
: ---
Assigned To: Jhbuild maintainers
Jhbuild QA
Depends on:
Reported: 2010-06-18 20:25 UTC by Tobias Mueller
Modified: 2010-06-19 08:29 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Tobias Mueller 2010-06-18 20:25:58 UTC
I am using the gnome-3.0 moduleset.

muelli@bigbox ~/svn/gnome2/gtk+ $ jhbuild list gmime
muelli@bigbox ~/svn/gnome2/gtk+ $ 

checking whether /usr/bin/mcs is GNU Mono... yes
checking for gacutil... /usr/bin/gacutil
checking for GTK_SHARP... configure: error: Package requirements (gtk-sharp-2.0 >= 2.4.0) were not met:

No package 'gtk-sharp-2.0' 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 GTK_SHARP_CFLAGS
and GTK_SHARP_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

*** Error during phase configure of gmime: ########## Error running ./configure --prefix /opt/gnome2 --libdir '/opt/gnome2/lib64'  --disable-static  --disable-scrollkeeper --disable-gtk-doc --disable-docs  *** [48/101]

Right now, gmime has "gtk-sharp" as "after" and not as real dependency.

I could build gmime after I have manually jhbuilded gtk-sharp.
Comment 1 Craig Keogh 2010-06-19 06:02:28 UTC
Thank you for reporting the bug.

If gtk-sharp is in your 'modules', gmime will build after gtk-sharp. gtk-sharp is in the default 'meta-gnome-desktop'.

If you don't have mono (mcs) installed, gmime will build without gtk-sharp. I don't think it is a good idea to add gtk-sharp as a dependency to gmime as it force mono on users.

I suggest either:
1. Add to ~/.jhbuildrc:

module_autogenargs['gmime'] = autogenargs + \
	' --disable-mono'

2. Uninstall mono.

3. Build with a 'modules' that includes gtk-sharp.

4. Build gtk-sharp manually.

I don't see how JHBuild can solve this problem.
Ideally, gmime should build the mono bindings if and only if mono AND gtk-sharp are found.
Comment 2 Tobias Mueller 2010-06-19 08:29:17 UTC
Hm. Well.

1) seems easy

2) is not possible:
checking whether /usr/bin/mcs is GNU Mono... yes

so it picked up the system's mono (which I think is fair enough).

3) yeah. Although jhbuild apparently doesn't respect the modified .modules any more ;-) I keeps bugging me to add use_local = True in my jhbuildrc but I wonder whether I lose any functionality then and which.

4) I've just done that

You are right, I don't think JHBuild at this stage can solve that. And I wouldn't argue that we should pimp JHBuild so that it is able to solve that problem. It's just very annoying. Maybe kind of an online help would be nice. I.e. another option "Suggest Fixes" that pulls stuff from l.g.o (or so). It would then simply show these alternatives. Implementation could be very easy, i.e. just realise that step "configure" of the package "mono" failed and then print a string. But I do realise that tracking all the issues might be a bad thing because we probably don't have the manpower to keep everything up to date.