[1329] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: sub-packages of krb5 for autoconf purposes

daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Mon Jun 17 23:57:11 1996

Date: Mon, 17 Jun 1996 23:56:56 -0400
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Ken Raeburn <raeburn@cygnus.com>
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>, Tom Yu <tlyu@MIT.EDU>, krbdev@MIT.EDU
In-Reply-To: Ken Raeburn's message of 14 Jun 1996 22:15:28 -0700,
	<tx1ennh1wcv.fsf@cygnus.com>

   From: Ken Raeburn <raeburn@cygnus.com>
   Date: 14 Jun 1996 22:15:28 -0700

   In order to avoid linking programs against inappropriate libraries,
   we'd have to set a bunch of different make variables, and pick and
   choose those we want for each application (e.g., AIX "-ls" would only
   be needed in one or two places).  Similarly for any uses of
   AC_REPLACE_FUNCS and @LIBOBJS@.  Which means porting to a new system
   is more likely to require changing Makefile.in as well as configure.in
   if some needed function is off in some library on the new system.

   The usual autoconf way is to build up LIBS and substitute for @LIBS@
   in Makefile.in, but common autoconf usage has never stopped the
   Kerberos team from doing things differently before... :-)

Ken,
	Can you explain what you mean by this in more detail?  If I
understand the general gist of what you're saying, it's that the
Autoconf Way is that you *should* have a separate configure file any
time you might have a different set of AC_REPLACE_FUNCS, which is likely
to be in many different directories.

						- Ted
home help back first fref pref prev next nref lref last post