On Fri, 21 Jan 2011 23:20:09 +0100
Ulrich Spörlein u...@freebsd.org wrote:
On Thu, 20.01.2011 at 21:17:40 +0100, Ulrich Spörlein wrote:
Hello,
Currently our buildworld relies on groff(1) and vgrind(1) being present
in the host system. I have a patch ready that at least makes sure these
On Sat, Jan 22, 2011 at 10:58:25AM +0100, Gary Jennejohn wrote:
On Fri, 21 Jan 2011 23:20:09 +0100
Ulrich Sp?rlein u...@freebsd.org wrote:
On Thu, 20.01.2011 at 21:17:40 +0100, Ulrich Sp?rlein wrote:
Hello,
Currently our buildworld relies on groff(1) and vgrind(1) being present
On Thu, 20 Jan 2011 23:11:43 +0100
Ulrich Spörlein u...@freebsd.org wrote:
On Thu, 20.01.2011 at 15:31:03 -0500, Alexander Kabaev wrote:
On Thu, 20 Jan 2011 21:17:40 +0100
Ulrich Spörlein u...@freebsd.org wrote:
Hello,
Currently our buildworld relies on groff(1) and vgrind(1)
On Sat, Jan 22, 2011 at 12:55 AM, Ivan Voras ivo...@freebsd.org wrote:
On 21/01/2011 14:22, Andrey V. Elsukov wrote:
On 21.01.2011 16:03, Ivan Voras wrote:
On 21/01/2011 13:56, Johan Hendriks wrote:
Ok the funny thing is, i get the same error on 8.1 Release (the corrupt
error), but it
Sergey Kandaurov pluk...@gmail.com wrote:
Committed in r217688.
Thanks!
Will this be eligible for MFC? (Not for 8.2 or 7.4 I suppose --
presumably they are only accepting bug-fixes at this point -- but
I'd expect it to be compatible with 8-CURRENT.)
The second Release Candidate for the FreeBSD 7.4 release cycle is
now available. For this build only the amd64, i386, pc98, and
sparc64 architectures are available.
An initial set of pre-build packages are available on the DVD
and CDROM images for the amd64 architecture. At the time the
i386
