My -STABLE build box (nfs src obj host for my -STABLE clients) died
yesterday afternoon. I was wondering if I could simply use my -CURRENT build
box (nfs src obj host for -CURRENT cleints) to also host src obj for
-STABLE. Would I just modify my supfile to put the -STABLE src elsewhere and
then
On Mon, Jan 22, 2001 at 03:46:51PM -0500, Benjamin Lewis wrote:
Robert,
You wrote:
For the last few days (not sure when it started) I've been unable to build
-STABLE on a -CURRENT machine. This has proven a problem for recent
RELENG_3 MFC's of security fixes; I've tried upgrading to
Robert,
You wrote:
For the last few days (not sure when it started) I've been unable to build
-STABLE on a -CURRENT machine. This has proven a problem for recent
RELENG_3 MFC's of security fixes; I've tried upgrading to the most recent
-CURRENT on the box, making sure /usr/include is
Sending this to freebsd-stable or freebsd-current was somewhat of a
toss-up, but since I expect more committers hang out on -current than
-stable, here it is.
For the last few days (not sure when it started) I've been unable to build
-STABLE on a -CURRENT machine. This has proven a problem for
On Thu, Jun 22, 2000 at 10:12:28PM -0400, Kent Hauser wrote:
For the last while (several months), whenever I try to build
a RELENG_4 release from my -current box, it fails building gcc.
Yes. (but it should only have been for the past 1.5 mos).
There are two ways to fix it. One will be done
On Thu 2000-06-22 (22:12), Kent Hauser wrote:
For the last while (several months), whenever I try to build
a RELENG_4 release from my -current box, it fails building gcc.
As -current is supposed to be "fluid" for the next several months,
I wanted to make a set of -current and -stable CDs
Hi,
For the last while (several months), whenever I try to build
a RELENG_4 release from my -current box, it fails building gcc.
As -current is supposed to be "fluid" for the next several months,
I wanted to make a set of -current and -stable CDs now.
The current build was fine. To build
