From owner-freebsd-bugs  Sat Mar 14 08:00:05 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA24021
          for freebsd-bugs-outgoing; Sat, 14 Mar 1998 08:00:05 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA23977;
          Sat, 14 Mar 1998 08:00:02 -0800 (PST)
          (envelope-from gnats)
Date: Sat, 14 Mar 1998 08:00:02 -0800 (PST)
Message-Id: <199803141600.IAA23977@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: bin/5999: kadmin bug -- crypt not linked correctly, fails to work 
Reply-To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR bin/5999; it has been noted by GNATS.

From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
To: Robert Watson <robert+freebsd@cyrus.watson.org>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: bin/5999: kadmin bug -- crypt not linked correctly, fails to work 
Date: Sat, 14 Mar 1998 07:53:25 -0800

 > I believe I attached a patch to the email; it appears to work correctly
 > here, as it just adds a -lcrypt to the kadmin Makefile.  When you say back
 > out the K4 changes, do you mean pull out on the KTH upgrade for 2.2.6?  A
 
 Yes, I mean pull them out completely.  kadmin is only *one* of the
 multiple targets that fall over when I enabled this option in
 2.2-stable and, in fact, a good many things don't even _build_ much
 less link! :-(
 
 					Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message