Alexander Langer wrote:
> maintain compatibility with existing binaries. A new kernel must
> be made and installed and booted with before a make world can
> be done.
>
> Alex
Sorry. I really miss this. :(
Vadim.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
Thus spake Vadim Chekan ([EMAIL PROTECTED]):
> > Are you SURE you're prepaired to run -CURRENT?
> Yes, Im shure.
No, you are _not_.
> Maybe I miss somesing, but I didn't found any hint "how to jump from 3
> to 4" in /usr/src/UPDATING
The second one:
19990929:
The sigset_t datatype ha
David O'Brien wrote:
>
> > I'm trying to update from 3.3-R to 4.0-current but without success.
> > cc every time died on the same place.
>
> Where are your D-E-T-A-I-L-S ???
Details which I describe was enough to get 4 replies.
I supposed and I was right that where it die has nothing to deal wi
> I'm trying to update from 3.3-R to 4.0-current but without success.
> cc every time died on the same place.
Where are your D-E-T-A-I-L-S ???
Where did it die? Compiling /bin/false ?
> When I try again cc died with message "Bad system call"
Did you read /usr/src/UPDATING? Have you been rea
On Thu, Nov 18, 1999 at 09:03:14PM +0100, Jag wrote:
> I have a 3.3-STABLE (SMP) system and I want to move to CURRENT.
Please don't do that.
> Do you mean that I should build a new kernel *before* I do buildworld?
> Is that possible?
You OBVIOUSLY have not read /usr/src/UPDATING nor this mailin
Vadim Chekan wrote:
>
> Hello everyone!
>
> I'm trying to update from 3.3-R to 4.0-current but without success.
Thanks to all!
Now I know what to do. 4.0 kernel is installed and is bootable. I need
to chouse few hours to build world.
Vadim Chekan.
To Unsubscribe: send mail to [EMAIL PROTECT
People,
1) Search -current archives if you are new to the list.
2) See that /usr/src/UPDATING file? READ IT!
Handbook&FreeBSD diary are *NOT* the kind of resource you resort to
if you want to run -current. Things in -current have not been
documented because they are happening here and now.
And
Yes, there was a change in the signal handling that requires the kernel
for 4.0 to be built and booted prior to building userland for 4.0. (This
is not from experience, this is from watching the current mailing list for
the past year). I believe the -current mailing list had lots of traffic
on t
Jag <[EMAIL PROTECTED]> wrote:
> Alexander Langer wrote:
> > Yes. Probably you've not built/booted a -current kernel before you build wo
> rld.
>
> Do you mean that I should build a new kernel *before* I do buildworld?
> Is that possible?
Yes and yes.
> Some clarification would be great.
Thus spake Jag ([EMAIL PROTECTED]):
> I'm in almost the same situation as mr Chekan. I have a 3.3-STABLE (SMP)
> system and I want to move to CURRENT. I have modified my cvs-scripts and
> updated the sources a few times the last couple of weeks. The problem is
> when I try to do buildworld. It cr
Hi!
I'm in almost the same situation as mr Chekan. I have a 3.3-STABLE (SMP)
system and I want to move to CURRENT. I have modified my cvs-scripts and
updated the sources a few times the last couple of weeks. The problem is
when I try to do buildworld. It crashes with things like:
cc -static -O -
Vadim Chekan wrote:
> Hello everyone!
>
> I'm trying to update from 3.3-R to 4.0-current but without success.
> cc every time died on the same place.
> I upgraded via sources to 3.3-stable without any problem.
> When I try again cc died with message "Bad system call"
> I wrote in /etc/makefile.co
Thus spake Vadim Chekan ([EMAIL PROTECTED]):
> Is my problem known or I should post more logs?
Yes. Probably you've not built/booted a -current kernel before you build world.
Alex
--
I doubt, therefore I might be.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cur
Hello everyone!
I'm trying to update from 3.3-R to 4.0-current but without success.
cc every time died on the same place.
I upgraded via sources to 3.3-stable without any problem.
When I try again cc died with message "Bad system call"
I wrote in /etc/makefile.conf
CC=/usr/local/bin/gcc295
CXX=/
14 matches
Mail list logo