[3093] in Kerberos-V5-bugs
krb5-admin/734: include files required by kadm5 applications not installed
daemon@ATHENA.MIT.EDU (roma@uiuc.edu)
Thu Jul 22 15:52:11 1999
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: krb5-unassigned@RT-11.MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU, roma@uiuc.edu
Message-Id: <199907221951.OAA17290@lutefisk.cso.uiuc.edu>
Date: Thu, 22 Jul 1999 14:51:24 -0500
From: roma@uiuc.edu
Reply-To: roma@uiuc.edu
To: krb5-bugs@MIT.EDU
>Number: 734
>Category: krb5-admin
>Synopsis: can't find kadm5 include files in any installed directory
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: krb5-unassigned
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Thu Jul 22 15:52:01 EDT 1999
>Last-Modified:
>Originator: Jon Roma
>Organization:
University of Illinois at Urbana-Champaign
>Release: krb5-1.0.6
>Environment:
System: AIX lutefisk 2 4 000006364900
>Description:
We have several locally-developed applications that need to interface with
the Kerberos administration system using the KADM5 application programming
interface.
The document titled "Kerberos Administration System -- KADM5 API Functional
Specifications" by Barry Jaspan states in section 4 that the data
structures needed for this API are defined in the include file
kadm5/admin.h .
A compilation of our locally-developed applications fails due to the
inability to find the kadm5/admin.h include file as well as several other
include files on which this file depends.
This failure occurs because several include files required for the successful
compilation of a utility using the KADM5 API are never installed by the
'make install' Makefile target; as such, they do not reside in a directory
such as /usr/local/include where the compiler/preprocessor will find them.
Compilation will succeed if the following additions are made to the
preprocessor directives used in compile:
-I$KRBROOT/src/include
-I$KRBROOT/src/include/krb5
where $KRBROOT denotes the full path of the root of the Kerberos source
tree.
In addition, the include files affected are removed by a 'make clean'.
This requires retaining the built source tree, instead of the preferred
and more conventional approach of installing include files into an
install directory such as /usr/local/include .
Our workaround of adding these preprocessor directives has allowed us to
successfully build the needed applications, but this workaround is not
desirable over the long term from a software management point of view;
I'm assuming that it is simply an inadvertant omission that the include
files needed for a KADM5 API client are not installed.
>How-To-Repeat:
>Fix:
See above for temporary workaround.
>Audit-Trail:
>Unformatted:
