Re: [head tinderbox] failure on arm/arm
TB --- 2014-06-28 16:10:48 - /usr/bin/make -B buildkernel KERNCONF=LINT I'm fixing this one shortly and a few others. Just waiting for my make universe to complete. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On 2013-06-19 07:27, Tim Kientzle wrote: stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] /src/usr.bin/svn/lib/libapr/../../../../contrib/apr/include/apr_ring.h:183:34: note: expanded from macro 'APR_RING_PREV' #define APR_RING_PREV(ep, link) (ep)-link.prev ^ /src/usr.bin/svn/lib/libapr/../../../../contrib/apr/include/apr_ring.h:177:34: note: expanded from macro 'APR_RING_NEXT' #define APR_RING_NEXT(ep, link) (ep)-link.next ^ fatal error: too many errors emitted, stopping now [-ferror-limit=] 1 warning and 20 errors generated. *** Error code 1 Stop. make: stopped in /src/usr.bin/svn/lib/libapr *** Error code 1 This might be the OffsetOf bug for APR on ARM. We just got a fix pushed upstream for this a few days ago. I don't have time to look, but someone should take a peek at the following patch and see if it's needed: --- ./apr-1.4.7/include/apr_general.h.orig +++ ./apr-1.4.7/include/apr_general.h @@ -76,7 +76,7 @@ ·*·@return·offset ·*/ -#if·defined(CRAY)·||·(defined(__arm)··!defined(LINUX)) +#if·defined(CRAY)·||·(defined(__arm)··!(defined(LINUX)·||·defined(__FreeBSD__))) #ifdef·__STDC__ #define·APR_OFFSET(p_type,field)·_Offsetof(p_type,field) #else Sorry for the late reply, There is a new apr version on the way which contains the fix already, I suspect it will be released during the next days (if no show stopper is found) The following patch updates apr from 1.4.6 to 1.4.8 http://people.freebsd.org/~ohauer/diffs/apr-1.4.8.1.4.1.diff Would you mind to test the new version on the arm platform and run $ make test (as non priv. user) I have tested on 8.4 and 9.1 no 10-cur system available, tests do not run on redports because of system restrictions (jail). -- olli ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
This revision causing the issue http://freshbsd.org/commit/freebsd/r251856 I have to revert the revision to solve the issue On Tue, Jun 18, 2013 at 10:23 AM, FreeBSD Tinderbox tinder...@freebsd.orgwrote: TB --- 2013-06-17 22:50:17 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-17 22:50:17 - FreeBSD freebsd-current.sentex.ca8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-06-17 22:50:17 - starting HEAD tinderbox run for arm/arm TB --- 2013-06-17 22:50:17 - cleaning the object tree TB --- 2013-06-17 22:50:17 - /usr/local/bin/svn stat /src TB --- 2013-06-17 22:50:22 - At svn revision 251871 TB --- 2013-06-17 22:50:23 - building world TB --- 2013-06-17 22:50:23 - CROSS_BUILD_TESTING=YES TB --- 2013-06-17 22:50:23 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-17 22:50:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-17 22:50:23 - SRCCONF=/dev/null TB --- 2013-06-17 22:50:23 - TARGET=arm TB --- 2013-06-17 22:50:23 - TARGET_ARCH=arm TB --- 2013-06-17 22:50:23 - TZ=UTC TB --- 2013-06-17 22:50:23 - __MAKE_CONF=/dev/null TB --- 2013-06-17 22:50:23 - cd /src TB --- 2013-06-17 22:50:23 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Mon Jun 17 22:50:29 UTC 2013 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Tue Jun 18 01:50:36 UTC 2013 TB --- 2013-06-18 01:50:36 - generating LINT kernel config TB --- 2013-06-18 01:50:36 - cd /src/sys/arm/conf TB --- 2013-06-18 01:50:36 - /usr/bin/make -B LINT TB --- 2013-06-18 01:50:36 - cd /src/sys/arm/conf TB --- 2013-06-18 01:50:36 - /usr/sbin/config -m LINT TB --- 2013-06-18 01:50:36 - building LINT kernel TB --- 2013-06-18 01:50:36 - CROSS_BUILD_TESTING=YES TB --- 2013-06-18 01:50:36 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-18 01:50:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-18 01:50:36 - SRCCONF=/dev/null TB --- 2013-06-18 01:50:36 - TARGET=arm TB --- 2013-06-18 01:50:36 - TARGET_ARCH=arm TB --- 2013-06-18 01:50:36 - TZ=UTC TB --- 2013-06-18 01:50:36 - __MAKE_CONF=/dev/null TB --- 2013-06-18 01:50:36 - cd /src TB --- 2013-06-18 01:50:36 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Jun 18 01:50:36 UTC 2013 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for LINT completed on Tue Jun 18 02:13:19 UTC 2013 TB --- 2013-06-18 02:13:19 - cd /src/sys/arm/conf TB --- 2013-06-18 02:13:19 - /usr/sbin/config -m AC100 TB --- 2013-06-18 02:13:19 - skipping AC100 kernel TB --- 2013-06-18 02:13:19 - cd /src/sys/arm/conf TB --- 2013-06-18 02:13:19 - /usr/sbin/config -m ARMADAXP TB --- 2013-06-18 02:13:19 - skipping ARMADAXP kernel TB --- 2013-06-18 02:13:19 - cd /src/sys/arm/conf TB --- 2013-06-18 02:13:19 - /usr/sbin/config -m ATMEL TB --- 2013-06-18 02:13:19 - building ATMEL kernel TB --- 2013-06-18 02:13:19 - CROSS_BUILD_TESTING=YES TB --- 2013-06-18 02:13:19 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-18 02:13:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-18 02:13:19 - SRCCONF=/dev/null TB --- 2013-06-18 02:13:19 - TARGET=arm TB --- 2013-06-18 02:13:19 - TARGET_ARCH=arm TB --- 2013-06-18 02:13:19 - TZ=UTC TB --- 2013-06-18 02:13:19 - __MAKE_CONF=/dev/null TB --- 2013-06-18 02:13:19 - cd /src TB --- 2013-06-18 02:13:19 - /usr/bin/make -B buildkernel KERNCONF=ATMEL Kernel build for ATMEL started on Tue Jun 18 02:13:20 UTC 2013 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for ATMEL completed on Tue Jun 18 02:17:02 UTC 2013 TB --- 2013-06-18 02:17:02 - cd /src/sys/arm/conf TB --- 2013-06-18 02:17:02 - /usr/sbin/config -m AVILA TB --- 2013-06-18 02:17:02 - skipping AVILA kernel TB --- 2013-06-18 02:17:02 - cd /src/sys/arm/conf TB --- 2013-06-18 02:17:02 - /usr/sbin/config -m BEAGLEBONE TB --- 2013-06-18 02:17:02 - skipping BEAGLEBONE kernel TB --- 2013-06-18 02:17:02 - cd /src/sys/arm/conf TB --- 2013-06-18 02:17:02 - /usr/sbin/config -m BWCT TB --- 2013-06-18 02:17:02 - building BWCT kernel TB --- 2013-06-18 02:17:02 - CROSS_BUILD_TESTING=YES TB --- 2013-06-18 02:17:02 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-18 02:17:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-18 02:17:02 - SRCCONF=/dev/null TB --- 2013-06-18
Re: [head tinderbox] failure on arm/arm
stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] /src/usr.bin/svn/lib/libapr/../../../../contrib/apr/include/apr_ring.h:183:34: note: expanded from macro 'APR_RING_PREV' #define APR_RING_PREV(ep, link) (ep)-link.prev ^ /src/usr.bin/svn/lib/libapr/../../../../contrib/apr/include/apr_ring.h:177:34: note: expanded from macro 'APR_RING_NEXT' #define APR_RING_NEXT(ep, link) (ep)-link.next ^ fatal error: too many errors emitted, stopping now [-ferror-limit=] 1 warning and 20 errors generated. *** Error code 1 Stop. make: stopped in /src/usr.bin/svn/lib/libapr *** Error code 1 This might be the OffsetOf bug for APR on ARM. We just got a fix pushed upstream for this a few days ago. I don't have time to look, but someone should take a peek at the following patch and see if it's needed: --- ./apr-1.4.7/include/apr_general.h.orig +++ ./apr-1.4.7/include/apr_general.h @@ -76,7 +76,7 @@ ·*·@return·offset ·*/ -#if·defined(CRAY)·||·(defined(__arm)··!defined(LINUX)) +#if·defined(CRAY)·||·(defined(__arm)··!(defined(LINUX)·||·defined(__FreeBSD__))) #ifdef·__STDC__ #define·APR_OFFSET(p_type,field)·_Offsetof(p_type,field) #else ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
sbruno already fixed this. Glen On Sun, Mar 24, 2013 at 02:48:39AM +, FreeBSD Tinderbox wrote: [...] pgphY5LCEEuwB.pgp Description: PGP signature
Re: [head tinderbox] failure on arm/arm
Fixed! Adrian On 8 March 2013 20:18, FreeBSD Tinderbox tinder...@freebsd.org wrote: TB --- 2013-03-09 01:30:17 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-09 01:30:17 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-03-09 01:30:17 - starting HEAD tinderbox run for arm/arm TB --- 2013-03-09 01:30:17 - cleaning the object tree TB --- 2013-03-09 01:30:17 - /usr/local/bin/svn stat /src TB --- 2013-03-09 01:30:21 - At svn revision 248079 TB --- 2013-03-09 01:30:22 - building world TB --- 2013-03-09 01:30:22 - CROSS_BUILD_TESTING=YES TB --- 2013-03-09 01:30:22 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-09 01:30:22 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-09 01:30:22 - SRCCONF=/dev/null TB --- 2013-03-09 01:30:22 - TARGET=arm TB --- 2013-03-09 01:30:22 - TARGET_ARCH=arm TB --- 2013-03-09 01:30:22 - TZ=UTC TB --- 2013-03-09 01:30:22 - __MAKE_CONF=/dev/null TB --- 2013-03-09 01:30:22 - cd /src TB --- 2013-03-09 01:30:22 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sat Mar 9 01:30:26 UTC 2013 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Sat Mar 9 03:19:43 UTC 2013 TB --- 2013-03-09 03:19:43 - generating LINT kernel config TB --- 2013-03-09 03:19:43 - cd /src/sys/arm/conf TB --- 2013-03-09 03:19:43 - /usr/bin/make -B LINT TB --- 2013-03-09 03:19:44 - cd /src/sys/arm/conf TB --- 2013-03-09 03:19:44 - /usr/sbin/config -m LINT TB --- 2013-03-09 03:19:44 - building LINT kernel TB --- 2013-03-09 03:19:44 - CROSS_BUILD_TESTING=YES TB --- 2013-03-09 03:19:44 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-09 03:19:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-09 03:19:44 - SRCCONF=/dev/null TB --- 2013-03-09 03:19:44 - TARGET=arm TB --- 2013-03-09 03:19:44 - TARGET_ARCH=arm TB --- 2013-03-09 03:19:44 - TZ=UTC TB --- 2013-03-09 03:19:44 - __MAKE_CONF=/dev/null TB --- 2013-03-09 03:19:44 - cd /src TB --- 2013-03-09 03:19:44 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Sat Mar 9 03:19:44 UTC 2013 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for LINT completed on Sat Mar 9 03:39:30 UTC 2013 TB --- 2013-03-09 03:39:30 - cd /src/sys/arm/conf TB --- 2013-03-09 03:39:30 - /usr/sbin/config -m AC100 TB --- 2013-03-09 03:39:30 - skipping AC100 kernel TB --- 2013-03-09 03:39:30 - cd /src/sys/arm/conf TB --- 2013-03-09 03:39:30 - /usr/sbin/config -m ARMADAXP TB --- 2013-03-09 03:39:30 - skipping ARMADAXP kernel TB --- 2013-03-09 03:39:30 - cd /src/sys/arm/conf TB --- 2013-03-09 03:39:30 - /usr/sbin/config -m ATMEL TB --- 2013-03-09 03:39:30 - building ATMEL kernel TB --- 2013-03-09 03:39:30 - CROSS_BUILD_TESTING=YES TB --- 2013-03-09 03:39:30 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-09 03:39:30 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-09 03:39:30 - SRCCONF=/dev/null TB --- 2013-03-09 03:39:30 - TARGET=arm TB --- 2013-03-09 03:39:30 - TARGET_ARCH=arm TB --- 2013-03-09 03:39:30 - TZ=UTC TB --- 2013-03-09 03:39:30 - __MAKE_CONF=/dev/null TB --- 2013-03-09 03:39:30 - cd /src TB --- 2013-03-09 03:39:30 - /usr/bin/make -B buildkernel KERNCONF=ATMEL Kernel build for ATMEL started on Sat Mar 9 03:39:30 UTC 2013 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for ATMEL completed on Sat Mar 9 03:43:34 UTC 2013 TB --- 2013-03-09 03:43:34 - cd /src/sys/arm/conf TB --- 2013-03-09 03:43:34 - /usr/sbin/config -m AVILA TB --- 2013-03-09 03:43:34 - skipping AVILA kernel TB --- 2013-03-09 03:43:34 - cd /src/sys/arm/conf TB --- 2013-03-09 03:43:34 - /usr/sbin/config -m BEAGLEBONE TB --- 2013-03-09 03:43:34 - skipping BEAGLEBONE kernel TB --- 2013-03-09 03:43:34 - cd /src/sys/arm/conf TB --- 2013-03-09 03:43:34 - /usr/sbin/config -m BWCT TB --- 2013-03-09 03:43:34 - building BWCT kernel TB --- 2013-03-09 03:43:34 - CROSS_BUILD_TESTING=YES TB --- 2013-03-09 03:43:34 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-09 03:43:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-09 03:43:34 - SRCCONF=/dev/null TB --- 2013-03-09 03:43:34 - TARGET=arm TB --- 2013-03-09 03:43:34 - TARGET_ARCH=arm TB --- 2013-03-09 03:43:34 - TZ=UTC TB --- 2013-03-09 03:43:34 -
Re: [head tinderbox] failure on arm/arm
On Friday, November 09, 2012 05:47:43 PM Adrian Chadd wrote: On 9 November 2012 14:37, Chuck Burns brea...@gmail.com wrote: Adrian. diskspace and cpu cycles are things I can spare, drop me a line outside of the ML and we can discuss particulars. It's just a personal box.. on a residential internet service, I have an amd64 box with 600G free on my pool.. 8G ram.. and I have a smaller i386 box... 100G or so free, 512M ram.. just drop me a line.. Hi, Those I do have - I have access to all of the ref* boxes in the cluster. I'm just typically hacking on this stuff on the train or at a cafe, and I don't have a workflow setup for pushing out potential diffs to build machines that have all the grunt/disk space for each little change that I do. I'm sorry about breaking things from time to time, but besides a small handful of what was I thinking?! things, the build breaks are just that - build breaks. They're easily fixed. This is why I use p4 branches. I hack on my laptop and then commit it to p4 and use 'p4 sync' as a glorified rsync on development hosts. I can then do a full 'make tinderbox' before committing to HEAD after extracting the patches from p4 and applying them to an SVN checkout. SVN branches should let you do something similar as well (or just about any soure code control system you choose to use). -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
from Brett brett.ma...@gmx.com: Just an observation: a few years ago when I got sick of Linux's headlong rush development model, I subscribed to various BSD mailing lists to see what +else was out there. I considered FreeBSD at the time - there was a neverending avalanche of [head tinderbox] failure messages. This told me that I would +be more likely to be running code written by people who knew what they were doing if I went with Open, Net, or DragonflyBSD. I safely run OpenBSD-current on my main computer and it always works (I think I have had 2-3 build problems in about 3 years, and they were all my fault). At the moment, I only feel confident enough with FreeBSD-current to run it on my unimportant torrent computer. This is 80% due to constant build failures, and 20% due to invasive changes being introduced with documentation/instructions scattered over many different pages and mailing lists, e.g: http://wiki.freebsd.org/FrontPage?action=fullsearchcontext=180value=xorgtitlesearch=Titles http://wiki.freebsd.org/FrontPage?action=fullsearchcontext=180value=pkgngtitlesearch=Titles Hypothetical user: Is it WITHOUT_PKGNG= or WITHOUT_PKGNG=yes or WITH_PKGNG=no today? I wonder how many other people that you never hear from feel the same, and if some sort of x weeks commit freezeout should apply to the build breakers. Cute pointy hats or whatever obviously have no effect. Rant over! I too had monstrous problems rebuilding all ports that depend on png. But I am not really satisfied with the other BSDs. NetBSD is hit-or-miss to build successfully, more miss than hit. NetBSD supports GPT awkwardly but has no support for USB 3.0. NetBSD is rather unstable. I think I'd trust FreeBSD-current over a stable or release version of NetBSD. How does OpenBSD compare in that regard? I think DragonFlyBSD just introduced USB 3.0 support in 3.2.1, but that is off by default. There are live USB images available for DragonflyBSD from www.dragonflybsd.org, and live USB images available for OpenBSD at liveusb-openbsd.sourceforge.net . I'd like to try, just to see what they look like and how or if they support my hardware. Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On 2012-Nov-10 09:16:32 +1100, Brett brett.ma...@gmx.com wrote: Just an observation: a few years ago when I got sick of Linux's headlong rush development model, I subscribed to various BSD mailing lists to see what else was out there. I considered FreeBSD at the time - there was a neverending avalanche of [head tinderbox] failure messages. The Project tries to avoid it but occasional build failures on the development branch are very likely to occur. As a new user, you would be much better off starting with a release branch. This told me that I would be more likely to be running code written by people who knew what they were doing if I went with Open, Net, or DragonflyBSD. I think that's being unfair. Do Open, Net or DFly have an equivalent to the tinderboxes that do automated test builds and report failures? And, since you have replied to an ARM failure, DragonflyBSD would not be an option since it doesn't support ARM. -- Peter Jeremy pgpggt7LmRYN1.pgp Description: PGP signature
Re: [head tinderbox] failure on arm/arm
NetBSD is hit-or-miss to build successfully, more miss than hit. NetBSD supports GPT awkwardly but has no support for USB 3.0. NetBSD is rather unstable. I think I'd trust FreeBSD-current over a stable or release version of NetBSD. How does OpenBSD compare in that regard? I think DragonFlyBSD just introduced USB 3.0 support in 3.2.1, but that is off by default. There are live USB images available for DragonflyBSD from www.dragonflybsd.org, and live USB images available for OpenBSD at liveusb-openbsd.sourceforge.net . I'd like to try, just to see what they look like and how or if they support my hardware. Tom I haven't used NetBSD for a while. OpenBSD (both current and release) are very stable and predictable. Totally trustworthy. The six month release cycle seems to encourage incremental change. The lack of multiple branches means its a lot easier for developers and porters to stay on top of things. FreeBSD has more new features (such as the USB 3.0 you mentioned), also more support for other hardware tweakables (e.g. more Intel CPU power saving modes). I've only briefly used DragonflyBSD but plan to get it cranking again on one of my machines soon. The release version I tried before seemed pretty solid and gave good (desktop) performance. Its interesting to look at the relative strengths and weaknesses of each, how they've evolved, and hopefully learn some more. Brett. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On Sat, 10 Nov 2012 23:34:24 +1100 Peter Jeremy pe...@rulingia.com wrote: On 2012-Nov-10 09:16:32 +1100, Brett brett.ma...@gmx.com wrote: Just an observation: a few years ago when I got sick of Linux's headlong rush development model, I subscribed to various BSD mailing lists to see what else was out there. I considered FreeBSD at the time - there was a neverending avalanche of [head tinderbox] failure messages. The Project tries to avoid it but occasional build failures on the development branch are very likely to occur. As a new user, you would be much better off starting with a release branch. I used 9.0 and release candidates for a couple of months beforehand so i would know what usually works and doesn't work before, trying current out. Compared to many of the old timers out there I guess this makes me very new still, though! This told me that I would be more likely to be running code written by people who knew what they were doing if I went with Open, Net, or DragonflyBSD. I think that's being unfair. Do Open, Net or DFly have an equivalent to the tinderboxes that do automated test builds and report failures? And, since you have replied to an ARM failure, DragonflyBSD would not be an option since it doesn't support ARM. The point I was trying to make (context lost in the partial quote above) was not that it is better or worse than the other BSDs, but that at the time (maybe 3 years ago) when I was looking around to alternatives to Linux and reading the various mailing lists, this was the impression I got. I am sure other people must see these daily failures and get the same impression. Whether this is fair or not has nothing to do with what impressions people form, and what OS they subsequently decide to install. As I recall reading, the tinderbox was established due to the high incidence of build failures. In my original post on this thread, I was commenting not on the failure of ARM build in particular, but chiming in after Doug Brewer's request for the code to be tested before being committed. If anyone else had backed him up I would not have felt the need to write. Cheers, Brett. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
Chuck Burns wrote: On 11/9/2012 4:16 PM, Brett wrote: Message: 11 Date: Fri, 9 Nov 2012 23:34:58 +0800 From: Doug Brewer brewer.d...@gmail.com To: Adrian Chadd adr...@freebsd.org Cc: a...@freebsd.org, FreeBSD Tinderbox tinder...@freebsd.org, curr...@freebsd.org Subject: Re: [head tinderbox] failure on arm/arm Message-ID: cag0v13tpalmdpg-8rifcjjroxz948mqzjnn1yvqz4teybjz...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 No offence, but how many times did you break the build? Could you please compile your code before committing next time? Thanks a lot! Just an observation: a few years ago when I got sick of Linux's headlong rush development model, I subscribed to various BSD mailing lists to see what else was out there. I considered FreeBSD at the time - there was a neverending avalanche of [head tinderbox] failure messages. This told me that I would be more likely to be running code written by people who knew what they were doing if I went with Open, Net, or DragonflyBSD. I safely run OpenBSD-current on my main computer and it always works (I think I have had 2-3 build problems in about 3 years, and they were all my fault). At the moment, I only feel confident enough with FreeBSD-current to run it on my unimportant torrent computer. This is 80% due to constant build failures, and 20% due to invasive changes being introduced with documentation/instructions scattered over many different pages and mailing lists, e.g: http://wiki.freebsd.org/FrontPage?action=fullsearchcontext=180value=xorgtitlesearch=Titles http://wiki.freebsd.org/FrontPage?action=fullsearchcontext=180value=pkgngtitlesearch=Titles Hypothetical user: Is it WITHOUT_PKGNG= or WITHOUT_PKGNG=yes or WITH_PKGNG=no today? I wonder how many other people that you never hear from feel the same, and if some sort of x weeks commit freezeout should apply to the build breakers. Cute pointy hats or whatever obviously have no effect. Rant over! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Quite honestly, the head/current branch is going to have build failures.. It's the test bed.. YOU'VE GOTTA BE KIDDING ME. Stick with the release system unless you want cutting edge.. just remember.. cutting edge cuts sometimes... ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On 10 November 2012 07:10, Doug Brewer brewer.d...@gmail.com wrote: Adrian Chadd wrote: On 9 November 2012 14:37, Chuck Burns brea...@gmail.com wrote: Adrian. diskspace and cpu cycles are things I can spare, drop me a line outside of the ML and we can discuss particulars. It's just a personal box.. on a residential internet service, I have an amd64 box with 600G free on my pool.. 8G ram.. and I have a smaller i386 box... 100G or so free, 512M ram.. just drop me a line.. Hi, Those I do have - I have access to all of the ref* boxes in the cluster. I'm just typically hacking on this stuff on the train or at a cafe, and I don't have a workflow setup for pushing out potential diffs to build machines that have all the grunt/disk space for each little change that I do. Wait wait wait. It makes me wonder if you get the patch tested well on the train or at a cafe before being committed. I tend to have a _lot_ of FreeBSD devices on me. People who have seen me hack can attest to this. I'm sorry about breaking things from time to time, but besides a small handful of what was I thinking?! things, the build breaks are just that - build breaks. They're easily fixed. I do not care how things are easily fixed. Remember, when Sam Leffler was the maintainer of ath and CAMBRIA board (it's an embedded device, right?), he had never broke the build. He's better than I? :) adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
Adrian Chadd wrote: On 9 November 2012 14:37, Chuck Burns brea...@gmail.com wrote: Adrian. diskspace and cpu cycles are things I can spare, drop me a line outside of the ML and we can discuss particulars. It's just a personal box.. on a residential internet service, I have an amd64 box with 600G free on my pool.. 8G ram.. and I have a smaller i386 box... 100G or so free, 512M ram.. just drop me a line.. Hi, Those I do have - I have access to all of the ref* boxes in the cluster. I'm just typically hacking on this stuff on the train or at a cafe, and I don't have a workflow setup for pushing out potential diffs to build machines that have all the grunt/disk space for each little change that I do. Wait wait wait. It makes me wonder if you get the patch tested well on the train or at a cafe before being committed. I'm sorry about breaking things from time to time, but besides a small handful of what was I thinking?! things, the build breaks are just that - build breaks. They're easily fixed. I do not care how things are easily fixed. Remember, when Sam Leffler was the maintainer of ath and CAMBRIA board (it's an embedded device, right?), he had never broke the build. Adrian BR, Doug. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[OT] Re: [head tinderbox] failure on arm/arm
On Sat, 10 Nov 2012 08:03:00 -0800 Adrian Chadd adr...@freebsd.org wrote: On 10 November 2012 07:10, Doug Brewer brewer.d...@gmail.com wrote: Adrian Chadd wrote: On 9 November 2012 14:37, Chuck Burns brea...@gmail.com wrote: Adrian. diskspace and cpu cycles are things I can spare, drop me a line outside of the ML and we can discuss particulars. It's just a personal box.. on a residential internet service, I have an amd64 box with 600G free on my pool.. 8G ram.. and I have a smaller i386 box... 100G or so free, 512M ram.. just drop me a line.. Hi, Those I do have - I have access to all of the ref* boxes in the cluster. I'm just typically hacking on this stuff on the train or at a cafe, and I don't have a workflow setup for pushing out potential diffs to build machines that have all the grunt/disk space for each little change that I do. Wait wait wait. It makes me wonder if you get the patch tested well on the train or at a cafe before being committed. I tend to have a _lot_ of FreeBSD devices on me. People who have seen me hack can attest to this. I'm sorry about breaking things from time to time, but besides a small handful of what was I thinking?! things, the build breaks are just that - build breaks. They're easily fixed. I do not care how things are easily fixed. Remember, when Sam Leffler was the maintainer of ath and CAMBRIA board (it's an embedded device, right?), he had never broke the build. He's better than I? :) funny... there is no angry letters about 100500 letters from tb after switch to clang... but when Adrian break build [again] we have it... Adrian, thanks for your work. No need to be offended by trolls adrian -- wbr, tiger ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On Sat, Nov 10, 2012 at 4:54 AM, Brett brett.ma...@gmx.com wrote: On Sat, 10 Nov 2012 23:34:24 +1100 Peter Jeremy pe...@rulingia.com wrote: On 2012-Nov-10 09:16:32 +1100, Brett brett.ma...@gmx.com wrote: Just an observation: a few years ago when I got sick of Linux's headlong rush development model, I subscribed to various BSD mailing lists to see what else was out there. I considered FreeBSD at the time - there was a neverending avalanche of [head tinderbox] failure messages. The Project tries to avoid it but occasional build failures on the development branch are very likely to occur. As a new user, you would be much better off starting with a release branch. I used 9.0 and release candidates for a couple of months beforehand so i would know what usually works and doesn't work before, trying current out. Compared to many of the old timers out there I guess this makes me very new still, though! This told me that I would be more likely to be running code written by people who knew what they were doing if I went with Open, Net, or DragonflyBSD. I think that's being unfair. Do Open, Net or DFly have an equivalent to the tinderboxes that do automated test builds and report failures? And, since you have replied to an ARM failure, DragonflyBSD would not be an option since it doesn't support ARM. The point I was trying to make (context lost in the partial quote above) was not that it is better or worse than the other BSDs, but that at the time (maybe 3 years ago) when I was looking around to alternatives to Linux and reading the various mailing lists, this was the impression I got. I am sure other people must see these daily failures and get the same impression. Whether this is fair or not has nothing to do with what impressions people form, and what OS they subsequently decide to install. As I recall reading, the tinderbox was established due to the high incidence of build failures. In my original post on this thread, I was commenting not on the failure of ARM build in particular, but chiming in after Doug Brewer's request for the code to be tested before being committed. If anyone else had backed him up I would not have felt the need to write. We heard your concerns loud and clear; there are several developers that understand your concerns well and we're shooting for build stability now (it's easy to achieve) and runtime stability as well (considerably harder because the automated infrastructure isn't in place yet to run smoke tests to verify that all commits are sane -- but hopefully that's coming sometime in the near future ;)...). So, as I said before, 1) let's come up with a proper solution that we can pilot (even if it's a prototype) to extend tinderbox to allow developers to toss code over the fence (branches/patches?) in order to get build results before it hits the tree (Chuck offered the hardware.. someone needs to offer the time to come up with a submit/receive mechanism) and 2) come up with a proper test environment so we can avoid regressions like this as well as the slew of clang related TB failures that are still being fixed. Thanks! -Garrett PS Adrian is doing good work out-of-band (not work related), so let's work with him in order to make his life easier -- not harder by stating the obvious and bikeshedding him to death. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [OT] Re: [head tinderbox] failure on arm/arm
It's a valid concern. I need to pick up my game. Adrian On 10 November 2012 08:26, Sergey V. Dyatko sergey.dya...@gmail.com wrote: On Sat, 10 Nov 2012 08:03:00 -0800 Adrian Chadd adr...@freebsd.org wrote: On 10 November 2012 07:10, Doug Brewer brewer.d...@gmail.com wrote: Adrian Chadd wrote: On 9 November 2012 14:37, Chuck Burns brea...@gmail.com wrote: Adrian. diskspace and cpu cycles are things I can spare, drop me a line outside of the ML and we can discuss particulars. It's just a personal box.. on a residential internet service, I have an amd64 box with 600G free on my pool.. 8G ram.. and I have a smaller i386 box... 100G or so free, 512M ram.. just drop me a line.. Hi, Those I do have - I have access to all of the ref* boxes in the cluster. I'm just typically hacking on this stuff on the train or at a cafe, and I don't have a workflow setup for pushing out potential diffs to build machines that have all the grunt/disk space for each little change that I do. Wait wait wait. It makes me wonder if you get the patch tested well on the train or at a cafe before being committed. I tend to have a _lot_ of FreeBSD devices on me. People who have seen me hack can attest to this. I'm sorry about breaking things from time to time, but besides a small handful of what was I thinking?! things, the build breaks are just that - build breaks. They're easily fixed. I do not care how things are easily fixed. Remember, when Sam Leffler was the maintainer of ath and CAMBRIA board (it's an embedded device, right?), he had never broke the build. He's better than I? :) funny... there is no angry letters about 100500 letters from tb after switch to clang... but when Adrian break build [again] we have it... Adrian, thanks for your work. No need to be offended by trolls adrian -- wbr, tiger ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
No offence, but how many times did you break the build? Could you please compile your code before committing next time? Thanks a lot! On Fri, Nov 9, 2012 at 7:13 AM, Adrian Chadd adr...@freebsd.org wrote: Fixed, sorry! adrian On 8 November 2012 15:03, FreeBSD Tinderbox tinder...@freebsd.org wrote: TB --- 2012-11-08 21:30:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-08 21:30:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-08 21:30:00 - starting HEAD tinderbox run for arm/arm TB --- 2012-11-08 21:30:00 - cleaning the object tree TB --- 2012-11-08 21:30:00 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-08 21:30:00 - cd /tinderbox/HEAD/arm/arm TB --- 2012-11-08 21:30:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-08 21:31:52 - /usr/local/bin/svn update /src TB --- 2012-11-08 21:32:01 - At svn revision 242793 TB --- 2012-11-08 21:32:02 - building world TB --- 2012-11-08 21:32:02 - CROSS_BUILD_TESTING=YES TB --- 2012-11-08 21:32:02 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-08 21:32:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-08 21:32:02 - SRCCONF=/dev/null TB --- 2012-11-08 21:32:02 - TARGET=arm TB --- 2012-11-08 21:32:02 - TARGET_ARCH=arm TB --- 2012-11-08 21:32:02 - TZ=UTC TB --- 2012-11-08 21:32:02 - __MAKE_CONF=/dev/null TB --- 2012-11-08 21:32:02 - cd /src TB --- 2012-11-08 21:32:02 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Nov 8 21:32:09 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Thu Nov 8 22:32:33 UTC 2012 TB --- 2012-11-08 22:32:33 - cd /src/sys/arm/conf TB --- 2012-11-08 22:32:33 - /usr/sbin/config -m AC100 TB --- 2012-11-08 22:32:33 - skipping AC100 kernel TB --- 2012-11-08 22:32:33 - cd /src/sys/arm/conf TB --- 2012-11-08 22:32:33 - /usr/sbin/config -m ARMADAXP TB --- 2012-11-08 22:32:33 - skipping ARMADAXP kernel TB --- 2012-11-08 22:32:33 - cd /src/sys/arm/conf TB --- 2012-11-08 22:32:33 - /usr/sbin/config -m ATMEL TB --- 2012-11-08 22:32:34 - building ATMEL kernel TB --- 2012-11-08 22:32:34 - CROSS_BUILD_TESTING=YES TB --- 2012-11-08 22:32:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-08 22:32:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-08 22:32:34 - SRCCONF=/dev/null TB --- 2012-11-08 22:32:34 - TARGET=arm TB --- 2012-11-08 22:32:34 - TARGET_ARCH=arm TB --- 2012-11-08 22:32:34 - TZ=UTC TB --- 2012-11-08 22:32:34 - __MAKE_CONF=/dev/null TB --- 2012-11-08 22:32:34 - cd /src TB --- 2012-11-08 22:32:34 - /usr/bin/make -B buildkernel KERNCONF=ATMEL Kernel build for ATMEL started on Thu Nov 8 22:32:34 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for ATMEL completed on Thu Nov 8 22:36:09 UTC 2012 TB --- 2012-11-08 22:36:09 - cd /src/sys/arm/conf TB --- 2012-11-08 22:36:09 - /usr/sbin/config -m AVILA TB --- 2012-11-08 22:36:09 - skipping AVILA kernel TB --- 2012-11-08 22:36:09 - cd /src/sys/arm/conf TB --- 2012-11-08 22:36:09 - /usr/sbin/config -m BEAGLEBONE TB --- 2012-11-08 22:36:09 - skipping BEAGLEBONE kernel TB --- 2012-11-08 22:36:09 - cd /src/sys/arm/conf TB --- 2012-11-08 22:36:09 - /usr/sbin/config -m BWCT TB --- 2012-11-08 22:36:09 - building BWCT kernel TB --- 2012-11-08 22:36:09 - CROSS_BUILD_TESTING=YES TB --- 2012-11-08 22:36:09 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-08 22:36:09 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-08 22:36:09 - SRCCONF=/dev/null TB --- 2012-11-08 22:36:09 - TARGET=arm TB --- 2012-11-08 22:36:09 - TARGET_ARCH=arm TB --- 2012-11-08 22:36:09 - TZ=UTC TB --- 2012-11-08 22:36:09 - __MAKE_CONF=/dev/null TB --- 2012-11-08 22:36:09 - cd /src TB --- 2012-11-08 22:36:09 - /usr/bin/make -B buildkernel KERNCONF=BWCT Kernel build for BWCT started on Thu Nov 8 22:36:09 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for BWCT completed on Thu Nov 8 22:38:19 UTC 2012 TB --- 2012-11-08 22:38:19 - cd /src/sys/arm/conf TB --- 2012-11-08 22:38:19 - /usr/sbin/config -m CAMBRIA TB --- 2012-11-08 22:38:19 - skipping CAMBRIA kernel TB --- 2012-11-08 22:38:19 - cd /src/sys/arm/conf TB --- 2012-11-08 22:38:19 - /usr/sbin/config -m CNS11XXNAS
Re: [head tinderbox] failure on arm/arm
On Fri, Nov 9, 2012 at 7:34 AM, Doug Brewer brewer.d...@gmail.com wrote: No offence, but how many times did you break the build? Could you please compile your code before committing next time? Thanks a lot! make tinderbox is the important point here because it uses different compile time options and flags that Adrian doesn't probably have set in his KERNCONF -- assuming that the default KERNCONFs haven't been mangled on his system, in which case it messes up this statement; [un]fortunately someone can change GENERIC, etc on his/her box, run make tinderbox and have it pass, then . In which case I would recommend the following [just to be safe]: 1. Custom KERNCONF that includes a generic one. 2. make tinderbox -DMAKE_JUST_KERNELS before performing commits with just ARM/x86 and a select KERNCONF as a smoke test, and a more extensive make tinderbox when doing a more major commit. Thoughts? Thanks! -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On 9 November 2012 07:34, Doug Brewer brewer.d...@gmail.com wrote: No offence, but how many times did you break the build? Could you please compile your code before committing next time? Thanks a lot! I'm implementing a cut-down version of make universe on my development laptop. It unfortunately is slightly too small to run make universe at the moment; I do a lot of development on netbooks with small amounts of RAM and disk. My cut-down version is likely going to be oh, and cross build a test MIPS kernel or two that doesn't actually set ATH_DEBUG* options by default. So I'm sorry about this; it'll get resolved soon. Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
Message: 11 Date: Fri, 9 Nov 2012 23:34:58 +0800 From: Doug Brewer brewer.d...@gmail.com To: Adrian Chadd adr...@freebsd.org Cc: a...@freebsd.org, FreeBSD Tinderbox tinder...@freebsd.org, curr...@freebsd.org Subject: Re: [head tinderbox] failure on arm/arm Message-ID: cag0v13tpalmdpg-8rifcjjroxz948mqzjnn1yvqz4teybjz...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 No offence, but how many times did you break the build? Could you please compile your code before committing next time? Thanks a lot! Just an observation: a few years ago when I got sick of Linux's headlong rush development model, I subscribed to various BSD mailing lists to see what else was out there. I considered FreeBSD at the time - there was a neverending avalanche of [head tinderbox] failure messages. This told me that I would be more likely to be running code written by people who knew what they were doing if I went with Open, Net, or DragonflyBSD. I safely run OpenBSD-current on my main computer and it always works (I think I have had 2-3 build problems in about 3 years, and they were all my fault). At the moment, I only feel confident enough with FreeBSD-current to run it on my unimportant torrent computer. This is 80% due to constant build failures, and 20% due to invasive changes being introduced with documentation/instructions scattered over many different pages and mailing lists, e.g: http://wiki.freebsd.org/FrontPage?action=fullsearchcontext=180value=xorgtitlesearch=Titles http://wiki.freebsd.org/FrontPage?action=fullsearchcontext=180value=pkgngtitlesearch=Titles Hypothetical user: Is it WITHOUT_PKGNG= or WITHOUT_PKGNG=yes or WITH_PKGNG=no today? I wonder how many other people that you never hear from feel the same, and if some sort of x weeks commit freezeout should apply to the build breakers. Cute pointy hats or whatever obviously have no effect. Rant over! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On 11/9/2012 3:20 PM, Adrian Chadd wrote: On 9 November 2012 07:34, Doug Brewer brewer.d...@gmail.com wrote: No offence, but how many times did you break the build? Could you please compile your code before committing next time? Thanks a lot! I'm implementing a cut-down version of make universe on my development laptop. It unfortunately is slightly too small to run make universe at the moment; I do a lot of development on netbooks with small amounts of RAM and disk. My cut-down version is likely going to be oh, and cross build a test MIPS kernel or two that doesn't actually set ATH_DEBUG* options by default. So I'm sorry about this; it'll get resolved soon. Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Adrian. diskspace and cpu cycles are things I can spare, drop me a line outside of the ML and we can discuss particulars. It's just a personal box.. on a residential internet service, I have an amd64 box with 600G free on my pool.. 8G ram.. and I have a smaller i386 box... 100G or so free, 512M ram.. just drop me a line.. -- Chuck Burns brea...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On 11/9/2012 4:16 PM, Brett wrote: Message: 11 Date: Fri, 9 Nov 2012 23:34:58 +0800 From: Doug Brewer brewer.d...@gmail.com To: Adrian Chadd adr...@freebsd.org Cc: a...@freebsd.org, FreeBSD Tinderbox tinder...@freebsd.org, curr...@freebsd.org Subject: Re: [head tinderbox] failure on arm/arm Message-ID: cag0v13tpalmdpg-8rifcjjroxz948mqzjnn1yvqz4teybjz...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 No offence, but how many times did you break the build? Could you please compile your code before committing next time? Thanks a lot! Just an observation: a few years ago when I got sick of Linux's headlong rush development model, I subscribed to various BSD mailing lists to see what else was out there. I considered FreeBSD at the time - there was a neverending avalanche of [head tinderbox] failure messages. This told me that I would be more likely to be running code written by people who knew what they were doing if I went with Open, Net, or DragonflyBSD. I safely run OpenBSD-current on my main computer and it always works (I think I have had 2-3 build problems in about 3 years, and they were all my fault). At the moment, I only feel confident enough with FreeBSD-current to run it on my unimportant torrent computer. This is 80% due to constant build failures, and 20% due to invasive changes being introduced with documentation/instructions scattered over many different pages and mailing lists, e.g: http://wiki.freebsd.org/FrontPage?action=fullsearchcontext=180value=xorgtitlesearch=Titles http://wiki.freebsd.org/FrontPage?action=fullsearchcontext=180value=pkgngtitlesearch=Titles Hypothetical user: Is it WITHOUT_PKGNG= or WITHOUT_PKGNG=yes or WITH_PKGNG=no today? I wonder how many other people that you never hear from feel the same, and if some sort of x weeks commit freezeout should apply to the build breakers. Cute pointy hats or whatever obviously have no effect. Rant over! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Quite honestly, the head/current branch is going to have build failures.. It's the test bed.. Stick with the release system unless you want cutting edge.. just remember.. cutting edge cuts sometimes... -- Chuck Burns brea...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On 9 November 2012 14:37, Chuck Burns brea...@gmail.com wrote: Adrian. diskspace and cpu cycles are things I can spare, drop me a line outside of the ML and we can discuss particulars. It's just a personal box.. on a residential internet service, I have an amd64 box with 600G free on my pool.. 8G ram.. and I have a smaller i386 box... 100G or so free, 512M ram.. just drop me a line.. Hi, Those I do have - I have access to all of the ref* boxes in the cluster. I'm just typically hacking on this stuff on the train or at a cafe, and I don't have a workflow setup for pushing out potential diffs to build machines that have all the grunt/disk space for each little change that I do. I'm sorry about breaking things from time to time, but besides a small handful of what was I thinking?! things, the build breaks are just that - build breaks. They're easily fixed. Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
No offence, but how many times did you break the build? Could you please compile your code before committing next time? Thanks a lot! Just an observation: a few years ago when I got sick of Linux's headlong rush development model, I subscribed to various BSD mailing lists to see what else was out there. I considered FreeBSD at the time - there was a neverending avalanche of [head tinderbox] failure messages. This told me that I would be more likely to be running code written by people who knew what they were doing if I went with Open, Net, or DragonflyBSD. Quite honestly, the head/current branch is going to have build failures.. It's the test bed.. Stick with the release system unless you want cutting edge.. just remember.. cutting edge cuts sometimes... In the context of this thread, 'test bed' could mean anything. To clarify, are you saying: a) You think it is ok for commits to be made to the head source code, that cause it to not compile. b) Anyone who disagrees with this should be running release, not current. The head branch is distributed around the world by a network of mirror sites, and then downloaded and compiled by a large number of people. It seems a very inefficient use of resources for this infrastructure to be used to see if some code will build. Would it not be more useful for current to be a test bed of bugfixes and new features, rather than directing users to a release and having current as a test bed for will this compile? Or I suppose we could all just wait 6 months for a release candidate to see if today's current has introduced any regressions on our hardware. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
Fixed, sorry! adrian On 8 November 2012 15:03, FreeBSD Tinderbox tinder...@freebsd.org wrote: TB --- 2012-11-08 21:30:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-08 21:30:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-08 21:30:00 - starting HEAD tinderbox run for arm/arm TB --- 2012-11-08 21:30:00 - cleaning the object tree TB --- 2012-11-08 21:30:00 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-08 21:30:00 - cd /tinderbox/HEAD/arm/arm TB --- 2012-11-08 21:30:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-08 21:31:52 - /usr/local/bin/svn update /src TB --- 2012-11-08 21:32:01 - At svn revision 242793 TB --- 2012-11-08 21:32:02 - building world TB --- 2012-11-08 21:32:02 - CROSS_BUILD_TESTING=YES TB --- 2012-11-08 21:32:02 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-08 21:32:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-08 21:32:02 - SRCCONF=/dev/null TB --- 2012-11-08 21:32:02 - TARGET=arm TB --- 2012-11-08 21:32:02 - TARGET_ARCH=arm TB --- 2012-11-08 21:32:02 - TZ=UTC TB --- 2012-11-08 21:32:02 - __MAKE_CONF=/dev/null TB --- 2012-11-08 21:32:02 - cd /src TB --- 2012-11-08 21:32:02 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Thu Nov 8 21:32:09 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Thu Nov 8 22:32:33 UTC 2012 TB --- 2012-11-08 22:32:33 - cd /src/sys/arm/conf TB --- 2012-11-08 22:32:33 - /usr/sbin/config -m AC100 TB --- 2012-11-08 22:32:33 - skipping AC100 kernel TB --- 2012-11-08 22:32:33 - cd /src/sys/arm/conf TB --- 2012-11-08 22:32:33 - /usr/sbin/config -m ARMADAXP TB --- 2012-11-08 22:32:33 - skipping ARMADAXP kernel TB --- 2012-11-08 22:32:33 - cd /src/sys/arm/conf TB --- 2012-11-08 22:32:33 - /usr/sbin/config -m ATMEL TB --- 2012-11-08 22:32:34 - building ATMEL kernel TB --- 2012-11-08 22:32:34 - CROSS_BUILD_TESTING=YES TB --- 2012-11-08 22:32:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-08 22:32:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-08 22:32:34 - SRCCONF=/dev/null TB --- 2012-11-08 22:32:34 - TARGET=arm TB --- 2012-11-08 22:32:34 - TARGET_ARCH=arm TB --- 2012-11-08 22:32:34 - TZ=UTC TB --- 2012-11-08 22:32:34 - __MAKE_CONF=/dev/null TB --- 2012-11-08 22:32:34 - cd /src TB --- 2012-11-08 22:32:34 - /usr/bin/make -B buildkernel KERNCONF=ATMEL Kernel build for ATMEL started on Thu Nov 8 22:32:34 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for ATMEL completed on Thu Nov 8 22:36:09 UTC 2012 TB --- 2012-11-08 22:36:09 - cd /src/sys/arm/conf TB --- 2012-11-08 22:36:09 - /usr/sbin/config -m AVILA TB --- 2012-11-08 22:36:09 - skipping AVILA kernel TB --- 2012-11-08 22:36:09 - cd /src/sys/arm/conf TB --- 2012-11-08 22:36:09 - /usr/sbin/config -m BEAGLEBONE TB --- 2012-11-08 22:36:09 - skipping BEAGLEBONE kernel TB --- 2012-11-08 22:36:09 - cd /src/sys/arm/conf TB --- 2012-11-08 22:36:09 - /usr/sbin/config -m BWCT TB --- 2012-11-08 22:36:09 - building BWCT kernel TB --- 2012-11-08 22:36:09 - CROSS_BUILD_TESTING=YES TB --- 2012-11-08 22:36:09 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-08 22:36:09 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-08 22:36:09 - SRCCONF=/dev/null TB --- 2012-11-08 22:36:09 - TARGET=arm TB --- 2012-11-08 22:36:09 - TARGET_ARCH=arm TB --- 2012-11-08 22:36:09 - TZ=UTC TB --- 2012-11-08 22:36:09 - __MAKE_CONF=/dev/null TB --- 2012-11-08 22:36:09 - cd /src TB --- 2012-11-08 22:36:09 - /usr/bin/make -B buildkernel KERNCONF=BWCT Kernel build for BWCT started on Thu Nov 8 22:36:09 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for BWCT completed on Thu Nov 8 22:38:19 UTC 2012 TB --- 2012-11-08 22:38:19 - cd /src/sys/arm/conf TB --- 2012-11-08 22:38:19 - /usr/sbin/config -m CAMBRIA TB --- 2012-11-08 22:38:19 - skipping CAMBRIA kernel TB --- 2012-11-08 22:38:19 - cd /src/sys/arm/conf TB --- 2012-11-08 22:38:19 - /usr/sbin/config -m CNS11XXNAS TB --- 2012-11-08 22:38:19 - building CNS11XXNAS kernel TB --- 2012-11-08 22:38:19 - CROSS_BUILD_TESTING=YES TB --- 2012-11-08 22:38:19 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-08 22:38:19 -
Re: [head tinderbox] failure on arm/arm
FreeBSD Tinderbox wrote: cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict -prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-sh ow-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contri b/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-comm on -finline-limit=8000 --param inline-unit-growth=100 --param large-function-gr owth=1000 -mcpu=arm9 -ffreestanding -Werror /src/sys/dev/ata/ata-sata.c /src/sys/dev/ata/ata-sata.c: In function 'ata_sata_phy_reset': /src/sys/dev/ata/ata-sata.c:158: error: 'struct ata_channel' has no member na med 'user' *** Error code 1 ata_channel member user is only defined if ATA_CAM is defined. Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
Fixed. On 20 August 2012 11:30, FreeBSD Tinderbox tinder...@freebsd.org wrote: TB --- 2012-08-20 16:50:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 16:50:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-08-20 16:50:00 - starting HEAD tinderbox run for arm/arm TB --- 2012-08-20 16:50:00 - cleaning the object tree TB --- 2012-08-20 16:56:30 - cvsupping the source tree TB --- 2012-08-20 16:56:30 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2012-08-20 16:59:05 - building world TB --- 2012-08-20 16:59:05 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 16:59:05 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 16:59:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 16:59:05 - SRCCONF=/dev/null TB --- 2012-08-20 16:59:05 - TARGET=arm TB --- 2012-08-20 16:59:05 - TARGET_ARCH=arm TB --- 2012-08-20 16:59:05 - TZ=UTC TB --- 2012-08-20 16:59:05 - __MAKE_CONF=/dev/null TB --- 2012-08-20 16:59:05 - cd /src TB --- 2012-08-20 16:59:05 - /usr/bin/make -B buildworld World build started on Mon Aug 20 16:59:06 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Mon Aug 20 18:01:33 UTC 2012 TB --- 2012-08-20 18:01:33 - cd /src/sys/arm/conf TB --- 2012-08-20 18:01:33 - /usr/sbin/config -m ARMADAXP TB --- 2012-08-20 18:01:34 - skipping ARMADAXP kernel TB --- 2012-08-20 18:01:34 - cd /src/sys/arm/conf TB --- 2012-08-20 18:01:34 - /usr/sbin/config -m ATMEL TB --- 2012-08-20 18:01:34 - building ATMEL kernel TB --- 2012-08-20 18:01:34 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:01:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:01:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:01:34 - SRCCONF=/dev/null TB --- 2012-08-20 18:01:34 - TARGET=arm TB --- 2012-08-20 18:01:34 - TARGET_ARCH=arm TB --- 2012-08-20 18:01:34 - TZ=UTC TB --- 2012-08-20 18:01:34 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:01:34 - cd /src TB --- 2012-08-20 18:01:34 - /usr/bin/make -B buildkernel KERNCONF=ATMEL Kernel build for ATMEL started on Mon Aug 20 18:01:34 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for ATMEL completed on Mon Aug 20 18:05:05 UTC 2012 TB --- 2012-08-20 18:05:05 - cd /src/sys/arm/conf TB --- 2012-08-20 18:05:05 - /usr/sbin/config -m AVILA TB --- 2012-08-20 18:05:06 - skipping AVILA kernel TB --- 2012-08-20 18:05:06 - cd /src/sys/arm/conf TB --- 2012-08-20 18:05:06 - /usr/sbin/config -m BEAGLEBONE TB --- 2012-08-20 18:05:06 - skipping BEAGLEBONE kernel TB --- 2012-08-20 18:05:06 - cd /src/sys/arm/conf TB --- 2012-08-20 18:05:06 - /usr/sbin/config -m BWCT TB --- 2012-08-20 18:05:06 - building BWCT kernel TB --- 2012-08-20 18:05:06 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:05:06 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:05:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:05:06 - SRCCONF=/dev/null TB --- 2012-08-20 18:05:06 - TARGET=arm TB --- 2012-08-20 18:05:06 - TARGET_ARCH=arm TB --- 2012-08-20 18:05:06 - TZ=UTC TB --- 2012-08-20 18:05:06 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:05:06 - cd /src TB --- 2012-08-20 18:05:06 - /usr/bin/make -B buildkernel KERNCONF=BWCT Kernel build for BWCT started on Mon Aug 20 18:05:06 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for BWCT completed on Mon Aug 20 18:07:15 UTC 2012 TB --- 2012-08-20 18:07:15 - cd /src/sys/arm/conf TB --- 2012-08-20 18:07:15 - /usr/sbin/config -m CAMBRIA TB --- 2012-08-20 18:07:15 - skipping CAMBRIA kernel TB --- 2012-08-20 18:07:15 - cd /src/sys/arm/conf TB --- 2012-08-20 18:07:15 - /usr/sbin/config -m CNS11XXNAS TB --- 2012-08-20 18:07:15 - building CNS11XXNAS kernel TB --- 2012-08-20 18:07:15 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:07:15 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:07:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:07:15 - SRCCONF=/dev/null TB --- 2012-08-20 18:07:15 - TARGET=arm TB --- 2012-08-20 18:07:15 - TARGET_ARCH=arm TB --- 2012-08-20 18:07:15 - TZ=UTC TB --- 2012-08-20 18:07:15 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:07:15 - cd /src TB --- 2012-08-20 18:07:15 - /usr/bin/make -B buildkernel KERNCONF=CNS11XXNAS
Re: [head tinderbox] failure on arm/arm
On 19 June 2012 23:12, FreeBSD Tinderbox tinder...@freebsd.org wrote: Stop in /src/usr.sbin/mfiutil. *** Error code 1 looks like this is my fault :( I've sent a patch to my mentor for approval which should fix this. -- Eitan Adler ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On Jun 14, 2012, at 9:11 PM, FreeBSD Tinderbox wrote: /src/sys/arm/s3c2xx0/s3c24x0_machdep.c: In function 'initarm': /src/sys/arm/s3c2xx0/s3c24x0_machdep.c:252: error: too few arguments to function 'fake_preload_metadata' Odd... This looks like a stale build. 252 no longer has that call on it... Warner ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On Sun, 27 Nov 2011 20:08:02 GMT FreeBSD Tinderbox wrote: FT /src/sys/kern/kern_proc.c:2589: error: 'KERN_PROC_PS_STRINGS' undeclared here (not in a function) FT *** Error code 1 Forgot to commit changes to sys/sysctl.h. Sorry for this. Should be fixed in r228046. -- Mikolaj Golub ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On 17 Nov 2011, at 23:31, Garrett Cooper wrote: On Thu, Nov 17, 2011 at 11:55 AM, FreeBSD Tinderbox tinder...@freebsd.org wrote: TB --- 2011-11-17 18:10:01 - tinderbox 2.8 running on freebsd-current.sentex.ca TB --- 2011-11-17 18:10:01 - starting HEAD tinderbox run for arm/arm TB --- 2011-11-17 18:10:01 - cleaning the object tree TB --- 2011-11-17 18:10:26 - cvsupping the source tree TB --- 2011-11-17 18:10:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2011-11-17 18:11:12 - building world TB --- 2011-11-17 18:11:12 - CROSS_BUILD_TESTING=YES TB --- 2011-11-17 18:11:12 - MAKEOBJDIRPREFIX=/obj TB --- 2011-11-17 18:11:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-11-17 18:11:12 - SRCCONF=/dev/null TB --- 2011-11-17 18:11:12 - TARGET=arm TB --- 2011-11-17 18:11:12 - TARGET_ARCH=arm TB --- 2011-11-17 18:11:12 - TZ=UTC TB --- 2011-11-17 18:11:12 - __MAKE_CONF=/dev/null TB --- 2011-11-17 18:11:12 - cd /src TB --- 2011-11-17 18:11:12 - /usr/bin/make -B buildworld World build started on Thu Nov 17 18:11:12 UTC 2011 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Thu Nov 17 19:06:31 UTC 2011 TB --- 2011-11-17 19:06:31 - cd /src/sys/arm/conf TB --- 2011-11-17 19:06:31 - /usr/sbin/config -m AVILA TB --- 2011-11-17 19:06:31 - building AVILA kernel TB --- 2011-11-17 19:06:31 - CROSS_BUILD_TESTING=YES TB --- 2011-11-17 19:06:31 - MAKEOBJDIRPREFIX=/obj TB --- 2011-11-17 19:06:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-11-17 19:06:31 - SRCCONF=/dev/null TB --- 2011-11-17 19:06:31 - TARGET=arm TB --- 2011-11-17 19:06:31 - TARGET_ARCH=arm TB --- 2011-11-17 19:06:31 - TZ=UTC TB --- 2011-11-17 19:06:31 - __MAKE_CONF=/dev/null TB --- 2011-11-17 19:06:31 - cd /src TB --- 2011-11-17 19:06:31 - /usr/bin/make -B buildkernel KERNCONF=AVILA Kernel build for AVILA started on Thu Nov 17 19:06:31 UTC 2011 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for AVILA completed on Thu Nov 17 19:09:34 UTC 2011 TB --- 2011-11-17 19:09:34 - cd /src/sys/arm/conf TB --- 2011-11-17 19:09:34 - /usr/sbin/config -m BWCT TB --- 2011-11-17 19:09:35 - building BWCT kernel TB --- 2011-11-17 19:09:35 - CROSS_BUILD_TESTING=YES TB --- 2011-11-17 19:09:35 - MAKEOBJDIRPREFIX=/obj TB --- 2011-11-17 19:09:35 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-11-17 19:09:35 - SRCCONF=/dev/null TB --- 2011-11-17 19:09:35 - TARGET=arm TB --- 2011-11-17 19:09:35 - TARGET_ARCH=arm TB --- 2011-11-17 19:09:35 - TZ=UTC TB --- 2011-11-17 19:09:35 - __MAKE_CONF=/dev/null TB --- 2011-11-17 19:09:35 - cd /src TB --- 2011-11-17 19:09:35 - /usr/bin/make -B buildkernel KERNCONF=BWCT Kernel build for BWCT started on Thu Nov 17 19:09:35 UTC 2011 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for BWCT completed on Thu Nov 17 19:12:13 UTC 2011 TB --- 2011-11-17 19:12:13 - cd /src/sys/arm/conf TB --- 2011-11-17 19:12:13 - /usr/sbin/config -m CAMBRIA TB --- 2011-11-17 19:12:13 - building CAMBRIA kernel TB --- 2011-11-17 19:12:13 - CROSS_BUILD_TESTING=YES TB --- 2011-11-17 19:12:13 - MAKEOBJDIRPREFIX=/obj TB --- 2011-11-17 19:12:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-11-17 19:12:13 - SRCCONF=/dev/null TB --- 2011-11-17 19:12:13 - TARGET=arm TB --- 2011-11-17 19:12:13 - TARGET_ARCH=arm TB --- 2011-11-17 19:12:13 - TZ=UTC TB --- 2011-11-17 19:12:13 - __MAKE_CONF=/dev/null TB --- 2011-11-17 19:12:13 - cd /src TB --- 2011-11-17 19:12:13 - /usr/bin/make -B buildkernel KERNCONF=CAMBRIA Kernel build for CAMBRIA started on Thu Nov 17 19:12:13 UTC 2011 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for CAMBRIA completed on Thu Nov 17 19:15:10 UTC 2011 TB --- 2011-11-17 19:15:10 - cd /src/sys/arm/conf TB --- 2011-11-17 19:15:10 - /usr/sbin/config -m CNS11XXNAS TB --- 2011-11-17 19:15:11 - building CNS11XXNAS kernel TB --- 2011-11-17 19:15:11 - CROSS_BUILD_TESTING=YES TB --- 2011-11-17 19:15:11 - MAKEOBJDIRPREFIX=/obj TB --- 2011-11-17 19:15:11 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-11-17 19:15:11 - SRCCONF=/dev/null TB --- 2011-11-17 19:15:11 - TARGET=arm TB --- 2011-11-17 19:15:11 - TARGET_ARCH=arm TB --- 2011-11-17
Re: [head tinderbox] failure on arm/arm
On Thu, Nov 17, 2011 at 11:55 AM, FreeBSD Tinderbox tinder...@freebsd.org wrote: TB --- 2011-11-17 18:10:01 - tinderbox 2.8 running on freebsd-current.sentex.ca TB --- 2011-11-17 18:10:01 - starting HEAD tinderbox run for arm/arm TB --- 2011-11-17 18:10:01 - cleaning the object tree TB --- 2011-11-17 18:10:26 - cvsupping the source tree TB --- 2011-11-17 18:10:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2011-11-17 18:11:12 - building world TB --- 2011-11-17 18:11:12 - CROSS_BUILD_TESTING=YES TB --- 2011-11-17 18:11:12 - MAKEOBJDIRPREFIX=/obj TB --- 2011-11-17 18:11:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-11-17 18:11:12 - SRCCONF=/dev/null TB --- 2011-11-17 18:11:12 - TARGET=arm TB --- 2011-11-17 18:11:12 - TARGET_ARCH=arm TB --- 2011-11-17 18:11:12 - TZ=UTC TB --- 2011-11-17 18:11:12 - __MAKE_CONF=/dev/null TB --- 2011-11-17 18:11:12 - cd /src TB --- 2011-11-17 18:11:12 - /usr/bin/make -B buildworld World build started on Thu Nov 17 18:11:12 UTC 2011 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Thu Nov 17 19:06:31 UTC 2011 TB --- 2011-11-17 19:06:31 - cd /src/sys/arm/conf TB --- 2011-11-17 19:06:31 - /usr/sbin/config -m AVILA TB --- 2011-11-17 19:06:31 - building AVILA kernel TB --- 2011-11-17 19:06:31 - CROSS_BUILD_TESTING=YES TB --- 2011-11-17 19:06:31 - MAKEOBJDIRPREFIX=/obj TB --- 2011-11-17 19:06:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-11-17 19:06:31 - SRCCONF=/dev/null TB --- 2011-11-17 19:06:31 - TARGET=arm TB --- 2011-11-17 19:06:31 - TARGET_ARCH=arm TB --- 2011-11-17 19:06:31 - TZ=UTC TB --- 2011-11-17 19:06:31 - __MAKE_CONF=/dev/null TB --- 2011-11-17 19:06:31 - cd /src TB --- 2011-11-17 19:06:31 - /usr/bin/make -B buildkernel KERNCONF=AVILA Kernel build for AVILA started on Thu Nov 17 19:06:31 UTC 2011 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for AVILA completed on Thu Nov 17 19:09:34 UTC 2011 TB --- 2011-11-17 19:09:34 - cd /src/sys/arm/conf TB --- 2011-11-17 19:09:34 - /usr/sbin/config -m BWCT TB --- 2011-11-17 19:09:35 - building BWCT kernel TB --- 2011-11-17 19:09:35 - CROSS_BUILD_TESTING=YES TB --- 2011-11-17 19:09:35 - MAKEOBJDIRPREFIX=/obj TB --- 2011-11-17 19:09:35 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-11-17 19:09:35 - SRCCONF=/dev/null TB --- 2011-11-17 19:09:35 - TARGET=arm TB --- 2011-11-17 19:09:35 - TARGET_ARCH=arm TB --- 2011-11-17 19:09:35 - TZ=UTC TB --- 2011-11-17 19:09:35 - __MAKE_CONF=/dev/null TB --- 2011-11-17 19:09:35 - cd /src TB --- 2011-11-17 19:09:35 - /usr/bin/make -B buildkernel KERNCONF=BWCT Kernel build for BWCT started on Thu Nov 17 19:09:35 UTC 2011 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for BWCT completed on Thu Nov 17 19:12:13 UTC 2011 TB --- 2011-11-17 19:12:13 - cd /src/sys/arm/conf TB --- 2011-11-17 19:12:13 - /usr/sbin/config -m CAMBRIA TB --- 2011-11-17 19:12:13 - building CAMBRIA kernel TB --- 2011-11-17 19:12:13 - CROSS_BUILD_TESTING=YES TB --- 2011-11-17 19:12:13 - MAKEOBJDIRPREFIX=/obj TB --- 2011-11-17 19:12:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-11-17 19:12:13 - SRCCONF=/dev/null TB --- 2011-11-17 19:12:13 - TARGET=arm TB --- 2011-11-17 19:12:13 - TARGET_ARCH=arm TB --- 2011-11-17 19:12:13 - TZ=UTC TB --- 2011-11-17 19:12:13 - __MAKE_CONF=/dev/null TB --- 2011-11-17 19:12:13 - cd /src TB --- 2011-11-17 19:12:13 - /usr/bin/make -B buildkernel KERNCONF=CAMBRIA Kernel build for CAMBRIA started on Thu Nov 17 19:12:13 UTC 2011 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for CAMBRIA completed on Thu Nov 17 19:15:10 UTC 2011 TB --- 2011-11-17 19:15:10 - cd /src/sys/arm/conf TB --- 2011-11-17 19:15:10 - /usr/sbin/config -m CNS11XXNAS TB --- 2011-11-17 19:15:11 - building CNS11XXNAS kernel TB --- 2011-11-17 19:15:11 - CROSS_BUILD_TESTING=YES TB --- 2011-11-17 19:15:11 - MAKEOBJDIRPREFIX=/obj TB --- 2011-11-17 19:15:11 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-11-17 19:15:11 - SRCCONF=/dev/null TB --- 2011-11-17 19:15:11 - TARGET=arm TB --- 2011-11-17 19:15:11 - TARGET_ARCH=arm TB --- 2011-11-17 19:15:11 - TZ=UTC TB --- 2011-11-17 19:15:11 -
Re: [head tinderbox] failure on arm/arm
Fixed! Sorry. Adrian On 25 June 2011 06:12, FreeBSD Tinderbox tinder...@freebsd.org wrote: TB --- 2011-06-24 21:10:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-06-24 21:10:00 - starting HEAD tinderbox run for arm/arm TB --- 2011-06-24 21:10:00 - cleaning the object tree TB --- 2011-06-24 21:10:20 - cvsupping the source tree TB --- 2011-06-24 21:10:20 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2011-06-24 21:10:50 - building world TB --- 2011-06-24 21:10:50 - MAKEOBJDIRPREFIX=/obj TB --- 2011-06-24 21:10:50 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-06-24 21:10:50 - TARGET=arm TB --- 2011-06-24 21:10:50 - TARGET_ARCH=arm TB --- 2011-06-24 21:10:50 - TZ=UTC TB --- 2011-06-24 21:10:50 - __MAKE_CONF=/dev/null TB --- 2011-06-24 21:10:50 - cd /src TB --- 2011-06-24 21:10:50 - /usr/bin/make -B buildworld World build started on Fri Jun 24 21:10:50 UTC 2011 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Fri Jun 24 22:05:13 UTC 2011 TB --- 2011-06-24 22:05:13 - WARNING: no kernel config for LINT TB --- 2011-06-24 22:05:13 - cd /src/sys/arm/conf TB --- 2011-06-24 22:05:13 - /usr/sbin/config -m AVILA TB --- 2011-06-24 22:05:13 - building AVILA kernel TB --- 2011-06-24 22:05:13 - MAKEOBJDIRPREFIX=/obj TB --- 2011-06-24 22:05:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-06-24 22:05:13 - TARGET=arm TB --- 2011-06-24 22:05:13 - TARGET_ARCH=arm TB --- 2011-06-24 22:05:13 - TZ=UTC TB --- 2011-06-24 22:05:13 - __MAKE_CONF=/dev/null TB --- 2011-06-24 22:05:13 - cd /src TB --- 2011-06-24 22:05:13 - /usr/bin/make -B buildkernel KERNCONF=AVILA Kernel build for AVILA started on Fri Jun 24 22:05:13 UTC 2011 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for AVILA completed on Fri Jun 24 22:08:05 UTC 2011 TB --- 2011-06-24 22:08:05 - cd /src/sys/arm/conf TB --- 2011-06-24 22:08:05 - /usr/sbin/config -m BWCT TB --- 2011-06-24 22:08:05 - building BWCT kernel TB --- 2011-06-24 22:08:05 - MAKEOBJDIRPREFIX=/obj TB --- 2011-06-24 22:08:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-06-24 22:08:05 - TARGET=arm TB --- 2011-06-24 22:08:05 - TARGET_ARCH=arm TB --- 2011-06-24 22:08:05 - TZ=UTC TB --- 2011-06-24 22:08:05 - __MAKE_CONF=/dev/null TB --- 2011-06-24 22:08:05 - cd /src TB --- 2011-06-24 22:08:05 - /usr/bin/make -B buildkernel KERNCONF=BWCT Kernel build for BWCT started on Fri Jun 24 22:08:05 UTC 2011 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for BWCT completed on Fri Jun 24 22:10:03 UTC 2011 TB --- 2011-06-24 22:10:03 - cd /src/sys/arm/conf TB --- 2011-06-24 22:10:03 - /usr/sbin/config -m CAMBRIA TB --- 2011-06-24 22:10:03 - building CAMBRIA kernel TB --- 2011-06-24 22:10:03 - MAKEOBJDIRPREFIX=/obj TB --- 2011-06-24 22:10:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-06-24 22:10:03 - TARGET=arm TB --- 2011-06-24 22:10:03 - TARGET_ARCH=arm TB --- 2011-06-24 22:10:03 - TZ=UTC TB --- 2011-06-24 22:10:03 - __MAKE_CONF=/dev/null TB --- 2011-06-24 22:10:03 - cd /src TB --- 2011-06-24 22:10:03 - /usr/bin/make -B buildkernel KERNCONF=CAMBRIA Kernel build for CAMBRIA started on Fri Jun 24 22:10:03 UTC 2011 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] /src/sys/dev/ath/ath_hal/ah.c:897: undefined reference to `ath_hal_debug' ah.o: In function `ath_hal_setTxQProps': /src/sys/dev/ath/ath_hal/ah.c:870: undefined reference to `ath_hal_debug' ah.o: In function `ath_hal_get_mimo_chan_noise': /src/sys/dev/ath/ath_hal/ah.c:1003: undefined reference to `ath_hal_debug' ah.o: In function `ath_hal_getChanNoise': /src/sys/dev/ath/ath_hal/ah.c:929: undefined reference to `ath_hal_debug' ah.o:/src/sys/dev/ath/ath_hal/ah.c:223: more undefined references to `ath_hal_debug' follow *** Error code 1 Stop in /obj/arm.arm/src/sys/CAMBRIA. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-06-24 22:12:43 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-06-24 22:12:43 - ERROR: failed to build CAMBRIA kernel TB --- 2011-06-24 22:12:43 - 2697.48 user 785.24 system 3763.68 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full
Re: [head tinderbox] failure on arm/arm
This is me, but I'm rather puzzled why it's failing.
SYSCTL_UQUAD is in the sys/sysctl.h for the image we're building. And
why is there a file with SYSCTL_FOO being built as a library?
Any help?
Thanks,
matthew
On Wed, Jan 12, 2011 at 2:20 PM, FreeBSD Tinderbox
tinder...@freebsd.org wrote:
TB --- 2011-01-12 22:00:00 - tinderbox 2.6 running on
freebsd-current.sentex.ca
TB --- 2011-01-12 22:00:00 - starting HEAD tinderbox run for arm/arm
TB --- 2011-01-12 22:00:00 - cleaning the object tree
TB --- 2011-01-12 22:00:09 - cvsupping the source tree
TB --- 2011-01-12 22:00:09 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca
/tinderbox/HEAD/arm/arm/supfile
TB --- 2011-01-12 22:00:30 - building world
TB --- 2011-01-12 22:00:30 - MAKEOBJDIRPREFIX=/obj
TB --- 2011-01-12 22:00:30 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2011-01-12 22:00:30 - TARGET=arm
TB --- 2011-01-12 22:00:30 - TARGET_ARCH=arm
TB --- 2011-01-12 22:00:30 - TZ=UTC
TB --- 2011-01-12 22:00:30 - __MAKE_CONF=/dev/null
TB --- 2011-01-12 22:00:30 - cd /src
TB --- 2011-01-12 22:00:30 - /usr/bin/make -B buildworld
World build started on Wed Jan 12 22:00:30 UTC 2011
Rebuilding the temporary build tree
stage 1.1: legacy release compatibility shims
stage 1.2: bootstrap tools
stage 2.1: cleaning up the object tree
stage 2.2: rebuilding the object tree
stage 2.3: build tools
stage 3: cross tools
stage 4.1: building includes
stage 4.2: building libraries
[...]
/src/cddl/lib/libzpool/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:678:
error: expected ')' before '(' token
/src/cddl/lib/libzpool/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:682:
error: expected ')' before '(' token
/src/cddl/lib/libzpool/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:684:
error: expected ')' before '(' token
/src/cddl/lib/libzpool/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:686:
error: expected ')' before '(' token
/src/cddl/lib/libzpool/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:689:
error: expected ')' before '(' token
/src/cddl/lib/libzpool/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:691:
error: expected ')' before '(' token
/src/cddl/lib/libzpool/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:694:
error: expected ')' before '(' token
/src/cddl/lib/libzpool/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:698:
error: expected ')' before '(' token
*** Error code 1
Stop in /src/cddl/lib/libzpool.
*** Error code 1
Stop in /src/cddl/lib.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
*** Error code 1
Stop in /src.
TB --- 2011-01-12 22:20:50 - WARNING: /usr/bin/make returned exit code 1
TB --- 2011-01-12 22:20:50 - ERROR: failed to build world
TB --- 2011-01-12 22:20:50 - 926.31 user 233.05 system 1249.77 real
http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On 2011-01-12 23:26, Matthew Fleming wrote: This is me, but I'm rather puzzled why it's failing. SYSCTL_UQUAD is in the sys/sysctl.h for the image we're building. And why is there a file with SYSCTL_FOO being built as a library? Any help? During the build of cddl/lib/libzpool, it looks like sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c includes cddl/contrib/opensolaris/lib/libzpool/common/sys/zfs_context.h (which is meant for userspace) at the top, and the latter contains: #define SYSCTL_DECL(...) #define SYSCTL_NODE(...) #define SYSCTL_INT(...) #define SYSCTL_UINT(...) #define SYSCTL_ULONG(...) #define SYSCTL_QUAD(...) as stubs for kernel calls that do not matter for a userspace library. However, it misses the corresponding definition for SYSCTL_UQUAD. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on arm/arm
On Mon, 1 Mar 2010, FreeBSD Tinderbox wrote: === usr.bin/systat (all) cc -O -pipe -DINET6 -std=gnu99 -Wno-pointer-sign -c /src/usr.bin/systat/cmds.c cc -O -pipe -DINET6 -std=gnu99 -Wno-pointer-sign -c /src/usr.bin/systat/cmdtab.c In file included from /src/usr.bin/systat/extern.h:39, from /src/usr.bin/systat/cmdtab.c:43: /obj/arm/src/tmp/usr/include/kvm.h:72: error: expected declaration specifiers or '...' before 'u_int' Converted from a u_int to an unsigned int in a follow-up commit, which fixes the build (I hope). Should have done a buildworld rather than building all the individual components, lesson re-learned. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
