[2457] in Kerberos_V5_Development
Re: Binary Support for SCO OpenServer
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Tue Jul 29 18:27:12 1997
Date: Tue, 29 Jul 1997 18:23:38 -0400
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Shane Gibson <shaneg@sco.COM>
Cc: krbdev@MIT.EDU
In-Reply-To: Shane Gibson's message of Tue, 29 Jul 1997 08:18:00 -0700,
<33DE09A8.41C6@sco.com>
Date: Tue, 29 Jul 1997 08:18:00 -0700
From: Shane Gibson <shaneg@sco.COM>
I just visited your Kerberos v5 Website. I am very impressed
with the amount of work that appears to have gone into all of
this.
Thanks!!
I noticed that you folks maintain binary distributions of various
flavors of Unix. I also assume that by so doing, your insuring
the portability in general, and specifically to those OS's. If
you could obtain a copy of SCO OpenServer 5.0.4, would you attempt
to provide binaries and support?
Most of our various binary distributions are maintained by volunteers.
There is a small set of core platforms which we maintain locally at MIT
--- they consist of the primary development platforms of our developers,
and include Solaris, Linux, NetBSD, and SGI. The other platforms are
maintained by volunteers.
If someone at SCO is willing to try compiling Kerberos V5, and
sending back any porting patches that they needed to make, we will
accept those changes. If they can follow the procedure required for
making a binary distributions, we'll put the binary distribution on our
web site.
Do you think someone at SCO would be willing to do that work?
- Ted
P.S. The alternative is that you could try loaning me the disk drive
and the computer so that I'd actually have a place to install
OpenServer, but to be honest I'm so busy these days that I wouldn't be
able to work on it for at least a few weeks, if not a month or two.
P.P.S. Here's the procedure we sent out to our volunteers...
----------------------------------------------------------------------
Instructions for creating a binary distribution of Kerberos 5 1.0 pl1
----------------------------------------------------------------------
o Begin with the krb5-1.0pl1.src.tar.gz, krb5-1.0pl1.crypto.tar.gz, and
krb5-1.0pl1.doc.tar.gz source tarballs, and unpack them. Do NOT use any
existing CVS working directory, however carefully patched.
o Read doc/krb5-install.info or doc/install-guide.ps for full details
on building krb5. When you get to running configure, use the options
% configure --with-ccopts=-O --enable-shared
If the Kerberos V5 distribution does not support shared libraries on
that platform, configure will print an error message and exit; re-run
it without --enable-shared. Run make to build the distribution. If
you receive any errors, notify krbdev@mit.edu immediately.
If you have TCL installed, you can add configure option --with-tcl.
For example, "--with-tcl=/mit/gnu". This assumes that
/mit/gnu/include and /mit/gnu/lib contain the TCL header files and
libraries. This doesn't change the compiled binaries, but allows the
full test suite to run, if you also have dejagnu and perl installed.
N.B. It's often helpful to build in a separate build directory,
assuming that your make supports VPATH. You can do this by creating a
build directory, and then running configure from the build directory
(see the krb5 installation notes for more details):
% mkdir build
% cd build
% ../src/configure --with-ccopts=-O --enable-shared
N.B. The build directory should really be on a local filesystem.
Unfortunately a number of remote filesystes, on on some OS's, may not
fully support full POSIX semantics, including locking. This may cause
some of the test suites to fail.
o Actually do the build:
% make >& MAKELOG
o Run the automated tests:
% make -k check |& tee check.log
Scan through check.log. Tests that fail will be marked by a make
error (typically preceeded by "***"). Tests that are not run because
you do not have the right permissions or software installed will be
marked by "+++" (software) or "# of untested" (permissions). In each
case, the name of tests should be apparent from the error message or
from the directory name printed immediately before the test was, for
example "making check in tests/dejagnu". Make a list of the test
directories containing tests that either failed or did not run so you
can include them in the build information form (see below).
o If you'd like, test the software yourself. Follow the installation
manual to install a Master KDC, create a principal with kadmin, and
test kinit. Set up klogind, kshd, telnetd, or gssftpd on a machine
and attempt to use the services.
o Run make install into an empty directory as root. Make sure you
have set your umask to 022 before doing the make install, so that the
permissions are correct. For example:
# umask 022
# mkdir /tmp/krb5-1.0
# make install DESTDIR=/tmp/krb5-1.0
o Fill out the build information template below and write the
completed result to the file README.buildinfo, which should be
installed in $DESTDIR/usr/local/README.buildinfo.
# cp README.buildinfo /tmp/krb5-1.0/usr/local
o Create the tar file:
% cd /tmp/krb5-1.0/usr/local
% tar cvf - . | gzip --best > /tmp/krb5-1.0pl1.<platform>.tar.gz
<platform> shall be the GNU system name (i.e., sparc-sun-solaris2.4)
This name is printed early in the configure process; you can also find
it by using the command "grep cv_host config.cache" in the top level
build directory.
o Create a detached PGP signature of the distribution file:
% pgp -sab /tmp/krb5-1.0pl1.<platform>.tar.gz
o Prepend the README.buildinfo to the beginning of the PGP signature file
(krb5-1.0.<platform>.asc)
o FTP the distribution image and PGP signature to
ftp://tsx-11.mit.edu/incoming/k5-1.0-builds/krb5-1.0pl1.<platform>.tar.gz
ftp://tsx-11.mit.edu/incoming/k5-1.0-builds/krb5-1.0pl1.<platform>.asc
o Send email to Ted Ts'o (tytso@mit.edu) informing him that you have
completed the build, and include another copy of the build information
template.
----------------------------------------------------------------------
Instructions for filling out Kerberos 5 1.0 build information form
----------------------------------------------------------------------
All fields of the build information template must be filled out for
your build to be used. Since you will be signing your build yourself,
you are responsible for the correctness of the information. The
template, which will be included as the README.buildinfo file in each
binary distribution, states that as the builder you assert only that
you compiled the source code as given to you by MIT and that you are
not responsible for any problems resulting from its use.
o Name of builder. Enter your name. This should contain your real
name and e-mail address. You might as well use the name on your PGP
key; for example "Barry Jaspan <bjaspan@mit.edu>".
o Date of build. The date of your build, in DD-MON-YY format. For
example, (23-Jan-68). (H-DOS lives on! Besides, DD/MM/YY can be
ambiguous. :-)
o Platform. The following two lines identify the platform on which
you compiled the distribution. For Hardware, specify the manufacturer
and major model name of the computer (for example, Sun SPARC). For
OS and Version, specify the name and version of your operating system
(for example, Solaris 2.5).
o Compiler. Specify the compiler you used. If the compiler is a
standard part of the OS, just enter "vendor." If you used some other
compiler, specify the name and version (for example, gcc 2.7.1).
o Configure options. Specify the command line arguments you gave to
configure. It should be the standard one, but if you used something
else (for example if shared library support isn't provided), list what
you used.
o Disk space required. Specify the amount of disk space required by
the binary distribution. You can obtain this figure by running "du
-sk" in the top-level of your install tree.
o Tests failed and Tests not run. If you did not run make check at
all, specify "all" for tests not run. Otherwise, list tests that
failed (printing "***") or were not run (printing "+++" or "# of
untested"). If you do not have dejagnu installed, the tests run not
section will include at least lib/rpc, lib/kadm5, kpasswd, and
tests/dejagnu.
o Notes. Any additional information you would like to provide. If
you used different compiler options or the like, explain why. You may
add as many Notes lines as necessary.
---------- cut here ----------
MIT Kerberos 5 1.0 Patchlevel 1 Build Information
The following form describes this Kerberos 5 1.0 pl1 binary
distribution. The builder asserts that she or he followed MIT's
instructions to compile and test exactly the source code provided in
MIT Kerberos 5 1.0 pl1 without modification. The builder makes no other
promises about the distribution; all disclaimers in the top-level
README file apply.
Name of builder :
Date of build :
Platform:
Hardware :
OS and version :
Compiler :
Configure options :
Disk space required :
Tests failed :
Tests not run :
Notes :
---------- cut here ----------
