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 172175 - gmime configure false positive for Mono
gmime configure false positive for Mono
Status: RESOLVED FIXED
Product: gmime
Classification: Other
Component: general
unspecified
Other OSF/1
: Normal minor
: ---
Assigned To: Jeffrey Stedfast
Jeffrey Stedfast
Depends on:
Blocks:
 
 
Reported: 2005-03-30 22:54 UTC by Tim Mooney
Modified: 2005-04-14 19:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
don't assume mcs is GNU Mono -- run it and see if it acts like mono (847 bytes, patch)
2005-03-30 22:55 UTC, Tim Mooney 		none Details | Review

Description Tim Mooney 2005-03-30 22:54:41 UTC 
Version details: 2.1.14

configure gmime-2.1.14 on a box that has a command named `mcs' that *isn't* GNU
Mono.  One example is Tru64 UNIX, where mcs is part of the development
toolchain, and is for manipulating the comment section (mcs) of an eCOFF-format
object file.  There are probably other examples.

configure detects /usr/bin/mcs, and assumes its mono, and then bails when it
can't find additional components it expects.

My fix (attached) is to try run $CSC --version, and if that succeeds, then we
assume it's Mono.  An even better test would be to parse the output of --version
and look for "GNU Mono".  If you would like I can add that, but this was
sufficient for my needs.
Comment 1 Tim Mooney 2005-03-30 22:55:37 UTC 
Created attachment 39465 [details] [review]
don't assume mcs is GNU Mono -- run it and see if it acts like mono
Comment 2 Jeffrey Stedfast 2005-04-14 19:51:18 UTC 
patch applied to CVS