similar to: bug: RELENG_4_8 rc.diskless1 typo

On a 4.8-PRERELEASE, I have cvsup'ed my sources to the latest RELENG_4_8. While doing buildworld, I get this: cc -c -O -pipe -fexceptions -DIN_GCC -D_PTHREADS -DGTHREAD_USE_WEAK -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DL_pure -o _pure.o /usr/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc2.c c++ -c -O -pipe -fexceptions

Read the documentation on the meaning of the various 4.X tags, and am not sure what is meant by this: "The release branch for FreeBSD-4.6 and FreeBSD-4.6.2, used only for security advisories and other seriously critical fixes." Similar descriptions are used for the other RELENG_4_X tags. If I specify RELENG_4 will cvsup also include RELENG_4_3 to RELENG_4_8? Sorry folks - I'm

I've built RELENG_4 isos no problem, is there a trick to building the RELENG_4_8 isos? I am building the 'miniinst' disk - that is, with the release, docs, and a port tree, but no ports. This is so I can do a fresh install without having to update the world... I am using a script that looks like this... #!/bin/sh rm -rf /usr/obj cd /usr/src make -DNOCLEAN world kernel cd

At the end of March, the RELENG_4_8 (sometimes called 4.8-SECURITY) branch will reach its designated End of Life and cease to be supported by the FreeBSD Security Team. Released in April 2003, FreeBSD 4.8 was the first release designated for "extended" two-year security support instead of the normal one-year support. Over this time, 27 security advisories have been issued which have

Sorry if this is a known problem... I've been tracking RELENG_4 on my Toshiba laptop for a while now; a couple of months ago (not sure when) my sound stopped working. More specifically, when it gets to the pcm probe, the boot hangs. I dual-boot with WinXP and figured that somehow XP had hosed the hardware, so I wrote it off. Today, I made world with RELENG_4_8, and voila, my sound's

On Fri, Jul 25, 2003 at 12:44:05AM +0100, Darren wrote: [...] > Thought i'd email you before mailing the list. I've been trying to > compile OpenSSH statically under FreeBSD and am running onto a linker > error that I can't resolve and wondered if you had knowledge of this > particular problem? > I've just committed a fix for this: src/share/mk/bsd.libnames.mk,v