From owner-freebsd-stable Sun Aug 4 11:13:40 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39E8937B405 for ; Sun, 4 Aug 2002 11:13:34 -0700 (PDT) Received: from silence.serial.nl (a94089.upc-a.chello.nl [62.163.94.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF46843E6A for ; Sun, 4 Aug 2002 11:13:32 -0700 (PDT) (envelope-from serial@serial.nl) Received: from winxp ( [192.168.0.4] (may be forged)) by silence.serial.nl (8.11.6/8.11.6) with SMTP id g74I9rR80964; Sun, 4 Aug 2002 20:09:53 +0200 (CEST) (envelope-from serial@serial.nl) Message-ID: <017b01c23be2$b5a1c240$0400a8c0@winxp> From: "Silvester van der Leer" To: "chris horn." Cc: References: Subject: Re: 4.6-stable branch broken ? Date: Sun, 4 Aug 2002 20:14:01 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, > I'm living in EDT (GMT -4). Last night and today I also found > that 4.6 seemed to be broken. Funny thing, though, is the problem I've > encountered is with readpassphrase.h not being found in in > /usr/src/crypto/openssh/ (not /usr/src/lib/libc/../libc/gen/). > same problem here. > Specifically, the error is thrown when readpasphrase.h is included here > > #ifdef HAVE_READPASSPHRASE_H > # include > #endif > > in the file /usr/src/crypto/openssh/includes.h > > How, if at all, were you able to resolve your problem? Maybe it's related to > mine. i haven't been able to fix the problem at this very moment, maybe there other people with the same problem. i think de -stable is broken Silvester To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message