>Number:         11488
>Category:       lib
>Synopsis:       gssapi.h includes header from wrong directory
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    lib-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 14 00:55:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Marc Horowitz
>Release:        -current as of 11/10, but also affects 1.5_BETA2
>Organization:
>Environment:
	
System: NetBSD marble-madness.toybox.cambridge.ma.us 1.5K NetBSD 1.5K (MARC) #1: Sun Nov 12 02:22:29 EST 2000 marc@marble-madness.toybox.cambridge.ma.us:/u2/netbsd/src/sys/arch/i386/compile/MARC i386
Architecture: i386
Machine: i386
>Description:

Building against gssapi will never work.  /usr/include/gssapi/gssapi.h
does:

#include <krb5-types.h>

This is fine with a native heimdal install, where krb5-types.h is
installed in ${prefix}/include.  But NetBSD installs it as
/usr/include/krb5/krb5-types.h.  In my experience, no build system
uses -I/usr/include/krb5 or anything similar, so no program which
tried to build gssapi, such as cyrus libsasl, will build without
hacking the build system.

There's a separate inconsistency in that MIT krb5 and Heimdal install
their gssapi headers in different places, but that should presumably
get fixed by the Heimdal people.

compile_et has a similar problem, in that the header files it
generates include <com_right.h>, which NetBSD installs in
/usr/include/krb5.

>How-To-Repeat:

Try to build cyrus libsasl or any other gssapi consumer, and watch it
fail.

>Fix:

The fix is to either change the installed headers to look in the right
place for included headers, or to install the headers in the same
place that Heimdal does.

>Release-Note:
>Audit-Trail:
>Unformatted:
 bcc; marc@netbsd.org
 Reply-To: marc@netbsd.org
 X-send-pr-version: 3.95