Fwd: 007_resolver.patch, rebuild bin and sbin, missing sbin/wsconsctl/keysym.h

["Jason P. Stanford" <Jason_(_dot_)_Stanford_(_at_)_lehigh_(_dot_)_edu>]

Mea culpa, I did *NOT* do 'make depend'! D'Oh!

I will read over cvsup. I'd used it on FreeBSD with good results. I've 
not tried it on OpenBSD (usually just re-re-review the CVS literature 
and go from there, but do not mind it).

I try to avoid the full "make world" type command unless absolutely 
necessary. The machine isn't all that powerful and I can't have it 
offline all that long. (I am currently trying to cobble together a 
build machine from spare parts for this type of thing, though.)

Just curious however, where does this keysym.h file come from anyway? 
Can I just grab it from somewhere to throw in the directory? (I think I 
can hear and expect loud groans in response that question... :-)  That 
way doesn't feel or sound right to me, but perhaps it's innocuous and 
harmless enough?)

-Jason


Begin forwarded message:

> From: "Jason P. Stanford" <Jason_(_dot_)_Stanford_(_at_)_Lehigh_(_dot_)_EDU>
> Date: Wed Aug 28, 2002  7:42:33 PM US/Eastern
> To: misc_(_at_)_openbsd_(_dot_)_org
> Subject: 007_resolver.patch, rebuild bin and sbin, missing 
> sbin/wsconsctl/keysym.h
>
> I have just installed 3.1 on a fresh i386 box from the CD set, and 
> have started to apply all patches. I am running into a problem (or at 
> least it *seems* to be a problem), and I cannot find the answer in the 
> mail archives or google.
>
> I have just applied the 007_resolver.patch as directed and it says 
> that the /usr/src/bin and /usr/src/sbin directories should be rebuilt 
> (or parts of them, but they were unspecified as far as I could find).
>
> I did a 'cd /usr/src/bin' and issued a 'make' and 'make install' 
> without problem. Then I went to /usr/src/sbin and issued a 'make' 
> command. It gets to the last directory /usr/src/sbin/wsconsctl and it 
> fails because a file 'keysym.h' is missing and is trying to include it 
> in 'keysym.c'. I've checked the CVS repository and 'keysym.h' is not 
> there as well.
>
> I'm not familiar with the keysym.* files, but according to my searches 
> it seems to have something to do with X. I'm not using, nor do I 
> intend to use X on this particular box.
>
> My question is, can I ignore the error to wsconsctl, should I manually 
> intervene? If so, what would I need to do?
>
> Thanks!
>
> --
> Jason P. Stanford
> Manager, Design Arts Computing Lab (CU209)
> Integrated Product Development (IPD)
> http://www.lehigh.edu/ipd/
> (610) 758-5845
--
Jason P. Stanford
Manager, Design Arts Computing Lab (CU209)
Integrated Product Development (IPD)
http://www.lehigh.edu/ipd/
(610) 758-5845