Re: PATCH: partial fix for broken "make release"...

2001-05-02 Thread John Baldwin
On 03-May-01 Terry Lambert wrote: > A "make world" works perfectly fine, and builds everything, including > the "pam_ssh", just fine. Examining the "/usr/obj" and the CHROOT > version of "/usr/obj" indicates that the difference is that the > libssh isn't built in the chroot case, and is referenc

Re: PATCH: partial fix for broken "make release"...

2001-05-02 Thread Terry Lambert
] On 02-May-01 Jordan Hubbard wrote: ] > From: Terry Lambert <[EMAIL PROTECTED]> ] >> The "make release" stuff is broken, at least in 4.3, and possibly ] >> before that. ] >> ] >> There are several obviously broken things: ] >> ] >> oThe libssh stuff is not installed, and it is not built ] >

Re: PATCH: partial fix for broken "make release"...

2001-05-02 Thread John Baldwin
On 02-May-01 Jordan Hubbard wrote: > From: Terry Lambert <[EMAIL PROTECTED]> > Subject: PATCH: partial fix for broken "make release"... > Date: Wed, 2 May 2001 22:00:37 + (GMT) > >> The "make release" stuff is broken, at least in 4.3, and possi

Re: PATCH: partial fix for broken "make release"...

2001-05-02 Thread Jordan Hubbard
From: Terry Lambert <[EMAIL PROTECTED]> Subject: PATCH: partial fix for broken "make release"... Date: Wed, 2 May 2001 22:00:37 + (GMT) > The "make release" stuff is broken, at least in 4.3, and possibly > before that. > > There are several obviousl

Re: PATCH: partial fix for broken "make release"...

2001-05-02 Thread Bruce A. Mah
If memory serves me right, Terry Lambert wrote: > o The files jade_1.2.1-13.diff.gz and pdf_sec.ps are not > available from any of the listed mirros in the "ports" > hierarchy, so they can not be correctly installed, and > a "doc" build can not complete. The workaround is t

PATCH: partial fix for broken "make release"...

2001-05-02 Thread Terry Lambert
The "make release" stuff is broken, at least in 4.3, and possibly before that. There are several obviously broken things: o The libssh stuff is not installed, and it is not built during a "make release"; I don't know why that is; the workaround is to wait for it to bomb out