Thanks for the clarification. I now understand that I have got things messed up. I have been on -current ( as of 25. Sep ) , at least I strongly believe this but cannot prove because I have overwritten the system in the meantime.
Then I run into problems rebuilding the kernel after a cvs update. I figured that I should update the binaries and pick the wrong ones, as you have pointed out. I fixed that and now all is fine again. Thanks Christoph PS: I should work on my googling abilities. I search for locore.s and thus missed the message you referred to. > -----Ursprüngliche Nachricht----- > Von: Philip Guenther [mailto:guent...@gmail.com] > Gesendet: Montag, 26. November 2012 21:44 > An: Christoph Leser > Cc: 'misc@openbsd.org' (misc@openbsd.org) > Betreff: Re: ../../../../arch/i386/i386/locore.s:1755: Error: no such > instruction: > `stac' > > On Mon, Nov 26, 2012 at 10:42 AM, Christoph Leser <le...@sup-logistik.de> > wrote: > > I'm trying to build the kernel for -current I updated the binaries > > first, then updated the source tree and then did > ... > > ../../../../arch/i386/i386/locore.s:1755: Error: no such instruction: `stac' > > ../../../../arch/i386/i386/locore.s:1759: Error: no such instruction: `clac' > > *** Error code 1 > > This question was asked and answered 3 weeks ago: > http://comments.gmane.org/gmane.os.openbsd.misc/200525 > > > Alternatively, you're thinking about -stable when you say -current. > Note the start of your dmesg: > > > OpenBSD 5.2 (GENERIC) #278: Wed Aug 1 10:04:16 MDT 2012 > > That sure looks like *stable* and not *current*. Indeed, the -current > i386 snapshot right now says: > > OpenBSD 5.2-current (GENERIC) #89: Mon Nov 19 12:49:11 MST 2012 > > If you want -stable, you'll need to change your cvs checkout to the branch > instead of the trunk. > > > Philip Guenther
