Building stable on current
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 build those sources (with a -CURRENT world) with MAKEOBJDIRPREFIX=/usr/obj.stable (for example) and then on the -STABLE clients, mount those export points as /usr/src and /usr/obj ? Thanks in advance. --- Robin P. Blanchard Systems Integration Specialist Georgia Center for Continuing Education fon: 706.542.2404 fax: 706.542.6546 --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building -STABLE on -CURRENT
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 the most recent
-CURRENT on the box, making sure /usr/include is updated, et al. I'm
guessing this is /usr/include pollution in the /usr/src build, but won't
speculate too much more as I'm travelling tomorrow. Attached below is the
breakage from buildworld.
[...]
cd /usr/src/share/syscons/scrnmaps; make build-tools
cc -static -O -pipe -I/usr/src/share/syscons/scrnmaps
-DFIL=\"koi8-r2cp866\"
-o koi8-r2cp866.mk /usr/src/share/syscons/scrnmaps/mkscrfil.c
In file included from /usr/src/share/syscons/scrnmaps/mkscrfil.c:28:
/usr/include/machine/console.h:3: #error "this file includes
machine/console.h
which is deprecated, use sys/{kb,cons,fb}io.h instead"
I've seen the same thing. I hacked up the -stable source to include the
correct -current include files to get past this, but that strikes me as
extremely non-optimal. I tried hacking up the Makefile in
/usr/src/share/syscons/scrnmaps to use a different include path, but don't
have the know-how or mojo to get that working.
I've just hit the same problem... Has anybody got a real fix for this?
--
Sean Kelly | PGP KeyID: 77042C7B
[EMAIL PROTECTED] | http://www.zombie.org
For PGP key, send e-mail with subject "send pgp key"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Building -STABLE on -CURRENT
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 updated, et al. I'm
guessing this is /usr/include pollution in the /usr/src build, but won't
speculate too much more as I'm travelling tomorrow. Attached below is the
breakage from buildworld.
[...]
cd /usr/src/share/syscons/scrnmaps; make build-tools
cc -static -O -pipe -I/usr/src/share/syscons/scrnmaps
-DFIL=\"koi8-r2cp866\"
-o koi8-r2cp866.mk /usr/src/share/syscons/scrnmaps/mkscrfil.c
In file included from /usr/src/share/syscons/scrnmaps/mkscrfil.c:28:
/usr/include/machine/console.h:3: #error "this file includes
machine/console.h
which is deprecated, use sys/{kb,cons,fb}io.h instead"
I've seen the same thing. I hacked up the -stable source to include the
correct -current include files to get past this, but that strikes me as
extremely non-optimal. I tried hacking up the Makefile in
/usr/src/share/syscons/scrnmaps to use a different include path, but don't
have the know-how or mojo to get that working.
Have you had any replies to this message or further insights? If so, I'd
very much appreciate hearing them.
Thank you,
-Ben
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Building -STABLE on -CURRENT
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 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 updated, et al. I'm
guessing this is /usr/include pollution in the /usr/src build, but won't
speculate too much more as I'm travelling tomorrow. Attached below is the
breakage from buildworld.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
cd /usr/src/share/syscons/scrnmaps; make build-tools
cc -static -O -pipe -I/usr/src/share/syscons/scrnmaps
-DFIL=\"koi8-r2cp866\"
-o koi8-r2cp866.mk /usr/src/share/syscons/scrnmaps/mkscrfil.c
In file included from /usr/src/share/syscons/scrnmaps/mkscrfil.c:28:
/usr/include/machine/console.h:3: #error "this file includes
machine/console.h
which is deprecated, use sys/{kb,cons,fb}io.h instead"
In file included from /usr/src/share/syscons/scrnmaps/mkscrfil.c:31:
/usr/src/share/syscons/scrnmaps/koi8-r2cp866:27: syntax error before
`scrmap'
/usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: excess elements
in scalar initializer
/usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: (near
initialization for `scrmap')
/usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: excess elements
in scalar initializer
/usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: (near
initialization for `scrmap')
/usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: excess elements
in scalar initializer
/usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: (near
initialization for `scrmap')
/usr/src/share/syscons/scrnmaps/koi8-r2cp866:28: warning: excess elements
in scalar initializer
...
/usr/src/share/syscons/scrnmaps/mkscrfil.c: In function `main':
/usr/src/share/syscons/scrnmaps/mkscrfil.c:42: `scrmap_t' undeclared
(first use in this function)
/usr/src/share/syscons/scrnmaps/mkscrfil.c:42: (Each undeclared identifier
is reported only once
/usr/src/share/syscons/scrnmaps/mkscrfil.c:42: for each function it
appears in.)
*** Error code 1
Stop in /usr/src/share/syscons/scrnmaps.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: building stable from current
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 before 4.1. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: building stable from current
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 now. The current build was fine. To build stable I did the following: # cd /usr; rm -rf src.stable;mkdir src.stable # rm -rf /usr/obj/usr/src.stable # su kent % cd src.stable % cvs -R -d /home/ncvs co -r RELENG_4 src % cd src.stable; mv src/* .;rmdir src % make buildworld build.log and it blew up linking cc1plus. I built -stable as me so as to be sure no system files were touched. But I'm also confused as I thought "buildworld" was self-contained -- as long as a reasonably current make was available to jump-start the process. Thoughts corrections greatly welcomed. Can you send the last 50 or so lines of build.log? Neil -- Neil Blakey-Milner Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
building stable from current
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 stable I did the following: # cd /usr; rm -rf src.stable;mkdir src.stable # rm -rf /usr/obj/usr/src.stable # su kent % cd src.stable % cvs -R -d /home/ncvs co -r RELENG_4 src % cd src.stable; mv src/* .;rmdir src % make buildworld build.log and it blew up linking cc1plus. I built -stable as me so as to be sure no system files were touched. But I'm also confused as I thought "buildworld" was self-contained -- as long as a reasonably current make was available to jump-start the process. Thoughts corrections greatly welcomed. Kent To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
