Received: from pch.mit.edu (PCH.MIT.EDU [18.7.21.90]) by krbdev.mit.edu (8.9.3p2) with ESMTP id NAA03797; Sun, 13 Mar 2005 13:13:29 -0500 (EST) Received: from pch.mit.edu (pch.mit.edu [127.0.0.1]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id j2DICxh7032588 for ; Sun, 13 Mar 2005 13:12:59 -0500 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id j2DFC3h7023308 for ; Sun, 13 Mar 2005 10:12:03 -0500 Received: from moab.few.eur.nl (moab.few.eur.nl [130.115.112.12]) j2DFBtI1020139 for ; Sun, 13 Mar 2005 10:11:56 -0500 (EST) Received: from euler.few.eur.nl (euler.few.eur.nl [130.115.112.29]) by moab.few.eur.nl (8.13.2/8.13.2) with SMTP id j2DFBq4T025188 for ; Sun, 13 Mar 2005 16:11:52 +0100 (MET) Date: Sun, 13 Mar 2005 16:11:52 +0100 (MET) From: Paul Kranenburg To: krb5-bugs@mit.edu Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new X-Spam-Score: -4.9 X-Spam-Flag: NO X-Scanned-BY: MIMEDefang 2.42 X-Mailman-Approved-At: Sun, 13 Mar 2005 13:12:57 -0500 Subject: gssapi.h pollution X-Beenthere: krb5-bugs-incoming@mailman.mit.edu X-Mailman-Version: 2.1 Precedence: list Sender: krb5-bugs-incoming-bounces@PCH.mit.edu Errors-To: krb5-bugs-incoming-bounces@PCH.mit.edu X-RT-Original-Encoding: us-ascii Content-Length: 1090 I recently built and installed krb5 v1.4, which went smoothly, thanks for that. Then I noticed that some other software package would not build any more. It took me a while to figure out this was due to the rather anti-social contents at the top of the installed /include/gssapi/gssapi.h header. Here we find a bunch of non-gss related symbols intruding the consumer's namespace. In my case, it turned out to be HAVE_REGEX that caused the kerberized application (samba 3.0.x) to gain functionality I did not intend it to have. I'm not sure why these configuration-related symbols were added to gssapi.h (and, I notice, krb5.h as well), but I would suggest finding another way than polluting the application's namespace in this manner to achieve whatever problem it was intended to alleviate. E.g. have the library implementation pull in the required configuration defines explicitly, or at least brace the offending section with something like #ifdef __GSSAPI_MIT_IMPLEMENTAION #endif Best regards, -pk ---- Paul Kranenburg Erasmus University Rotterdam