sysinstall bootstrapping issues [Was: -CURRENT b0rked?]

2001-05-14 Thread Maxim Sobolev
On Sun, 13 May 2001 17:13:01 +0200 (SAT), John Hay wrote: It seems that sysinstall(8) was not fully integrated into buildworld - it depends on content of /usr/share/syscons/keymaps, while it shouldn't. I've just committed a patch that should fix this problem. You

Re: [sysinstall bootstrapping issues [Was: -CURRENT b0rked?]]

2001-05-14 Thread John Hay
It looks like kbdcontrol is not very happy. Ok, here is a patch that fix the problem for me. The problem is that a second call to mkfullname() will reuse the memory at the pointer that it returns, so you have to preserve it before then. OOPS, sorry. I've overlooked it. Should

Re: -CURRENT b0rked?

2001-05-14 Thread Terry Lambert
John Hay wrote: It seems that sysinstall(8) was not fully integrated into buildworld - it depends on content of /usr/share/syscons/keymaps, while it shouldn't. I've just committed a patch that should fix this problem. You should look a little earlier in the logs to

Re: Re: -CURRENT b0rked?

2001-05-13 Thread Mike Pritchard
On Sat, May 12, 2001 at 10:11:25PM -0500, Matthew D. Fuller wrote: On Sat, May 12, 2001 at 10:07:20PM -0500 I heard the voice of Ken Wills, and lo! it spake thus: Deleting keymap.h (autogenerated, in obj/* somewhere, I forget), and restarting the build got me past this. I start all my

Re: Re: -CURRENT b0rked?

2001-05-13 Thread John Hay
It seems that sysinstall(8) was not fully integrated into buildworld - it depends on content of /usr/share/syscons/keymaps, while it shouldn't. I've just committed a patch that should fix this problem. Hoo, here I come to make your life a living hell once more... In file

Re: Re: -CURRENT b0rked?

2001-05-13 Thread John Hay
It seems that sysinstall(8) was not fully integrated into buildworld - it depends on content of /usr/share/syscons/keymaps, while it shouldn't. I've just committed a patch that should fix this problem. You should look a little earlier in the logs to where the damage was

Re: -CURRENT b0rked?

2001-05-13 Thread David Wolfskill
I applied John's patch to usr.sbin/kbdcontrol/kbdcontrol.c, but it still dies for me; same way: -- stage 4: make dependencies -- ... === usr.sbin/sysinstall rm -f

Re: -CURRENT b0rked?

2001-05-13 Thread David Wolfskill
From: John Hay [EMAIL PROTECTED] Date: Sun, 13 May 2001 20:54:56 +0200 (SAT) Well I must admit that I cheated. After the patch I did a make all install in the kbdcontrol directory. The problem is that kdbcontrol is not in any of the build-tools/bootstrap-tools targets, so the installed version

Re: -CURRENT b0rked?

2001-05-13 Thread Thomas D. Dean
After having the sysinstall/kbdcontrol problem, I cd src/usr.sbin/sysinstall make clean cvsup make world and all worked OK. As of Sat May 12 1430 PDT. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: Re: -CURRENT b0rked?

2001-05-12 Thread Maxim Sobolev
On Sat, 12 May 2001 08:48:24 +0300 (EEST), Maxim Sobolev wrote: On Fri, 11 May 2001 23:44:17 -0500, Matthew D. Fuller wrote: On several attempts to build world, I'm getting ths same error: In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40: keymap.h:3606:

Re: Re: -CURRENT b0rked?

2001-05-12 Thread Matthew D. Fuller
On Sat, May 12, 2001 at 12:21:55PM +0300 I heard the voice of Maxim Sobolev, and lo! it spake thus: It seems that sysinstall(8) was not fully integrated into buildworld - it depends on content of /usr/share/syscons/keymaps, while it shouldn't. I've just committed a patch that should fix

Re: Re: -CURRENT b0rked?

2001-05-12 Thread Ken Wills
* Matthew D. Fuller [EMAIL PROTECTED] [010512 19:35]: On Sat, May 12, 2001 at 12:21:55PM +0300 I heard the voice of Maxim Sobolev, and lo! it spake thus: It seems that sysinstall(8) was not fully integrated into buildworld - it depends on content of /usr/share/syscons/keymaps, while it

Re: Re: -CURRENT b0rked?

2001-05-12 Thread Matthew D. Fuller
On Sat, May 12, 2001 at 10:07:20PM -0500 I heard the voice of Ken Wills, and lo! it spake thus: Deleting keymap.h (autogenerated, in obj/* somewhere, I forget), and restarting the build got me past this. I start all my builds with an empty /usr/obj and a freshly co'd /usr/src. Re-newfs'ing

-CURRENT b0rked?

2001-05-11 Thread Matthew D. Fuller
On several attempts to build world, I'm getting ths same error: In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40: keymap.h:3606: `keymap_ua_koi8_u_shift_alt' undeclared here (not in a function) keymap.h:3606: initializer element is not constant keymap.h:3606: (near initialization

Re: -CURRENT b0rked?

2001-05-11 Thread Maxim Sobolev
On Fri, 11 May 2001 23:44:17 -0500, Matthew D. Fuller wrote: On several attempts to build world, I'm getting ths same error: In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40: keymap.h:3606: `keymap_ua_koi8_u_shift_alt' undeclared here (not in a function) keymap.h:3606: