From owner-freebsd-current Thu Mar 7 7:55:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 60EFD37B404; Thu, 7 Mar 2002 07:55:49 -0800 (PST) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.11.6/8.11.6) with UUCP id g27FtjR56123; Thu, 7 Mar 2002 15:55:45 GMT (envelope-from mark@grimreaper.grondar.za) Received: from grimreaper (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.2/8.12.2) with ESMTP id g27FrmRV022078; Thu, 7 Mar 2002 15:53:48 GMT (envelope-from mark@grimreaper.grondar.za) Message-Id: <200203071553.g27FrmRV022078@grimreaper.grondar.org> To: Dag-Erling Smorgrav Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: 5-CURRENT source upgrade path is broken in PAM References: In-Reply-To: ; from Dag-Erling Smorgrav "07 Mar 2002 12:55:46 +0100." Date: Thu, 07 Mar 2002 15:53:47 +0000 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Maxim Sobolev writes: > > Looks like source upgrade path is broken due to PAM. My system is -CURRENT > > compiled on 19 February. Please fix. > > Please use 'make world' to upgrade your system. Its more broken than that. I have a fix. The problem is in the headers; you changed #include "pam_mod_misc.h" to #include without ensuring that a (correct) pam_mod_misc.h was in an appropriate secure/ dir. I've just finished fixing this (includes a repo-copy) and it will go in shortly. M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message