similar to: [releng_4 tinderbox] failure on i386/pc98

TB --- 2003-08-09 16:00:11 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-08-09 16:00:11 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:11 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:11 - ERROR: unable to check out the source tree TB ---

TB --- 2003-08-09 16:00:11 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-08-09 16:00:11 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:11 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:11 - ERROR: unable to check out the source tree TB ---

TB --- 2003-07-21 05:27:28 - starting RELENG_4 tinderbox run for i386/pc98 TB --- 2003-07-21 05:27:28 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-07-21 05:33:30 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98/src TB --- /usr/bin/make -B buildworld >>>

TB --- 2003-10-02 04:00:01 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-10-02 04:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:07:38 - building world TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>>

TB --- 2003-10-02 04:44:07 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-10-02 04:44:07 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:49:12 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/i386/src TB --- /usr/bin/make -B buildworld >>>

TB --- 2013-10-31 19:50:43 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-10-31 19:50:43 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-10-31 19:50:43 - starting RELENG_10 tinderbox run for i386/pc98 TB --- 2013-10-31 19:50:43 - cleaning the

Very shortly after starting the buildworld, it fails in colldef: ===> usr.bin/colldef /usr/obj/home/src/i386/home/src/usr.bin/colldef created for /home/src/usr.bin/colldef yacc -d /home/src/usr.bin/colldef/parse.y cp y.tab.c parse.c lex -t -8 -i /home/src/usr.bin/colldef/scan.l > scan.c rm -f .depend mkdep -f .depend -a -I. -I/home/src/usr.bin/colldef

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've just cvsupped my RELENG_4 tree this morning, and this is what I get when I do make depend after I configure my kernel: mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ - -I@/../include -I/usr/include /usr/src/sys/modules/ida/../../dev/ida/ida.c /usr/src/sys/modules/ida/../../dev/ida/ida_disk.c

after cvsup'ing src-all to RELENG_4 and trying to make buildworld I get the next error message: /usr/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/cmap.cc:25: cmap.h: No such file or directory and a lot of the same messages "No such file or directory" on file cmap.cc, with mkdep: compile failed *** Error code 1 at the end of output I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:13.sendmail Security Advisory The FreeBSD Project Topic: Race condition in sendmail Category: contrib Module: contrib_sendmail Announced:

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

Hi All. After one false start, I now have a Tinderbox up and running for the OpenSSH portable tree. For those not familiar with it, Tinderbox is a tool for automatically displaying the status of builds and tests. At the moment, I do 1 update and 4 builds hourly. It's not fully functional yet but the basics work. It can be found at http://dodgynet.dyndns.org/tinderbox/OpenSSH_Portable/ (I

Today my system coredumped (4.8-STABLE from Saturday), I believe it's somehow X11 related: X11 crashed first (signal 11). I was running it as root (I know I shouldn't). I didn't think about it and restarted X11. While it was starting, I had a look at the console, there was a bright white message: issignal. This shows up at X11 startup. Then the system coredumped. Below is more

TB --- 2008-07-29 09:37:14 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-07-29 09:37:14 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2008-07-29 09:37:14 - cleaning the object tree TB --- 2008-07-29 09:37:32 - cvsupping the source tree TB --- 2008-07-29 09:37:32 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB ---

TB --- 2008-08-27 11:26:00 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-08-27 11:26:00 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2008-08-27 11:26:00 - cleaning the object tree TB --- 2008-08-27 11:26:30 - cvsupping the source tree TB --- 2008-08-27 11:26:30 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/amd64/amd64/supfile TB --- 2008-08-27

http://tinderbox.x.org/builds/2008-07-08-0003/ http://tinderbox.x.org/builds/2008-07-08-0003/logs/xf86-video-nouveau/#build nouveau_bo.c: In function 'nouveau_bo_new': nouveau_bo.c:51: error: 'NOUVEAU_MEM_TILE' undeclared (first use in this function) nouveau_bo.c:51: error: (Each undeclared identifier is reported only once nouveau_bo.c:51: error: for each function it appears in.)

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

On the one hand, yes, they're about things most readers can't do anything about. On the other hand, they do let you know (once the tinderbox has stabilized, this being a new setup with the bugs being worked out of it) whether recent -STABLE will build or not, which can be quite useful even for ordinary users of -STABLE. (You know to hold off on updating if it's failing for your

I use FreeBSD RELENG_4 with rsync version 2.5.4 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 32-bit system inums, 64-bit internal inums and when I try to transfer file I get rsync: connection unexpectedly closed (5994 bytes read so

TB --- 2008-06-03 08:42:30 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-03 08:42:30 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2008-06-03 08:42:30 - cleaning the object tree TB --- 2008-06-03 08:43:09 - cvsupping the source tree TB --- 2008-06-03 08:43:09 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/i386/supfile TB --- 2008-06-03 08:43:22