Re: 3.3-stable -> 4.0-current problem...

1999-12-08 Thread Adam
Sounds like its time to hack cvsup to display a diff of UPDATING from before and after cvsup. If it actually happened I dont think people would mind because the average change is only a dozen lines or less it would coincide with the amount of output cvsup would show for someone who frequently cvs

Re: 3.3-stable -> 4.0-current problem...

1999-12-08 Thread David O'Brien
On Tue, Dec 07, 1999 at 09:09:01PM +, Michael Chin-Yuan Wu wrote: > > All they need is a simple pointer, Feh. What do you think /usr/src/UPDATING is? > why not be a bit nicer? :) I was the first 20 times things like this came up. -- -- David([EMAIL PROTECTED]) To Unsubscribe: se

Re: 3.3-stable -> 4.0-current problem...

1999-12-07 Thread David Scheidt
On Tue, 7 Dec 1999, Darryl Okahata wrote: > Michael Chin-Yuan Wu <[EMAIL PROTECTED]> wrote: > > > Please try this tutorial when you move from -stable to -current > > > > www.external.org/freebsd/current.html > > I think you're missing the recent block device obsolescence > change. I had

Re: 3.3-stable -> 4.0-current problem...

1999-12-07 Thread Darryl Okahata
Michael Chin-Yuan Wu <[EMAIL PROTECTED]> wrote: > Please try this tutorial when you move from -stable to -current > > www.external.org/freebsd/current.html I think you're missing the recent block device obsolescence change. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER:

Re: 3.3-stable -> 4.0-current problem...

1999-12-07 Thread Michael Chin-Yuan Wu
David O'Brien wrote: > > On Tue, Dec 07, 1999 at 11:41:43AM +0300, Hostas Red wrote: > > I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and > ... > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c > > Bad system call - core dumped > > mkdep: compile failed > > *** Error

Re: 3.3-stable -> 4.0-current problem...

1999-12-07 Thread David O'Brien
On Tue, Dec 07, 1999 at 11:41:43AM +0300, Hostas Red wrote: > I've cvsup'ed my 3.3-stable source tree to 4.0-current source tree, and ... > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c > Bad system call - core dumped > mkdep: compile failed > *** Error code 1 ..snip.. > > Anybody knows w

Re: 3.3-stable -> 4.0-current problem...

1999-12-07 Thread Hostas Red
Hi! On Tue, 7 Dec 1999, Sean Jensen-Grey wrote: > Building the kernel first works. also you will need to run the /usr/sbin/config > from the /usr/src/usr.sbin tree as the installed one is for the older kernel > format. Yes, worked fine, thanks. I've tried to compile new kernel before, but forgo

Re: 3.3-stable -> 4.0-current problem...

1999-12-07 Thread Michael Chin-Yuan Wu
Sean Jensen-Grey wrote: > > Building the kernel first works. also you will need to run the /usr/sbin/config > from the /usr/src/usr.sbin tree as the installed one is for the older kernel > format. > > Sean. This will work: src/usr.sbin/config # make all install use this new config to compile

Re: 3.3-stable -> 4.0-current problem...

1999-12-07 Thread Sean Jensen-Grey
Building the kernel first works. also you will need to run the /usr/sbin/config from the /usr/src/usr.sbin tree as the installed one is for the older kernel format. Sean. On Tue, 7 Dec 1999, Marc Solsona wrote: > I've tried to do the same and it seems that there have been some changes of > the

Re: 3.3-stable -> 4.0-current problem...

1999-12-07 Thread Marc Solsona
I've tried to do the same and it seems that there have been some changes of the signal achitecture. A solution I found was to build a kernel 4.0 before building world. I haven't tried though. Tell me if it works!! EXT Hostas Red wrote: > Hi! > > I've cvsup'ed my 3.3-stable source tree to 4.0-cu