Re: expanding past 1 TB on amd64
On 7/16/2013 2:12 PM, Alan Cox wrote: ... The Haswell line of CPUs is widely reported to support DIMMs twice as large, and it's due in September. That would make the systems of late 2013 hold up to 1536GB of memory. I'd point you at stuff like the Supermicro X8BQ6 series of mainboards. QP E5-8800 systems with 1 TB of memory have been around since 2011. ___ 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
core.txt.N not created anymore on panic
Hi, Early May I set ddb_enable=YES (crashinfo_enable=YES by default). Upon panic, it created the following kind of files: -rw--- 1 root wheel 549 Jun 26 22:09 info.0 -rw--- 1 root wheel 1518501888 Jun 26 22:09 vmcore.0 -rw--- 1 root wheel 196981 Jun 26 22:09 core.txt.0 -rw--- 1 root wheel 546 Jun 26 23:15 info.1 -rw--- 1 root wheel 472608768 Jun 26 23:15 vmcore.1 -rw--- 1 root wheel 207034 Jun 26 23:15 core.txt.1 -rw--- 1 root wheel 546 Jun 27 00:47 info.2 -rw--- 1 root wheel 667717632 Jun 27 00:47 vmcore.2 -rw--- 1 root wheel 208745 Jun 27 00:48 core.txt.2 -rw--- 1 root wheel 549 Jul 3 14:40 info.3 -rw--- 1 root wheel 1455198208 Jul 3 14:40 vmcore.3 -rw--- 1 root wheel 208173 Jul 3 14:41 core.txt.3 The core.txt.N files contained crashinfo(8) informations along with ddb textdump, because crashinfo(8) outputs dmesg. Yesterday, I upgraded to latest -CURRENT from one from June 9th. While stress-testing overnight, I got a couple of panics but core.txt.N are not created anymore. -rw--- 1 root wheel 530 Jul 17 01:10 info.5 -rw--- 1 root wheel 75776 Jul 17 01:10 textdump.tar.5 -rw--- 1 root wheel 529 Jul 17 02:01 info.6 -rw--- 1 root wheel 74240 Jul 17 02:01 textdump.tar.6 -rw--- 1 root wheel 530 Jul 17 04:20 info.7 -rw--- 1 root wheel 74752 Jul 17 04:20 textdump.tar.7 -rw--- 1 root wheel 530 Jul 17 07:50 info.8 -rw--- 1 root wheel 92672 Jul 17 07:50 textdump.tar.8 -rw--- 1 root wheel 531 Jul 17 08:44 info.9 -rw--- 1 root wheel 110592 Jul 17 08:44 textdump.tar.9 Each textdump.tar.N contains: tar tvf /var/crash/textdump.tar.9 -rw--- 0 root wheel 49152 Jul 17 08:30 ddb.txt -rw--- 0 root wheel3179 Jul 17 08:30 config.txt -rw--- 0 root wheel 54137 Jul 17 08:30 msgbuf.txt -rw--- 0 root wheel 88 Jul 17 08:30 panic.txt -rw--- 0 root wheel 120 Jul 17 08:30 version.txt Any idea changed in between? I checked svn log in etc/ but I found nothing relevant. -- Jeremie Le Hen Scientists say the world is made up of Protons, Neutrons and Electrons. They forgot to mention Morons. ___ 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: core.txt.N not created anymore on panic
On Wed, Jul 17, 2013 at 09:16:55AM +0200, Jeremie Le Hen wrote: Hi, Early May I set ddb_enable=YES (crashinfo_enable=YES by default). Upon panic, it created the following kind of files: -rw--- 1 root wheel 549 Jun 26 22:09 info.0 -rw--- 1 root wheel 1518501888 Jun 26 22:09 vmcore.0 -rw--- 1 root wheel 196981 Jun 26 22:09 core.txt.0 -rw--- 1 root wheel 546 Jun 26 23:15 info.1 -rw--- 1 root wheel 472608768 Jun 26 23:15 vmcore.1 -rw--- 1 root wheel 207034 Jun 26 23:15 core.txt.1 -rw--- 1 root wheel 546 Jun 27 00:47 info.2 -rw--- 1 root wheel 667717632 Jun 27 00:47 vmcore.2 -rw--- 1 root wheel 208745 Jun 27 00:48 core.txt.2 -rw--- 1 root wheel 549 Jul 3 14:40 info.3 -rw--- 1 root wheel 1455198208 Jul 3 14:40 vmcore.3 -rw--- 1 root wheel 208173 Jul 3 14:41 core.txt.3 The core.txt.N files contained crashinfo(8) informations along with ddb textdump, because crashinfo(8) outputs dmesg. Yesterday, I upgraded to latest -CURRENT from one from June 9th. While stress-testing overnight, I got a couple of panics but core.txt.N are not created anymore. -rw--- 1 root wheel 530 Jul 17 01:10 info.5 -rw--- 1 root wheel 75776 Jul 17 01:10 textdump.tar.5 -rw--- 1 root wheel 529 Jul 17 02:01 info.6 -rw--- 1 root wheel 74240 Jul 17 02:01 textdump.tar.6 -rw--- 1 root wheel 530 Jul 17 04:20 info.7 -rw--- 1 root wheel 74752 Jul 17 04:20 textdump.tar.7 -rw--- 1 root wheel 530 Jul 17 07:50 info.8 -rw--- 1 root wheel 92672 Jul 17 07:50 textdump.tar.8 -rw--- 1 root wheel 531 Jul 17 08:44 info.9 -rw--- 1 root wheel 110592 Jul 17 08:44 textdump.tar.9 Each textdump.tar.N contains: tar tvf /var/crash/textdump.tar.9 -rw--- 0 root wheel 49152 Jul 17 08:30 ddb.txt -rw--- 0 root wheel3179 Jul 17 08:30 config.txt -rw--- 0 root wheel 54137 Jul 17 08:30 msgbuf.txt -rw--- 0 root wheel 88 Jul 17 08:30 panic.txt -rw--- 0 root wheel 120 Jul 17 08:30 version.txt Any idea changed in between? I checked svn log in etc/ but I found nothing relevant. For the record: debug.ddb.capture.bufoff: 0 debug.ddb.capture.maxbufsize: 5242880 debug.ddb.capture.inprogress: 0 debug.ddb.capture.bufsize: 49152 debug.ddb.capture.data: debug.ddb.scripting.scripts: lockinfo=show locks; show alllocks; show lockedvnods kdb.enter.panic=textdump set; capture on; run lockinfo; show pcpu; bt; ps; alltrace; capture off; call doadump; reset kdb.enter.witness=run lockinfo debug.ddb.scripting.unscript: debug.ddb.textdump.pending: 0 debug.ddb.textdump.do_config: 1 debug.ddb.textdump.do_ddb: 1 debug.ddb.textdump.do_msgbuf: 1 debug.ddb.textdump.do_panic: 1 debug.ddb.textdump.do_version: 1 debug.debugger_on_panic: 1 debug.kdb.available: ddb debug.kdb.current: ddb debug.kdb.enter: 0 debug.kdb.panic: 0 debug.kdb.trap: 0 debug.kdb.trap_code: 0 debug.kdb.break_to_debugger: 0 debug.kdb.alt_break_to_debugger: 0 -- Jeremie Le Hen Scientists say the world is made up of Protons, Neutrons and Electrons. They forgot to mention Morons. ___ 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: Lenovo x220 - hangs on shutdown
On 16.07.2013 22:48, Joel Dahl wrote: Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it hangs when I do a shutdown from an xterm. The screen just goes black and the fan never spins down. It doesn't respond to ping. My build is from Sunday. I never type 'shutdown', but it is configured to shutdown when I close the display. Everything works fine. I can investigate revision and shutdown from xterm at home if you like. Michael ___ 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: Deadlock in nullfs/zfs somewhere
on 16/07/2013 22:40 Adrian Chadd said the following: :( So it's a deadlock. Ok, so what's next? A creative process... One possibility is to add getnewvnode_reserve() calls before the ZFS transaction beginnings in the places where a new vnode/znode may have to be allocated within a transaction. This looks like a quick and cheap solution but it makes the code somewhat messier. Another possibility is to change something in VFS machinery, so that VOP_RECLAIM getting blocked for one filesystem does not prevent vnode allocation for other filesystems. I could think of other possible solutions via infrastructural changes in VFS or ZFS... -- Andriy Gapon ___ 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: Re: Lenovo x220 - hangs on shutdown
Date: Wed, 17 Jul 2013 12:07:11 +0200 From: Michael Schmiedgen schmied...@gmx.net To: Joel Dahl j...@vnode.se Cc: curr...@freebsd.org Subject: Re: Lenovo x220 - hangs on shutdown Message-ID: 51e66ccf.2040...@gmx.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 16.07.2013 22:48, Joel Dahl wrote: Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it hangs when I do a shutdown from an xterm. The screen just goes black and the fan never spins down. It doesn't respond to ping. My build is from Sunday. I never type 'shutdown', but it is configured to shutdown when I close the display. Everything works fine. I can investigate revision and shutdown from xterm at home if you like. Michael Hi, I fall in this kind of issue with my laptop and deactivating powerd solves the problem. I'm sorry but I didn't explore this issue beyond. - rodrigo ___ 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: expanding past 1 TB on amd64
On 7/16/2013 2:12 PM, Alan Cox wrote: ... The Haswell line of CPUs is widely reported to support DIMMs twice as large, and it's due in September. That would make the systems of late 2013 hold up to 1536GB of memory. I'd point you at stuff like the Supermicro X8BQ6 series of mainboards. QP E5-8800 systems with 1 TB of memory have been around since 2011. That might have been true, but I did check SuperMicro's motherboard matrix of available products before posting. The largest listed memory configuration on any of their current products is 768GB. http://www.supermicro.com/products/motherboard/matrix/?cpuclass=allsorton=memory -Kurt ___ 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: expanding past 1 TB on amd64
Hi, On 17 Jul 2013, at 15:17, Kurt Lidl wrote: On 7/16/2013 2:12 PM, Alan Cox wrote: ... The Haswell line of CPUs is widely reported to support DIMMs twice as large, and it's due in September. That would make the systems of late 2013 hold up to 1536GB of memory. I'd point you at stuff like the Supermicro X8BQ6 series of mainboards. QP E5-8800 systems with 1 TB of memory have been around since 2011. That might have been true, but I did check SuperMicro's motherboard matrix of available products before posting. The largest listed memory configuration on any of their current products is 768GB. http://www.supermicro.com/products/motherboard/matrix/?cpuclass=allsorton=memory -Kurt http://www.supermicro.com/products/motherboard/Xeon7000 Looks like their matrix is not up-to-date. -- Bob Bishop r...@gid.co.uk ___ 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: expanding past 1 TB on amd64
On Wed, Jul 17, 2013 at 7:50 AM, Bob Bishop r...@gid.co.uk wrote: Hi, On 17 Jul 2013, at 15:17, Kurt Lidl wrote: On 7/16/2013 2:12 PM, Alan Cox wrote: ... The Haswell line of CPUs is widely reported to support DIMMs twice as large, and it's due in September. That would make the systems of late 2013 hold up to 1536GB of memory. I'd point you at stuff like the Supermicro X8BQ6 series of mainboards. QP E5-8800 systems with 1 TB of memory have been around since 2011. That might have been true, but I did check SuperMicro's motherboard matrix of available products before posting. The largest listed memory configuration on any of their current products is 768GB. http://www.supermicro.com/products/motherboard/matrix/?cpuclass=allsorton=memory -Kurt http://www.supermicro.com/products/motherboard/Xeon7000 Looks like their matrix is not up-to-date. There's also several AMD motherboards that support 1 TB of RAM: http://www.supermicro.com/products/nfo/AMD_G34.cfm?pg=MOBO You know, the CPUs that started the 64-bit x86 support ... :) -- Freddie Cash fjwc...@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: Sound lag over HDMI
Alexander Motin m...@freebsd.org wrote: I don't know what to say. I am now using HDMI audio from NVIDIA card to quite old external 5.1 receiver with XBMC every day, and I haven't noticed lags. The only potentially related effect I have noticed is that my receiver eats first second or about that of playback stream. That's from the receiver examining the incoming data to see if it is AC-3, DTS, or plain PCM. -- Christian naddy Weisgerber na...@mips.inka.de ___ 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: expanding past 1 TB on amd64
On 7/17/13 11:26 AM, Freddie Cash wrote: On Wed, Jul 17, 2013 at 7:50 AM, Bob Bishop r...@gid.co.uk mailto:r...@gid.co.uk wrote: Hi, On 17 Jul 2013, at 15:17, Kurt Lidl wrote: On 7/16/2013 2:12 PM, Alan Cox wrote: ... The Haswell line of CPUs is widely reported to support DIMMs twice as large, and it's due in September. That would make the systems of late 2013 hold up to 1536GB of memory. I'd point you at stuff like the Supermicro X8BQ6 series of mainboards. QP E5-8800 systems with 1 TB of memory have been around since 2011. That might have been true, but I did check SuperMicro's motherboard matrix of available products before posting. The largest listed memory configuration on any of their current products is 768GB. http://www.supermicro.com/products/motherboard/matrix/?cpuclass=allsorton=memory -Kurt http://www.supermicro.com/products/motherboard/Xeon7000 Looks like their matrix is not up-to-date. There's also several AMD motherboards that support 1 TB of RAM: http://www.supermicro.com/products/nfo/AMD_G34.cfm?pg=MOBO You know, the CPUs that started the 64-bit x86 support ... :) Searching a bit harder, it looks like Intel is shipping a quad-socket board that supports 1500GB of memory. http://ark.intel.com/products/61033 So, 1500GB is now, and the next doubling will probably be soon, assuming Intel revs their quad processor boards for Haswell, and that support for 64GB DIMMs is there. I'm not trying to find the biggest motherboard out there, I'm just trying to say that Chris' patch for support up to 16TB isn't too farfetched. And within the next 5 year window, it's entirely likely that 4TB systems will be available. -Kurt ___ 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: Deadlock in nullfs/zfs somewhere
On 17 July 2013 04:26, Andriy Gapon a...@freebsd.org wrote: on 16/07/2013 22:40 Adrian Chadd said the following: :( So it's a deadlock. Ok, so what's next? A creative process... Wonderful. :) One possibility is to add getnewvnode_reserve() calls before the ZFS transaction beginnings in the places where a new vnode/znode may have to be allocated within a transaction. This looks like a quick and cheap solution but it makes the code somewhat messier. Another possibility is to change something in VFS machinery, so that VOP_RECLAIM getting blocked for one filesystem does not prevent vnode allocation for other filesystems. I could think of other possible solutions via infrastructural changes in VFS or ZFS... Well, what do others think? This seems like a showstopper for systems with lots and lots of ZFS filesystems doing lots and lots of activity. -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: Lenovo x220 - hangs on shutdown
On 07/16/13 22:48, Joel Dahl wrote: Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it hangs when I do a shutdown from an xterm. The screen just goes black and the fan never spins down. It doesn't respond to ping. X220, 10.0-CURRENT #0 r253368 amd, powerd running. In xterm I type 'shutdown -p now' and everything works fine. But the kernel is compiled without INVARIANTS and without WITNESS and malloc runs in production mode. Michael ___ 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: Lenovo x220 - hangs on shutdown
On Wed, Jul 17, 2013 at 07:39:30PM +0200, Michael Schmiedgen wrote: On 07/16/13 22:48, Joel Dahl wrote: Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it hangs when I do a shutdown from an xterm. The screen just goes black and the fan never spins down. It doesn't respond to ping. X220, 10.0-CURRENT #0 r253368 amd, powerd running. In xterm I type 'shutdown -p now' and everything works fine. But the kernel is compiled without INVARIANTS and without WITNESS and malloc runs in production mode. I tried enabling powerd - no change. The machine won't power off. -- Joel ___ 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
Panic when starting X with Intel KMS
Hi, I'm having panics or hard freezes when starting X with an Intel video card. The machine is able to start old X+twm without problems but when I try gnome3 (in normal or fallback mode, doesn't matter) the machine panics or hard freezes. This doesn't happen when running X with vesa. With vesa the gnome is able to start in fallback (no composition) mode. Also, an old i386 with an nvidia card is able to run that gnome3 with composition so I'd say it has to do with the intel card. These are the specs of the machine: FreeBSD 10.0-CURRENT #4 r+3dc57aa: Wed Jul 17 15:13:07 CEST 2013 root@portgus:/usr/obj/usr/src/sys/CUSTOM amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 RAM: 8GB Video Card: Intel chipid=0x00468086 The debugging knobs in the kernel config are there. I can also confirm that I can break to the debugger with CTRL+ALT+ESC before starting X. The world was build without debug symbols. Because the machine runs with an Intel card, I had to use my $work dockstation to obtain a serial port and do the debug via serial port with another machine. When starting X, either the machine freezes hard (and so no CTRL+ALT+ESC) or the machine panics. It has never executed X without panics or freezes. I was able to obtain a core dump, the results are at: https://dl.dropboxusercontent.com/u/2094962/core.txt.4 I was unable to dive any further because the dump only shows the kernel side of things. The bt only seems to show the kernel side and the user side of things seems to be corrupt. Any other info I can obtain from the machine in the moment of the panic, let me know. I can easy do the debug via serial port. Gus -- Salut i força, Gustau --- Prou top-posting : http://ca.wikipedia.org/wiki/Top-posting Stop top-posting : http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Unitat de Gestió dels departaments O O O Matemàtica Aplicada IV i Enginyeria Telemàtica Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona ___ 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
Panic when starting X with Intel KMS
Hi, I'm having panics or hard freezes when starting X with an Intel video card. The machine is able to start old X+twm without problems but when I try gnome3 (in normal or fallback mode, doesn't matter) the machine panics or hard freezes. This doesn't happen when running X with vesa. With vesa the gnome is able to start in debug mode. Also, an old i386 with an nvidia card is able to run that gnome3 with composition so I'd say it has to do with the intel card. These are the specs of the machine: FreeBSD 10.0-CURRENT #4 r+3dc57aa: Wed Jul 17 15:13:07 CEST 2013 root@portgus:/usr/obj/usr/src/sys/CUSTOM amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 RAM: 8GB Video Card: Intel chipid=0x00468086 The debugging knobs in the kernel config are there. I can also confirm that I can break to the debugger with CTRL+ALT+ESC before starting X. The world was build without debug symbols. Because the machine runs with an Intel card, I had to use my $work dockstation to obtain a serial port and do the debug via serial port. When starting X, either the machine freezes hard (and so no CTRL+ALT+ESC) or the machine panics. It has never executed X without panics or freezes. I was able to obtain a core dump, the results are at: https://dl.dropboxusercontent.com/u/2094962/core.txt.4 I was unable to dive further because the dump only shows the kernel side of things. The bt only seems to show the kernel side an the user side of things seems to be corrupt. Any other info I can provide, let me know. I can easy do the debug via serial port. Gus -- Salut i força, Gustau --- Prou top-posting : http://ca.wikipedia.org/wiki/Top-posting Stop top-posting : http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Unitat de Gestió dels departaments O O O Matemàtica Aplicada IV i Enginyeria Telemàtica Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona ___ 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
[head tinderbox] failure on ia64/ia64
TB --- 2013-07-17 23:43:10 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-17 23:43:10 - 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-07-17 23:43:10 - starting HEAD tinderbox run for ia64/ia64
TB --- 2013-07-17 23:43:10 - cleaning the object tree
TB --- 2013-07-17 23:43:10 - /usr/local/bin/svn stat /src
TB --- 2013-07-17 23:43:14 - At svn revision 253432
TB --- 2013-07-17 23:43:15 - building world
TB --- 2013-07-17 23:43:15 - CROSS_BUILD_TESTING=YES
TB --- 2013-07-17 23:43:15 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-07-17 23:43:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-07-17 23:43:15 - SRCCONF=/dev/null
TB --- 2013-07-17 23:43:15 - TARGET=ia64
TB --- 2013-07-17 23:43:15 - TARGET_ARCH=ia64
TB --- 2013-07-17 23:43:15 - TZ=UTC
TB --- 2013-07-17 23:43:15 - __MAKE_CONF=/dev/null
TB --- 2013-07-17 23:43:15 - cd /src
TB --- 2013-07-17 23:43:15 - /usr/bin/make -B buildworld
Building an up-to-date make(1)
World build started on Wed Jul 17 23:43:22 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
[...]
LC_ALL=C awk '!/^#|^$/ { printf #define\tK_%s\t%d\n\t{\%s\, K_%s},\n,
toupper($1), ++L, $1, toupper($1); }' /src/sbin/route/keywords keywords.h
|| (rm -f keywords.h; false)
rm -f .depend
CC='cc ' mkdep -f .depend -a-DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99
/src/sbin/route/route.c
echo route: /obj/ia64.ia64/src/tmp/usr/lib/libc.a .depend
cc -O2 -pipe -DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99 -Wsystem-headers
-Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c
/src/sbin/route/route.c
cc1: warnings being treated as errors
/src/sbin/route/route.c: In function 'rtmsg':
/src/sbin/route/route.c:1491: warning: the address of 'so' will always evaluate
as 'true'
*** Error code 1
Stop.
make: stopped in /src/sbin/route
*** Error code 1
Stop.
make: stopped in /obj/ia64.ia64/src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop in /src.
TB --- 2013-07-18 00:50:37 - WARNING: /usr/bin/make returned exit code 1
TB --- 2013-07-18 00:50:37 - ERROR: failed to build world
TB --- 2013-07-18 00:50:37 - 3190.01 user 612.41 system 4046.74 real
http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-ia64-ia64.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
Re: errors building 9-STABLE on recent HEAD
Yea thank you guys, I got it to work now. - Martin On Jul 16, 2013, at 11:42 AM, hiren panchasara hiren.panchas...@gmail.com wrote: On Mon, Jul 15, 2013 at 8:27 PM, wen heping wenhep...@gmail.com wrote: I build 9-STABLE on head today, while failed many times last month. There were some intermittent issues but *recent* stable/9 should build fine on *recent* head. If not, please report the errors and have sjg@ look at them. Thanks, Hiren wen 2013/7/16 Brooks Davis bro...@freebsd.org After not working for quite some time, I was able to build 9-STABLE last week. I'm not sure if something changed in the branch or if the new current I'd updated to fixed it. -- Brooks On Sat, Jul 13, 2013 at 11:07:04PM +0800, Martin Wilke wrote: Hi, I see exactly the same error on pointyhat too, did you find any work around for that? On Jun 25, 2013, at 4:11 AM, Brooks Davis bro...@freebsd.org wrote: I recently upgraded my main buildbox from an ancient 9.0-STABLE snapshot to head and I've run into an issue building 9-STABLE on it. Initally this was broken by the switch to bmake, but Simon committed a work around that and using the fmake port also works around it. Now I'm seeing a strange error in yacc generated code. I say strange because yacc is correctly being bootstrapped so we're using the expected version and not the one in HEAD. Does anyone have any insight into this issue? cc -O2 -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/home/bed22/src-9/gnu/usr.bin/binutils/ld -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../libbfd -I/home/bed22/obj/home/bed22/src-9/gnu/usr.bin/binutils/ld/../libbfd -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/include -DTARGET=\x86_64-unknown-freebsd\ -DDEFAULT_EMULATION=\elf_x86_64_fbsd\ -DSCRIPTDIR=\/usr/libdata\ -DBFD_VERSION_STRING=\2.17.50 [FreeBSD] 2007-07-03\ -DBINDIR=\/usr/bin\ -DTARGET_SYSTEM_ROOT=\\ -DTOOLBINDIR=\//usr/bin/libexec\ -D_GNU_SOURCE -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld -I/home/bed22/src-9/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/bfd -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c ldlex.c cc1: warnings being treated as errors stdout: In function 'yy_get_next_buffer': stdout:3229: warning: passing argument 2 of 'yy_input' from incompatible pointer type *** [ldlex.o] Error code 1 Stop in /home/bed22/src-9/gnu/usr.bin/binutils/ld. *** [all] Error code 1 Thanks, Brooks +-oOO--(_)--OOo-+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest ___ 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 +-oOO--(_)--OOo-+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest ___ 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
[head tinderbox] failure on mips/mips
TB --- 2013-07-18 00:50:37 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-18 00:50:37 - 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-07-18 00:50:37 - starting HEAD tinderbox run for mips/mips
TB --- 2013-07-18 00:50:37 - cleaning the object tree
TB --- 2013-07-18 00:50:37 - /usr/local/bin/svn stat /src
TB --- 2013-07-18 00:50:45 - At svn revision 253432
TB --- 2013-07-18 00:50:46 - building world
TB --- 2013-07-18 00:50:46 - CROSS_BUILD_TESTING=YES
TB --- 2013-07-18 00:50:46 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-07-18 00:50:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-07-18 00:50:46 - SRCCONF=/dev/null
TB --- 2013-07-18 00:50:46 - TARGET=mips
TB --- 2013-07-18 00:50:46 - TARGET_ARCH=mips
TB --- 2013-07-18 00:50:46 - TZ=UTC
TB --- 2013-07-18 00:50:46 - __MAKE_CONF=/dev/null
TB --- 2013-07-18 00:50:46 - cd /src
TB --- 2013-07-18 00:50:46 - /usr/bin/make -B buildworld
Building an up-to-date make(1)
World build started on Thu Jul 18 00:50:53 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
[...]
LC_ALL=C awk '!/^#|^$/ { printf #define\tK_%s\t%d\n\t{\%s\, K_%s},\n,
toupper($1), ++L, $1, toupper($1); }' /src/sbin/route/keywords keywords.h
|| (rm -f keywords.h; false)
rm -f .depend
CC='cc ' mkdep -f .depend -a-DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99
/src/sbin/route/route.c
echo route: /obj/mips.mips/src/tmp/usr/lib/libc.a .depend
cc -O -pipe -G0 -DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99 -Wsystem-headers
-Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c
/src/sbin/route/route.c
cc1: warnings being treated as errors
/src/sbin/route/route.c: In function 'rtmsg':
/src/sbin/route/route.c:1491: warning: the address of 'so' will always evaluate
as 'true'
*** Error code 1
Stop.
make: stopped in /src/sbin/route
*** Error code 1
Stop.
make: stopped in /obj/mips.mips/src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop in /src.
TB --- 2013-07-18 01:38:46 - WARNING: /usr/bin/make returned exit code 1
TB --- 2013-07-18 01:38:46 - ERROR: failed to build world
TB --- 2013-07-18 01:38:46 - 2096.65 user 519.19 system 2889.08 real
http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-mips-mips.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
[head tinderbox] failure on mips64/mips
TB --- 2013-07-18 01:38:47 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-18 01:38:47 - 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-07-18 01:38:47 - starting HEAD tinderbox run for mips64/mips
TB --- 2013-07-18 01:38:47 - cleaning the object tree
TB --- 2013-07-18 01:38:47 - /usr/local/bin/svn stat /src
TB --- 2013-07-18 01:39:14 - At svn revision 253432
TB --- 2013-07-18 01:39:15 - building world
TB --- 2013-07-18 01:39:15 - CROSS_BUILD_TESTING=YES
TB --- 2013-07-18 01:39:15 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-07-18 01:39:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-07-18 01:39:15 - SRCCONF=/dev/null
TB --- 2013-07-18 01:39:15 - TARGET=mips
TB --- 2013-07-18 01:39:15 - TARGET_ARCH=mips64
TB --- 2013-07-18 01:39:15 - TZ=UTC
TB --- 2013-07-18 01:39:15 - __MAKE_CONF=/dev/null
TB --- 2013-07-18 01:39:15 - cd /src
TB --- 2013-07-18 01:39:15 - /usr/bin/make -B buildworld
Building an up-to-date make(1)
World build started on Thu Jul 18 01:39:22 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
[...]
LC_ALL=C awk '!/^#|^$/ { printf #define\tK_%s\t%d\n\t{\%s\, K_%s},\n,
toupper($1), ++L, $1, toupper($1); }' /src/sbin/route/keywords keywords.h
|| (rm -f keywords.h; false)
rm -f .depend
CC='cc ' mkdep -f .depend -a-DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99
/src/sbin/route/route.c
echo route: /obj/mips.mips64/src/tmp/usr/lib/libc.a .depend
cc -O -pipe -G0 -DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99 -Wsystem-headers
-Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c
/src/sbin/route/route.c
cc1: warnings being treated as errors
/src/sbin/route/route.c: In function 'rtmsg':
/src/sbin/route/route.c:1491: warning: the address of 'so' will always evaluate
as 'true'
*** Error code 1
Stop.
make: stopped in /src/sbin/route
*** Error code 1
Stop.
make: stopped in /obj/mips.mips64/src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop in /src.
TB --- 2013-07-18 02:26:51 - WARNING: /usr/bin/make returned exit code 1
TB --- 2013-07-18 02:26:51 - ERROR: failed to build world
TB --- 2013-07-18 02:26:51 - 2105.06 user 482.70 system 2884.50 real
http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-mips64-mips.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
[head tinderbox] failure on sparc64/sparc64
TB --- 2013-07-18 02:26:51 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-18 02:26:51 - 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-07-18 02:26:51 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2013-07-18 02:26:51 - cleaning the object tree
TB --- 2013-07-18 02:26:51 - /usr/local/bin/svn stat /src
TB --- 2013-07-18 02:26:55 - At svn revision 253432
TB --- 2013-07-18 02:26:56 - building world
TB --- 2013-07-18 02:26:56 - CROSS_BUILD_TESTING=YES
TB --- 2013-07-18 02:26:56 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-07-18 02:26:56 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-07-18 02:26:56 - SRCCONF=/dev/null
TB --- 2013-07-18 02:26:56 - TARGET=sparc64
TB --- 2013-07-18 02:26:56 - TARGET_ARCH=sparc64
TB --- 2013-07-18 02:26:56 - TZ=UTC
TB --- 2013-07-18 02:26:56 - __MAKE_CONF=/dev/null
TB --- 2013-07-18 02:26:56 - cd /src
TB --- 2013-07-18 02:26:56 - /usr/bin/make -B buildworld
Building an up-to-date make(1)
World build started on Thu Jul 18 02:27:03 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
[...]
LC_ALL=C awk '!/^#|^$/ { printf #define\tK_%s\t%d\n\t{\%s\, K_%s},\n,
toupper($1), ++L, $1, toupper($1); }' /src/sbin/route/keywords keywords.h
|| (rm -f keywords.h; false)
rm -f .depend
CC='cc ' mkdep -f .depend -a-DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99
/src/sbin/route/route.c
echo route: /obj/sparc64.sparc64/src/tmp/usr/lib/libc.a .depend
cc -O2 -pipe -DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99 -fstack-protector
-Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized
-Wno-pointer-sign -c /src/sbin/route/route.c
cc1: warnings being treated as errors
/src/sbin/route/route.c: In function 'rtmsg':
/src/sbin/route/route.c:1491: warning: the address of 'so' will always evaluate
as 'true'
*** Error code 1
Stop.
make: stopped in /src/sbin/route
*** Error code 1
Stop.
make: stopped in /obj/sparc64.sparc64/src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop in /src.
TB --- 2013-07-18 03:15:36 - WARNING: /usr/bin/make returned exit code 1
TB --- 2013-07-18 03:15:36 - ERROR: failed to build world
TB --- 2013-07-18 03:15:36 - 2401.46 user 434.80 system 2924.53 real
http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-sparc64-sparc64.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
[head tinderbox] failure on powerpc/powerpc
TB --- 2013-07-18 02:00:53 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-18 02:00:53 - 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-07-18 02:00:53 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2013-07-18 02:00:53 - cleaning the object tree
TB --- 2013-07-18 02:00:53 - /usr/local/bin/svn stat /src
TB --- 2013-07-18 02:01:02 - At svn revision 253432
TB --- 2013-07-18 02:01:03 - building world
TB --- 2013-07-18 02:01:03 - CROSS_BUILD_TESTING=YES
TB --- 2013-07-18 02:01:03 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-07-18 02:01:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-07-18 02:01:03 - SRCCONF=/dev/null
TB --- 2013-07-18 02:01:03 - TARGET=powerpc
TB --- 2013-07-18 02:01:03 - TARGET_ARCH=powerpc
TB --- 2013-07-18 02:01:03 - TZ=UTC
TB --- 2013-07-18 02:01:03 - __MAKE_CONF=/dev/null
TB --- 2013-07-18 02:01:03 - cd /src
TB --- 2013-07-18 02:01:03 - /usr/bin/make -B buildworld
Building an up-to-date make(1)
World build started on Thu Jul 18 02:01:11 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
[...]
LC_ALL=C awk '!/^#|^$/ { printf #define\tK_%s\t%d\n\t{\%s\, K_%s},\n,
toupper($1), ++L, $1, toupper($1); }' /src/sbin/route/keywords keywords.h
|| (rm -f keywords.h; false)
rm -f .depend
CC='cc ' mkdep -f .depend -a-DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99
/src/sbin/route/route.c
echo route: /obj/powerpc.powerpc/src/tmp/usr/lib/libc.a .depend
cc -O2 -pipe -DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99 -fstack-protector
-Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized
-Wno-pointer-sign -c /src/sbin/route/route.c
cc1: warnings being treated as errors
/src/sbin/route/route.c: In function 'rtmsg':
/src/sbin/route/route.c:1491: warning: the address of 'so' will always evaluate
as 'true'
*** Error code 1
Stop.
make: stopped in /src/sbin/route
*** Error code 1
Stop.
make: stopped in /obj/powerpc.powerpc/src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop in /src.
TB --- 2013-07-18 04:14:41 - WARNING: /usr/bin/make returned exit code 1
TB --- 2013-07-18 04:14:41 - ERROR: failed to build world
TB --- 2013-07-18 04:14:41 - 7074.83 user 806.41 system 8027.67 real
http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-powerpc-powerpc.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
[head tinderbox] failure on powerpc64/powerpc
TB --- 2013-07-18 02:03:56 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-18 02:03:56 - 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-07-18 02:03:56 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2013-07-18 02:03:56 - cleaning the object tree
TB --- 2013-07-18 02:03:56 - /usr/local/bin/svn stat /src
TB --- 2013-07-18 02:03:59 - At svn revision 253432
TB --- 2013-07-18 02:04:00 - building world
TB --- 2013-07-18 02:04:00 - CROSS_BUILD_TESTING=YES
TB --- 2013-07-18 02:04:00 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-07-18 02:04:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-07-18 02:04:00 - SRCCONF=/dev/null
TB --- 2013-07-18 02:04:00 - TARGET=powerpc
TB --- 2013-07-18 02:04:00 - TARGET_ARCH=powerpc64
TB --- 2013-07-18 02:04:00 - TZ=UTC
TB --- 2013-07-18 02:04:00 - __MAKE_CONF=/dev/null
TB --- 2013-07-18 02:04:00 - cd /src
TB --- 2013-07-18 02:04:00 - /usr/bin/make -B buildworld
Building an up-to-date make(1)
World build started on Thu Jul 18 02:04:07 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
[...]
LC_ALL=C awk '!/^#|^$/ { printf #define\tK_%s\t%d\n\t{\%s\, K_%s},\n,
toupper($1), ++L, $1, toupper($1); }' /src/sbin/route/keywords keywords.h
|| (rm -f keywords.h; false)
rm -f .depend
CC='cc ' mkdep -f .depend -a-DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99
/src/sbin/route/route.c
echo route: /obj/powerpc.powerpc64/src/tmp/usr/lib/libc.a .depend
cc -O2 -pipe -DNS -DINET -DINET6 -I. -DRESCUE -std=gnu99 -fstack-protector
-Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized
-Wno-pointer-sign -c /src/sbin/route/route.c
cc1: warnings being treated as errors
/src/sbin/route/route.c: In function 'rtmsg':
/src/sbin/route/route.c:1491: warning: the address of 'so' will always evaluate
as 'true'
*** Error code 1
Stop.
make: stopped in /src/sbin/route
*** Error code 1
Stop.
make: stopped in /obj/powerpc.powerpc64/src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue/rescue
*** Error code 1
Stop.
make: stopped in /src/rescue
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop.
make: stopped in /src
*** Error code 1
Stop in /src.
TB --- 2013-07-18 04:17:16 - WARNING: /usr/bin/make returned exit code 1
TB --- 2013-07-18 04:17:16 - ERROR: failed to build world
TB --- 2013-07-18 04:17:16 - 7126.42 user 816.09 system 7999.89 real
http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-powerpc64-powerpc.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
