6 replies to this topic

[v90]

Was doing a make buildkernel, giving me shit with linking umass.o, did a make -j4, suddenly that problem is gone Now it's just giving me some crazy crap Think it's time to break out OpenBSD, Free giving me too much shit... Anyone encountered the make bug before?

[psychopuppy]

what version is that?

[v90]

5.0 with RELENG_5_1 sources from 2 days ago

[psychopuppy]

thats the CURRENT branch right? thats probably why its giving you crap.

I tried 5.1 a few weeks ago and it worked fine though. i guess thats why they call it unstable, sometimes it works and sometime it doesnt

[v90]

I believe thats -stable but I'm seriously screwing up things between *BSDs Also no new updates in 2 days so I don't think it's -current, I'm just gonna wait a week, get my Open box set up, then reupdate all my sources and remake world and my kernel... Not in the mood for another ass screwing...

[phax]

Hey, sorry for the late comment but if you where using -stable always cp your working kernel source and tar it.

the sources for FreeBSD-STABLE may or may not be suitable for any particular purpuse.

update your kernel source at least every 4 days if using -stable it common for that to happen if U want use the -release works like a charm no problems.

MORE INFO

If using FreeBSD read it and re-read it

[psychopuppy]

i just reinstalled freebsd and cvsup'ed to RELENG_5_1 and i get the same error about umass.o when i try to compile the kernel with firewall support in it.