From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 00:27:21 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83E50106564A; Sun, 25 Dec 2011 00:27:21 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4ACD88FC08; Sun, 25 Dec 2011 00:27:20 +0000 (UTC) Received: by pbcc3 with SMTP id c3so8486952pbc.13 for ; Sat, 24 Dec 2011 16:27:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=mvr6J243bGpMgv9lq9v3tp3CUl9M3IuC5Mpbtyujjac=; b=pcMWOtOerRov7YwADwmlO71COabgZ2F8aUKul1zuZsPbjri51y19144E5bG3+gVlzD 6AvV8Td9pbSoLlPMypQhmzv9LtQ1xSpi3wMvbCAf3Y80ajcEmeXBCWEh07MgcYJtDEeJ kK7GXZ3PtiiB0xiizjWhH8PWRhCGncN6x0474= MIME-Version: 1.0 Received: by 10.68.189.65 with SMTP id gg1mr12022403pbc.107.1324771144657; Sat, 24 Dec 2011 15:59:04 -0800 (PST) Sender: chmeeedalf@gmail.com Received: by 10.142.100.21 with HTTP; Sat, 24 Dec 2011 15:59:04 -0800 (PST) Received: by 10.142.100.21 with HTTP; Sat, 24 Dec 2011 15:59:04 -0800 (PST) In-Reply-To: <201112242345.pBONjh5K008411@freebsd-current.sentex.ca> References: <201112242345.pBONjh5K008411@freebsd-current.sentex.ca> Date: Sat, 24 Dec 2011 18:59:04 -0500 X-Google-Sender-Auth: Ek0InnsqHSerpAne5eBTQ5KzM6w Message-ID: From: Justin Hibbits To: FreeBSD Tinderbox Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: powerpc64@freebsd.org, current@freebsd.org Subject: Re: [head tinderbox] failure on powerpc64/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 00:27:21 -0000 On Dec 24, 2011 6:46 PM, "FreeBSD Tinderbox" wrote: > > TB --- 2011-12-24 21:13:44 - tinderbox 2.8 running on freebsd-current.sentex.ca > TB --- 2011-12-24 21:13:44 - starting HEAD tinderbox run for powerpc64/powerpc > TB --- 2011-12-24 21:13:44 - cleaning the object tree > TB --- 2011-12-24 21:13:56 - cvsupping the source tree > TB --- 2011-12-24 21:13:56 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile > TB --- 2011-12-24 21:14:08 - building world > TB --- 2011-12-24 21:14:08 - CROSS_BUILD_TESTING=YES > TB --- 2011-12-24 21:14:08 - MAKEOBJDIRPREFIX=/obj > TB --- 2011-12-24 21:14:08 - PATH=/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2011-12-24 21:14:08 - SRCCONF=/dev/null > TB --- 2011-12-24 21:14:08 - TARGET=powerpc > TB --- 2011-12-24 21:14:08 - TARGET_ARCH=powerpc64 > TB --- 2011-12-24 21:14:08 - TZ=UTC > TB --- 2011-12-24 21:14:08 - __MAKE_CONF=/dev/null > TB --- 2011-12-24 21:14:08 - cd /src > TB --- 2011-12-24 21:14:08 - /usr/bin/make -B buildworld > >>> World build started on Sat Dec 24 21:14:08 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 > >>> stage 5.1: building 32 bit shim libraries > >>> World build completed on Sat Dec 24 23:35:25 UTC 2011 > TB --- 2011-12-24 23:35:25 - generating LINT kernel config > TB --- 2011-12-24 23:35:25 - cd /src/sys/powerpc/conf > TB --- 2011-12-24 23:35:25 - /usr/bin/make -B LINT > TB --- 2011-12-24 23:35:25 - cd /src/sys/powerpc/conf > TB --- 2011-12-24 23:35:25 - /usr/sbin/config -m LINT > TB --- 2011-12-24 23:35:25 - building LINT kernel > TB --- 2011-12-24 23:35:25 - CROSS_BUILD_TESTING=YES > TB --- 2011-12-24 23:35:25 - MAKEOBJDIRPREFIX=/obj > TB --- 2011-12-24 23:35:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2011-12-24 23:35:25 - SRCCONF=/dev/null > TB --- 2011-12-24 23:35:25 - TARGET=powerpc > TB --- 2011-12-24 23:35:25 - TARGET_ARCH=powerpc64 > TB --- 2011-12-24 23:35:25 - TZ=UTC > TB --- 2011-12-24 23:35:25 - __MAKE_CONF=/dev/null > TB --- 2011-12-24 23:35:25 - cd /src > TB --- 2011-12-24 23:35:25 - /usr/bin/make -B buildkernel KERNCONF=LINT > >>> Kernel build for LINT started on Sat Dec 24 23:35:25 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 > [...] > cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/dev/fb/fb.c > cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/dev/hwpmc/hwpmc_powerpc.c > /src/sys/dev/hwpmc/hwpmc_powerpc.c: In function 'powerpc_intr': > /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'AMD_PMC_ENABLE' undeclared (first use in this function) > /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: (Each undeclared identifier is reported only once > /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: for each function it appears in.) > /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no member named 'pm_amd' > /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no member named 'pm_amd' > *** Error code 1 > > Stop in /obj/powerpc.powerpc64/src/sys/LINT. > *** Error code 1 > > Stop in /src. > *** Error code 1 > > Stop in /src. > TB --- 2011-12-24 23:45:43 - WARNING: /usr/bin/make returned exit code 1 > TB --- 2011-12-24 23:45:43 - ERROR: failed to build LINT kernel > TB --- 2011-12-24 23:45:43 - 7497.27 user 1367.80 system 9118.84 real > > > http://tinderbox.freebsd.org/tinderbox-head-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-unsubscribe@freebsd.org" Sorry about this, bad patch when I tested the build. I'll fix it tomorrow when I get time. From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 00:30:46 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1D86106566B; Sun, 25 Dec 2011 00:30:46 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id B203A8FC17; Sun, 25 Dec 2011 00:30:46 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:552b:bd3f:dbfe:7e88] (unknown [IPv6:2001:7b8:3a7:0:552b:bd3f:dbfe:7e88]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id D44D25C37; Sun, 25 Dec 2011 01:30:44 +0100 (CET) Message-ID: <4EF66EB5.6080609@FreeBSD.org> Date: Sun, 25 Dec 2011 01:30:45 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Marius Strobl References: <201112241543.pBOFhpF0037639@freebsd-current.sentex.ca> <20111224182112.GA50370@alchemy.franken.de> In-Reply-To: <20111224182112.GA50370@alchemy.franken.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: powerpc64@freebsd.org, FreeBSD Tinderbox , current@freebsd.org Subject: Re: [head tinderbox] failure on powerpc64/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 00:30:47 -0000 On 2011-12-24 19:21, Marius Strobl wrote: > On Sat, Dec 24, 2011 at 03:43:51PM +0000, FreeBSD Tinderbox wrote: ... >> TB --- 2011-12-24 13:54:50 - tinderbox 2.8 running on freebsd-current.sentex.ca >> TB --- 2011-12-24 13:54:50 - starting HEAD tinderbox run for powerpc64/powerpc ... >>>>> stage 4.4: building everything >> [...] >> rsyncfile.o:(.text+0xf8): undefined reference to `MD5Update' >> stream.o:(.text+0x544): undefined reference to `MD5Init' >> stream.o:(.text+0xb9c): undefined reference to `MD5Update' >> stream.o:(.text+0xd0c): undefined reference to `MD5Update' >> stream.o:(.text+0xd40): undefined reference to `MD5Update' >> stream.o:(.text+0xd54): undefined reference to `MD5Update' >> stream.o:(.text+0xd84): undefined reference to `MD5Update' >> stream.o:(.text+0xd98): more undefined references to `MD5Update' follow >> *** Error code 1 > > The tinderbox output isn't very helpful here and I've no idea how this > could happen as r228857 also added -lmd nor can I reproduce it. Could > this be a transient failure due to the tinderbox updating sources at > an unfortunate point in time or a glitch in the exported (according to > the sources presented by cvsweb.freebsd.org r228857 has reached the CVS > repository just fine though)? Must be something transient, I guess. I tried building r228864 on powerpc64, and buildworld went just fine.... From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 04:08:25 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3627106566C for ; Sun, 25 Dec 2011 04:08:25 +0000 (UTC) (envelope-from vertexSymphony@zoho.com) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.95]) by mx1.freebsd.org (Postfix) with ESMTP id ABEC78FC14 for ; Sun, 25 Dec 2011 04:08:25 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type; b=JcOF5s6eBJnhTp8/+6kpFVFgIr07fqlzAZlMAcm5WllLciN1XMNdFkTALfLy1COabwD1gfq24DFc w7KPQUEzFox8R/FM0SvTxwroeQCvyU13tUWgP5Y/LhdYQECgkm7h Received: from [192.168.0.100] (213-56-16-190.fibertel.com.ar [190.16.56.213]) by mx.zohomail.com with SMTPS id 1324786104507747.9717687627336; Sat, 24 Dec 2011 20:08:24 -0800 (PST) Message-ID: <4EF6A1B0.8020803@zoho.com> Date: Sun, 25 Dec 2011 01:08:16 -0300 From: Alex Kuster User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:8.0) Gecko/20111112 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4EF25468.9040204@gmail.com> <4EF2C613.3020609@digsys.bg> <4EF3D68C.2060803@zedat.fu-berlin.de> <20111223074706.1afe4d26@zelda.sugioarto.com> <4EF4474B.3050203@digsys.bg> <20111223114424.GA60815@freebsd.org> <4EF5E9FF.2020300@mail.zedat.fu-berlin.de> In-Reply-To: <4EF5E9FF.2020300@mail.zedat.fu-berlin.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ZohoMailClient: External X-Zoho-Virus-Status: 2 Subject: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 04:08:25 -0000 On 12/24/2011 12:04, O. Hartmann wrote: > There maybe serious reasons having the Linuxulator, i do not know. But > if not, why spending rare developer resources on that? As far as I'm > concerned, the only real reason having the Linuxulator is some stuff > from Adobe for desktop systems, Flash. That's it. Well, Linuxulator allows me to use binary only applications of Linux in FreeBSD without too much problem. I think running Firefox in the Linuxulator is nonsense, because it's supposed that Linuxulator is there for applications that can not be ported to FreeBSD (for example: the code is not open, you bough a privative linux-or-windows-only binary app). Naturally the Linuxulator will always lag behind Linux, but it works for me and I bet I'm not the only one. I think it should only be removed if 1) no one wants to maintain it 2) It obstructs the development of new code. Otherwise, I see no logical reason in this. Regards, Alex. P.S → Also notice that this is an offtopic of the original discussion, sorry. From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 06:01:17 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB369106566B; Sun, 25 Dec 2011 06:01:17 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 8603D8FC12; Sun, 25 Dec 2011 06:01:17 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.4) with ESMTP id pBP61GSx007020; Sun, 25 Dec 2011 01:01:16 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.4/Submit) id pBP61GCd006967; Sun, 25 Dec 2011 06:01:16 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 25 Dec 2011 06:01:16 GMT Message-Id: <201112250601.pBP61GCd006967@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 06:01:17 -0000 TB --- 2011-12-25 03:52:52 - tinderbox 2.8 running on freebsd-current.sentex.ca TB --- 2011-12-25 03:52:52 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2011-12-25 03:52:52 - cleaning the object tree TB --- 2011-12-25 03:53:08 - cvsupping the source tree TB --- 2011-12-25 03:53:08 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2011-12-25 03:53:37 - building world TB --- 2011-12-25 03:53:37 - CROSS_BUILD_TESTING=YES TB --- 2011-12-25 03:53:37 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-25 03:53:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-25 03:53:37 - SRCCONF=/dev/null TB --- 2011-12-25 03:53:37 - TARGET=powerpc TB --- 2011-12-25 03:53:37 - TARGET_ARCH=powerpc TB --- 2011-12-25 03:53:37 - TZ=UTC TB --- 2011-12-25 03:53:37 - __MAKE_CONF=/dev/null TB --- 2011-12-25 03:53:37 - cd /src TB --- 2011-12-25 03:53:37 - /usr/bin/make -B buildworld >>> World build started on Sun Dec 25 03:53:37 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 Sun Dec 25 05:51:01 UTC 2011 TB --- 2011-12-25 05:51:01 - generating LINT kernel config TB --- 2011-12-25 05:51:01 - cd /src/sys/powerpc/conf TB --- 2011-12-25 05:51:01 - /usr/bin/make -B LINT TB --- 2011-12-25 05:51:01 - cd /src/sys/powerpc/conf TB --- 2011-12-25 05:51:01 - /usr/sbin/config -m LINT TB --- 2011-12-25 05:51:01 - building LINT kernel TB --- 2011-12-25 05:51:01 - CROSS_BUILD_TESTING=YES TB --- 2011-12-25 05:51:01 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-25 05:51:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-25 05:51:01 - SRCCONF=/dev/null TB --- 2011-12-25 05:51:01 - TARGET=powerpc TB --- 2011-12-25 05:51:01 - TARGET_ARCH=powerpc TB --- 2011-12-25 05:51:01 - TZ=UTC TB --- 2011-12-25 05:51:01 - __MAKE_CONF=/dev/null TB --- 2011-12-25 05:51:01 - cd /src TB --- 2011-12-25 05:51:01 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Dec 25 05:51:01 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 [...] cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/fb/fb.c cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/hwpmc/hwpmc_powerpc.c /src/sys/dev/hwpmc/hwpmc_powerpc.c: In function 'powerpc_intr': /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'AMD_PMC_ENABLE' undeclared (first use in this function) /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: (Each undeclared identifier is reported only once /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: for each function it appears in.) /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no member named 'pm_amd' /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no member named 'pm_amd' *** Error code 1 Stop in /obj/powerpc.powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-12-25 06:01:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-12-25 06:01:15 - ERROR: failed to build LINT kernel TB --- 2011-12-25 06:01:15 - 6231.74 user 1062.88 system 7703.06 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 06:59:51 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1092106564A; Sun, 25 Dec 2011 06:59:51 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 8E9F98FC08; Sun, 25 Dec 2011 06:59:51 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.4) with ESMTP id pBP6xo3x044888; Sun, 25 Dec 2011 01:59:50 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.4/Submit) id pBP6xox7044887; Sun, 25 Dec 2011 06:59:50 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 25 Dec 2011 06:59:50 GMT Message-Id: <201112250659.pBP6xox7044887@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc64/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 06:59:51 -0000 TB --- 2011-12-25 04:29:40 - tinderbox 2.8 running on freebsd-current.sentex.ca TB --- 2011-12-25 04:29:40 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2011-12-25 04:29:40 - cleaning the object tree TB --- 2011-12-25 04:29:59 - cvsupping the source tree TB --- 2011-12-25 04:29:59 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile TB --- 2011-12-25 04:30:14 - building world TB --- 2011-12-25 04:30:14 - CROSS_BUILD_TESTING=YES TB --- 2011-12-25 04:30:14 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-25 04:30:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-25 04:30:14 - SRCCONF=/dev/null TB --- 2011-12-25 04:30:14 - TARGET=powerpc TB --- 2011-12-25 04:30:14 - TARGET_ARCH=powerpc64 TB --- 2011-12-25 04:30:14 - TZ=UTC TB --- 2011-12-25 04:30:14 - __MAKE_CONF=/dev/null TB --- 2011-12-25 04:30:14 - cd /src TB --- 2011-12-25 04:30:14 - /usr/bin/make -B buildworld >>> World build started on Sun Dec 25 04:30:14 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Sun Dec 25 06:49:32 UTC 2011 TB --- 2011-12-25 06:49:33 - generating LINT kernel config TB --- 2011-12-25 06:49:33 - cd /src/sys/powerpc/conf TB --- 2011-12-25 06:49:33 - /usr/bin/make -B LINT TB --- 2011-12-25 06:49:33 - cd /src/sys/powerpc/conf TB --- 2011-12-25 06:49:33 - /usr/sbin/config -m LINT TB --- 2011-12-25 06:49:33 - building LINT kernel TB --- 2011-12-25 06:49:33 - CROSS_BUILD_TESTING=YES TB --- 2011-12-25 06:49:33 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-25 06:49:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-25 06:49:33 - SRCCONF=/dev/null TB --- 2011-12-25 06:49:33 - TARGET=powerpc TB --- 2011-12-25 06:49:33 - TARGET_ARCH=powerpc64 TB --- 2011-12-25 06:49:33 - TZ=UTC TB --- 2011-12-25 06:49:33 - __MAKE_CONF=/dev/null TB --- 2011-12-25 06:49:33 - cd /src TB --- 2011-12-25 06:49:33 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Dec 25 06:49:33 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 [...] cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/dev/fb/fb.c cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/dev/hwpmc/hwpmc_powerpc.c /src/sys/dev/hwpmc/hwpmc_powerpc.c: In function 'powerpc_intr': /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'AMD_PMC_ENABLE' undeclared (first use in this function) /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: (Each undeclared identifier is reported only once /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: for each function it appears in.) /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no member named 'pm_amd' /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no member named 'pm_amd' *** Error code 1 Stop in /obj/powerpc.powerpc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-12-25 06:59:50 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-12-25 06:59:50 - ERROR: failed to build LINT kernel TB --- 2011-12-25 06:59:50 - 7458.24 user 1352.34 system 9010.15 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc64-powerpc.full From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 10:27:02 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F4F3106564A; Sun, 25 Dec 2011 10:27:02 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id A8A078FC0C; Sun, 25 Dec 2011 10:27:00 +0000 (UTC) Received: from deuterium.andreas.nets (dhclient-91-190-14-19.flashcable.ch [91.190.14.19]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id pBPA5dA2063187; Sun, 25 Dec 2011 11:05:41 +0100 (CET) (envelope-from andreast-list@fgznet.ch) Message-ID: <4EF6F633.80803@fgznet.ch> Date: Sun, 25 Dec 2011 11:08:51 +0100 From: Andreas Tobler User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Justin Hibbits References: <201112242345.pBONjh5K008411@freebsd-current.sentex.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: powerpc64@freebsd.org, FreeBSD Tinderbox , current@freebsd.org Subject: Re: [head tinderbox] failure on powerpc64/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 10:27:02 -0000 On 25.12.11 00:59, Justin Hibbits wrote: > On Dec 24, 2011 6:46 PM, "FreeBSD Tinderbox" wrote: >> >> TB --- 2011-12-24 21:13:44 - tinderbox 2.8 running on > freebsd-current.sentex.ca >> TB --- 2011-12-24 21:13:44 - starting HEAD tinderbox run for > powerpc64/powerpc >> TB --- 2011-12-24 21:13:44 - cleaning the object tree >> TB --- 2011-12-24 21:13:56 - cvsupping the source tree >> TB --- 2011-12-24 21:13:56 - /usr/bin/csup -z -r 3 -g -L 1 -h > cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile >> TB --- 2011-12-24 21:14:08 - building world >> TB --- 2011-12-24 21:14:08 - CROSS_BUILD_TESTING=YES >> TB --- 2011-12-24 21:14:08 - MAKEOBJDIRPREFIX=/obj >> TB --- 2011-12-24 21:14:08 - PATH=/usr/bin:/usr/sbin:/bin:/sbin >> TB --- 2011-12-24 21:14:08 - SRCCONF=/dev/null >> TB --- 2011-12-24 21:14:08 - TARGET=powerpc >> TB --- 2011-12-24 21:14:08 - TARGET_ARCH=powerpc64 >> TB --- 2011-12-24 21:14:08 - TZ=UTC >> TB --- 2011-12-24 21:14:08 - __MAKE_CONF=/dev/null >> TB --- 2011-12-24 21:14:08 - cd /src >> TB --- 2011-12-24 21:14:08 - /usr/bin/make -B buildworld >>>>> World build started on Sat Dec 24 21:14:08 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 >>>>> stage 5.1: building 32 bit shim libraries >>>>> World build completed on Sat Dec 24 23:35:25 UTC 2011 >> TB --- 2011-12-24 23:35:25 - generating LINT kernel config >> TB --- 2011-12-24 23:35:25 - cd /src/sys/powerpc/conf >> TB --- 2011-12-24 23:35:25 - /usr/bin/make -B LINT >> TB --- 2011-12-24 23:35:25 - cd /src/sys/powerpc/conf >> TB --- 2011-12-24 23:35:25 - /usr/sbin/config -m LINT >> TB --- 2011-12-24 23:35:25 - building LINT kernel >> TB --- 2011-12-24 23:35:25 - CROSS_BUILD_TESTING=YES >> TB --- 2011-12-24 23:35:25 - MAKEOBJDIRPREFIX=/obj >> TB --- 2011-12-24 23:35:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin >> TB --- 2011-12-24 23:35:25 - SRCCONF=/dev/null >> TB --- 2011-12-24 23:35:25 - TARGET=powerpc >> TB --- 2011-12-24 23:35:25 - TARGET_ARCH=powerpc64 >> TB --- 2011-12-24 23:35:25 - TZ=UTC >> TB --- 2011-12-24 23:35:25 - __MAKE_CONF=/dev/null >> TB --- 2011-12-24 23:35:25 - cd /src >> TB --- 2011-12-24 23:35:25 - /usr/bin/make -B buildkernel KERNCONF=LINT >>>>> Kernel build for LINT started on Sat Dec 24 23:35:25 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 >> [...] >> cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions > -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. > -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common > -finline-limit=15000 --param inline-unit-growth=100 --param > large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many > -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc > -ffreestanding -fstack-protector -Werror /src/sys/dev/fb/fb.c >> cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions > -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. > -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common > -finline-limit=15000 --param inline-unit-growth=100 --param > large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many > -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc > -ffreestanding -fstack-protector -Werror /src/sys/dev/hwpmc/hwpmc_powerpc.c >> /src/sys/dev/hwpmc/hwpmc_powerpc.c: In function 'powerpc_intr': >> /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'AMD_PMC_ENABLE' > undeclared (first use in this function) >> /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: (Each undeclared > identifier is reported only once >> /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: for each function it > appears in.) >> /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no > member named 'pm_amd' >> /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no > member named 'pm_amd' >> *** Error code 1 >> >> Stop in /obj/powerpc.powerpc64/src/sys/LINT. >> *** Error code 1 >> >> Stop in /src. >> *** Error code 1 >> >> Stop in /src. >> TB --- 2011-12-24 23:45:43 - WARNING: /usr/bin/make returned exit code 1 >> TB --- 2011-12-24 23:45:43 - ERROR: failed to build LINT kernel >> TB --- 2011-12-24 23:45:43 - 7497.27 user 1367.80 system 9118.84 real >> >> >> http://tinderbox.freebsd.org/tinderbox-head-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-unsubscribe@freebsd.org" > > Sorry about this, bad patch when I tested the build. I'll fix it tomorrow > when I get time. Something like this? Andreas Index: hwpmc_powerpc.c =================================================================== --- hwpmc_powerpc.c (revision 228872) +++ hwpmc_powerpc.c (working copy) @@ -686,10 +686,10 @@ v = pm->pm_sc.pm_reloadcount; config = mfspr(SPR_MMCR0); - KASSERT((config & ~AMD_PMC_ENABLE) == - (pm->pm_md.pm_amd.pm_amd_evsel & ~AMD_PMC_ENABLE), + KASSERT((config & ~POWERPC_PMC_ENABLE) == + (pm->pm_md.pm_powerpc.pm_powerpc_evsel & ~POWERPC_PMC_ENABLE), ("[powerpc,%d] config mismatch reg=0x%x pm=0x%x", __LINE__, - config, pm->pm_md.pm_amd.pm_amd_evsel)); + config, pm->pm_md.pm_powerpc.pm_powerpc_evsel)); mtspr(SPR_MMCR0, config | SPR_MMCR0_FC); powerpc_pmcn_write(i, v); From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 11:42:53 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1391A1065672; Sun, 25 Dec 2011 11:42:53 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id C7E568FC13; Sun, 25 Dec 2011 11:42:52 +0000 (UTC) Received: by dakp5 with SMTP id p5so9806713dak.13 for ; Sun, 25 Dec 2011 03:42:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=GnMQMNBhnGA47z/Fg+slWKtqpBRCsS2v/iwsDV/Q44c=; b=AU1tzdDfe6JGgHs4fWohP/qIGs8Ab5yg4j0Lb/97qSBxxPUoxgt6yJC4/FHIvZoMx4 Emv+yPgOhViaP7mGtwOE17MzYgCi3NmT+0IdfCZOcdGnSONQrEXxZffe5EQ9Bo8cZ6EF PuhDYqRkcbBOs2daTygPF9cyyTEu5zoAXg8+M= MIME-Version: 1.0 Received: by 10.68.192.97 with SMTP id hf1mr48061298pbc.5.1324813372035; Sun, 25 Dec 2011 03:42:52 -0800 (PST) Sender: chmeeedalf@gmail.com Received: by 10.142.100.21 with HTTP; Sun, 25 Dec 2011 03:42:51 -0800 (PST) Received: by 10.142.100.21 with HTTP; Sun, 25 Dec 2011 03:42:51 -0800 (PST) In-Reply-To: <4EF6F633.80803@fgznet.ch> References: <201112242345.pBONjh5K008411@freebsd-current.sentex.ca> <4EF6F633.80803@fgznet.ch> Date: Sun, 25 Dec 2011 06:42:51 -0500 X-Google-Sender-Auth: NXeInwEf8TaIGIAfD9hu7nUVx7A Message-ID: From: Justin Hibbits To: Andreas Tobler Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: powerpc64@freebsd.org, FreeBSD Tinderbox , current@freebsd.org Subject: Re: [head tinderbox] failure on powerpc64/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 11:42:53 -0000 On Dec 25, 2011 5:27 AM, "Andreas Tobler" wrote: > > On 25.12.11 00:59, Justin Hibbits wrote: >> >> On Dec 24, 2011 6:46 PM, "FreeBSD Tinderbox" wrote: >>> >>> >>> TB --- 2011-12-24 21:13:44 - tinderbox 2.8 running on >> >> freebsd-current.sentex.ca >>> >>> TB --- 2011-12-24 21:13:44 - starting HEAD tinderbox run for >> >> powerpc64/powerpc >>> >>> TB --- 2011-12-24 21:13:44 - cleaning the object tree >>> TB --- 2011-12-24 21:13:56 - cvsupping the source tree >>> TB --- 2011-12-24 21:13:56 - /usr/bin/csup -z -r 3 -g -L 1 -h >> >> cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile >>> >>> TB --- 2011-12-24 21:14:08 - building world >>> TB --- 2011-12-24 21:14:08 - CROSS_BUILD_TESTING=YES >>> TB --- 2011-12-24 21:14:08 - MAKEOBJDIRPREFIX=/obj >>> TB --- 2011-12-24 21:14:08 - PATH=/usr/bin:/usr/sbin:/bin:/sbin >>> TB --- 2011-12-24 21:14:08 - SRCCONF=/dev/null >>> TB --- 2011-12-24 21:14:08 - TARGET=powerpc >>> TB --- 2011-12-24 21:14:08 - TARGET_ARCH=powerpc64 >>> TB --- 2011-12-24 21:14:08 - TZ=UTC >>> TB --- 2011-12-24 21:14:08 - __MAKE_CONF=/dev/null >>> TB --- 2011-12-24 21:14:08 - cd /src >>> TB --- 2011-12-24 21:14:08 - /usr/bin/make -B buildworld >>>>>> >>>>>> World build started on Sat Dec 24 21:14:08 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 >>>>>> stage 5.1: building 32 bit shim libraries >>>>>> World build completed on Sat Dec 24 23:35:25 UTC 2011 >>> >>> TB --- 2011-12-24 23:35:25 - generating LINT kernel config >>> TB --- 2011-12-24 23:35:25 - cd /src/sys/powerpc/conf >>> TB --- 2011-12-24 23:35:25 - /usr/bin/make -B LINT >>> TB --- 2011-12-24 23:35:25 - cd /src/sys/powerpc/conf >>> TB --- 2011-12-24 23:35:25 - /usr/sbin/config -m LINT >>> TB --- 2011-12-24 23:35:25 - building LINT kernel >>> TB --- 2011-12-24 23:35:25 - CROSS_BUILD_TESTING=YES >>> TB --- 2011-12-24 23:35:25 - MAKEOBJDIRPREFIX=/obj >>> TB --- 2011-12-24 23:35:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin >>> TB --- 2011-12-24 23:35:25 - SRCCONF=/dev/null >>> TB --- 2011-12-24 23:35:25 - TARGET=powerpc >>> TB --- 2011-12-24 23:35:25 - TARGET_ARCH=powerpc64 >>> TB --- 2011-12-24 23:35:25 - TZ=UTC >>> TB --- 2011-12-24 23:35:25 - __MAKE_CONF=/dev/null >>> TB --- 2011-12-24 23:35:25 - cd /src >>> TB --- 2011-12-24 23:35:25 - /usr/bin/make -B buildkernel KERNCONF=LINT >>>>>> >>>>>> Kernel build for LINT started on Sat Dec 24 23:35:25 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 >>> >>> [...] >>> cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs >> >> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline >> -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions >> -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. >> -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL >> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common >> -finline-limit=15000 --param inline-unit-growth=100 --param >> large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many >> -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc >> -ffreestanding -fstack-protector -Werror /src/sys/dev/fb/fb.c >>> >>> cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs >> >> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline >> -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions >> -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. >> -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL >> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common >> -finline-limit=15000 --param inline-unit-growth=100 --param >> large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many >> -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc >> -ffreestanding -fstack-protector -Werror /src/sys/dev/hwpmc/hwpmc_powerpc.c >>> >>> /src/sys/dev/hwpmc/hwpmc_powerpc.c: In function 'powerpc_intr': >>> /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'AMD_PMC_ENABLE' >> >> undeclared (first use in this function) >>> >>> /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: (Each undeclared >> >> identifier is reported only once >>> >>> /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: for each function it >> >> appears in.) >>> >>> /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no >> >> member named 'pm_amd' >>> >>> /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no >> >> member named 'pm_amd' >>> >>> *** Error code 1 >>> >>> Stop in /obj/powerpc.powerpc64/src/sys/LINT. >>> *** Error code 1 >>> >>> Stop in /src. >>> *** Error code 1 >>> >>> Stop in /src. >>> TB --- 2011-12-24 23:45:43 - WARNING: /usr/bin/make returned exit code 1 >>> TB --- 2011-12-24 23:45:43 - ERROR: failed to build LINT kernel >>> TB --- 2011-12-24 23:45:43 - 7497.27 user 1367.80 system 9118.84 real >>> >>> >>> http://tinderbox.freebsd.org/tinderbox-head-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-unsubscribe@freebsd.org" >> >> >> Sorry about this, bad patch when I tested the build. I'll fix it tomorrow >> when I get time. > > > Something like this? > > Andreas > > Index: hwpmc_powerpc.c > =================================================================== > --- hwpmc_powerpc.c (revision 228872) > +++ hwpmc_powerpc.c (working copy) > @@ -686,10 +686,10 @@ > v = pm->pm_sc.pm_reloadcount; > config = mfspr(SPR_MMCR0); > > - KASSERT((config & ~AMD_PMC_ENABLE) == > - (pm->pm_md.pm_amd.pm_amd_evsel & ~AMD_PMC_ENABLE), > + KASSERT((config & ~POWERPC_PMC_ENABLE) == > + (pm->pm_md.pm_powerpc.pm_powerpc_evsel & ~POWERPC_PMC_ENABLE), > ("[powerpc,%d] config mismatch reg=0x%x pm=0x%x", __LINE__, > - config, pm->pm_md.pm_amd.pm_amd_evsel)); > + config, pm->pm_md.pm_powerpc.pm_powerpc_evsel)); > > mtspr(SPR_MMCR0, config | SPR_MMCR0_FC); > powerpc_pmcn_write(i, v); > > It's fine to delete the assert, I sent Nathan a patch to do so, but don't expect to commit it until tonight or tomorrow. You could commit a deletion if you want. - Justin From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 13:15:55 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7E9F1065670; Sun, 25 Dec 2011 13:15:55 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 6E6CE8FC08; Sun, 25 Dec 2011 13:15:55 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.4) with ESMTP id pBPDFsk0028169; Sun, 25 Dec 2011 08:15:54 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.4/Submit) id pBPDFsWa028119; Sun, 25 Dec 2011 13:15:54 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 25 Dec 2011 13:15:54 GMT Message-Id: <201112251315.pBPDFsWa028119@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 13:15:55 -0000 TB --- 2011-12-25 11:06:31 - tinderbox 2.8 running on freebsd-current.sentex.ca TB --- 2011-12-25 11:06:31 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2011-12-25 11:06:31 - cleaning the object tree TB --- 2011-12-25 11:06:44 - cvsupping the source tree TB --- 2011-12-25 11:06:44 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2011-12-25 11:07:44 - building world TB --- 2011-12-25 11:07:44 - CROSS_BUILD_TESTING=YES TB --- 2011-12-25 11:07:44 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-25 11:07:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-25 11:07:44 - SRCCONF=/dev/null TB --- 2011-12-25 11:07:44 - TARGET=powerpc TB --- 2011-12-25 11:07:44 - TARGET_ARCH=powerpc TB --- 2011-12-25 11:07:44 - TZ=UTC TB --- 2011-12-25 11:07:44 - __MAKE_CONF=/dev/null TB --- 2011-12-25 11:07:44 - cd /src TB --- 2011-12-25 11:07:44 - /usr/bin/make -B buildworld >>> World build started on Sun Dec 25 11:07:45 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 Sun Dec 25 13:05:40 UTC 2011 TB --- 2011-12-25 13:05:40 - generating LINT kernel config TB --- 2011-12-25 13:05:40 - cd /src/sys/powerpc/conf TB --- 2011-12-25 13:05:40 - /usr/bin/make -B LINT TB --- 2011-12-25 13:05:40 - cd /src/sys/powerpc/conf TB --- 2011-12-25 13:05:40 - /usr/sbin/config -m LINT TB --- 2011-12-25 13:05:40 - building LINT kernel TB --- 2011-12-25 13:05:40 - CROSS_BUILD_TESTING=YES TB --- 2011-12-25 13:05:40 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-25 13:05:40 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-25 13:05:40 - SRCCONF=/dev/null TB --- 2011-12-25 13:05:40 - TARGET=powerpc TB --- 2011-12-25 13:05:40 - TARGET_ARCH=powerpc TB --- 2011-12-25 13:05:40 - TZ=UTC TB --- 2011-12-25 13:05:40 - __MAKE_CONF=/dev/null TB --- 2011-12-25 13:05:40 - cd /src TB --- 2011-12-25 13:05:40 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Dec 25 13:05:40 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 [...] cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/fb/fb.c cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/hwpmc/hwpmc_powerpc.c /src/sys/dev/hwpmc/hwpmc_powerpc.c: In function 'powerpc_intr': /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'AMD_PMC_ENABLE' undeclared (first use in this function) /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: (Each undeclared identifier is reported only once /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: for each function it appears in.) /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no member named 'pm_amd' /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no member named 'pm_amd' *** Error code 1 Stop in /obj/powerpc.powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-12-25 13:15:53 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-12-25 13:15:53 - ERROR: failed to build LINT kernel TB --- 2011-12-25 13:15:53 - 6252.92 user 1070.92 system 7762.48 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 13:39:10 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E45021065670 for ; Sun, 25 Dec 2011 13:39:10 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id C4BEE8FC0C for ; Sun, 25 Dec 2011 13:39:10 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1ReoI9-000297-0W; Sun, 25 Dec 2011 13:39:10 +0000 Date: Sun, 25 Dec 2011 08:39:02 -0500 Message-ID: From: Randy Bush To: FreeBSD current mailing list User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: Subject: lost inode, no backup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 13:39:11 -0000 FreeBSD ran.psg.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4: Sat Dec 24 12:33:51 UTC 2011 root@ran.psg.com:/usr/obj/usr/src/sys/RAN amd64 so doing all the wonderful holiday security upgrades and hit an ugly. these two problems may not be related. ---- problem one on reboot, /usr/home was empty, as iff the inode had been lost. but no lost+found and fsck found no problem. # df -H Filesystem Size Used Avail Capacity Mounted on /dev/da0s1a 5.2G 1.6G 3.1G 34% / devfs 1.0k 1.0k 0B 100% /dev /dev/da0s1d 2.1G 356M 1.6G 19% /var /dev/da0s1e 2.1G 1.8M 1.9G 0% /var/spool /dev/da0s1f 138G 111G 15G 88% /usr /dev/md0 259M 36k 238M 0% /tmp and we know /usr/home was fine before the reboot as i was running out of it, backup ran out of it, ... ---- problem two so i go for the local raid which is the target of the ever faithful backup job, the essence of which is # 4 - /usr /sbin/dump 0Luaf - /dev/da0s1f | $SSH $USYS "/bin/cat > $DDIR/usr" and which had run quite happily a few hours before DUMP: Date of this level 0 dump: Sat Dec 24 00:47:42 2011 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/da0s1f (/usr) to standard output DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 56969906 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 0.78% done, finished in 10:36 at Sat Dec 24 11:29:34 2011 DUMP: 1.52% done, finished in 10:47 at Sat Dec 24 11:45:15 2011 ... DUMP: 97.88% done, finished in 0:05 at Sat Dec 24 05:13:38 2011 DUMP: DUMP: 56980137 tape blocks DUMP: finished in 15750 seconds, throughput 3617 KBytes/sec DUMP: level 0 dump on Sat Dec 24 00:47:42 2011 DUMP: DUMP IS DONE except that on all backups since the system moved to 10-current, home is empty in the usr file!!! all other directories there are good. and we know /usr/home was good, see above. the bleeping dump user has its directory there. ---- luckily i had other means of restoring. but wtf? randy From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 14:12:30 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1C6C106564A; Sun, 25 Dec 2011 14:12:30 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 9784D8FC0C; Sun, 25 Dec 2011 14:12:30 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.4) with ESMTP id pBPECTVO077596; Sun, 25 Dec 2011 09:12:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.4/Submit) id pBPECTC2077595; Sun, 25 Dec 2011 14:12:29 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 25 Dec 2011 14:12:29 GMT Message-Id: <201112251412.pBPECTC2077595@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc64/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 14:12:30 -0000 TB --- 2011-12-25 11:42:21 - tinderbox 2.8 running on freebsd-current.sentex.ca TB --- 2011-12-25 11:42:21 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2011-12-25 11:42:21 - cleaning the object tree TB --- 2011-12-25 11:42:46 - cvsupping the source tree TB --- 2011-12-25 11:42:46 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile TB --- 2011-12-25 11:43:00 - building world TB --- 2011-12-25 11:43:00 - CROSS_BUILD_TESTING=YES TB --- 2011-12-25 11:43:00 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-25 11:43:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-25 11:43:00 - SRCCONF=/dev/null TB --- 2011-12-25 11:43:00 - TARGET=powerpc TB --- 2011-12-25 11:43:00 - TARGET_ARCH=powerpc64 TB --- 2011-12-25 11:43:00 - TZ=UTC TB --- 2011-12-25 11:43:00 - __MAKE_CONF=/dev/null TB --- 2011-12-25 11:43:00 - cd /src TB --- 2011-12-25 11:43:00 - /usr/bin/make -B buildworld >>> World build started on Sun Dec 25 11:43:00 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Sun Dec 25 14:02:20 UTC 2011 TB --- 2011-12-25 14:02:20 - generating LINT kernel config TB --- 2011-12-25 14:02:20 - cd /src/sys/powerpc/conf TB --- 2011-12-25 14:02:20 - /usr/bin/make -B LINT TB --- 2011-12-25 14:02:20 - cd /src/sys/powerpc/conf TB --- 2011-12-25 14:02:20 - /usr/sbin/config -m LINT TB --- 2011-12-25 14:02:20 - building LINT kernel TB --- 2011-12-25 14:02:20 - CROSS_BUILD_TESTING=YES TB --- 2011-12-25 14:02:20 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-25 14:02:20 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-25 14:02:20 - SRCCONF=/dev/null TB --- 2011-12-25 14:02:20 - TARGET=powerpc TB --- 2011-12-25 14:02:20 - TARGET_ARCH=powerpc64 TB --- 2011-12-25 14:02:20 - TZ=UTC TB --- 2011-12-25 14:02:20 - __MAKE_CONF=/dev/null TB --- 2011-12-25 14:02:20 - cd /src TB --- 2011-12-25 14:02:20 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Dec 25 14:02:20 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 [...] cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/dev/fb/fb.c cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/dev/hwpmc/hwpmc_powerpc.c /src/sys/dev/hwpmc/hwpmc_powerpc.c: In function 'powerpc_intr': /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'AMD_PMC_ENABLE' undeclared (first use in this function) /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: (Each undeclared identifier is reported only once /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: for each function it appears in.) /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no member named 'pm_amd' /src/sys/dev/hwpmc/hwpmc_powerpc.c:689: error: 'union pmc_md_pmc' has no member named 'pm_amd' *** Error code 1 Stop in /obj/powerpc.powerpc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-12-25 14:12:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-12-25 14:12:29 - ERROR: failed to build LINT kernel TB --- 2011-12-25 14:12:29 - 7456.03 user 1357.92 system 9008.17 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc64-powerpc.full From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 14:30:50 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D35651065672; Sun, 25 Dec 2011 14:30:50 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) by mx1.freebsd.org (Postfix) with ESMTP id 5C6E98FC1D; Sun, 25 Dec 2011 14:30:50 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 2CB0825D389E; Sun, 25 Dec 2011 14:30:48 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 1ACB6BD7C22; Sun, 25 Dec 2011 14:30:48 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id 8XiOYk7iSTXH; Sun, 25 Dec 2011 14:30:47 +0000 (UTC) Received: from orange-en1.sbone.de (orange-en1.sbone.de [IPv6:fde9:577b:c1a9:31:cabc:c8ff:fecf:e8e3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id E8704BD7C21; Sun, 25 Dec 2011 14:30:46 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Bjoern A. Zeeb" In-Reply-To: Date: Sun, 25 Dec 2011 14:30:45 +0000 Content-Transfer-Encoding: 7bit Message-Id: <7139CFFA-1DEA-4739-B689-B7DB03B4B625@FreeBSD.org> References: <201112242345.pBONjh5K008411@freebsd-current.sentex.ca> <4EF6F633.80803@fgznet.ch> To: Justin Hibbits X-Mailer: Apple Mail (2.1084) Cc: powerpc64@freebsd.org, Andreas Tobler , FreeBSD Tinderbox , current@freebsd.org Subject: Re: [head tinderbox] failure on powerpc64/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 14:30:50 -0000 On 25. Dec 2011, at 11:42 , Justin Hibbits wrote: >>> Sorry about this, bad patch when I tested the build. I'll fix it tomorrow >>> when I get time. >> >> >> Something like this? >> >> Andreas >> >> Index: hwpmc_powerpc.c >> =================================================================== >> --- hwpmc_powerpc.c (revision 228872) >> +++ hwpmc_powerpc.c (working copy) >> @@ -686,10 +686,10 @@ >> v = pm->pm_sc.pm_reloadcount; >> config = mfspr(SPR_MMCR0); >> >> - KASSERT((config & ~AMD_PMC_ENABLE) == >> - (pm->pm_md.pm_amd.pm_amd_evsel & ~AMD_PMC_ENABLE), >> + KASSERT((config & ~POWERPC_PMC_ENABLE) == >> + (pm->pm_md.pm_powerpc.pm_powerpc_evsel & > ~POWERPC_PMC_ENABLE), >> ("[powerpc,%d] config mismatch reg=0x%x pm=0x%x", > __LINE__, >> - config, pm->pm_md.pm_amd.pm_amd_evsel)); >> + config, pm->pm_md.pm_powerpc.pm_powerpc_evsel)); >> >> mtspr(SPR_MMCR0, config | SPR_MMCR0_FC); >> powerpc_pmcn_write(i, v); >> >> > > It's fine to delete the assert, I sent Nathan a patch to do so, but don't > expect to commit it until tonight or tomorrow. You could commit a deletion > if you want. I just did in r228874. Happy holidays, /bz -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 14:55:28 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CD80106566B for ; Sun, 25 Dec 2011 14:55:28 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea]) by mx1.freebsd.org (Postfix) with ESMTP id 313C98FC12 for ; Sun, 25 Dec 2011 14:55:28 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 07E079E08E for ; Sun, 25 Dec 2011 15:55:26 +0100 (CET) From: Stefan Bethke Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sun, 25 Dec 2011 15:55:26 +0100 Message-Id: To: freebsd-current@freebsd.org Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) Subject: Why does kern.module_path use ";" and not ":"? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 14:55:28 -0000 I just got tripped up by this difference in a minor way. Is there a = particular reason kern_linker uses semicolon as a seperator instead of = the more common colon? Stefan --=20 Stefan Bethke Fon +49 151 14070811 From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 15:09:59 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B93BD106564A; Sun, 25 Dec 2011 15:09:59 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.freebsd.org (Postfix) with ESMTP id 3A1B68FC15; Sun, 25 Dec 2011 15:09:58 +0000 (UTC) Received: from c211-30-171-136.carlnfd1.nsw.optusnet.com.au (c211-30-171-136.carlnfd1.nsw.optusnet.com.au [211.30.171.136]) by mail03.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id pBPF9su1010312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Dec 2011 02:09:56 +1100 Date: Mon, 26 Dec 2011 02:09:54 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Alexander Best In-Reply-To: <20111224121425.GA31084@freebsd.org> Message-ID: <20111226003337.Y805@besplex.bde.org> References: <20111223235642.GA37495@freebsd.org> <20111224160050.T1141@besplex.bde.org> <20111224093753.GA12377@freebsd.org> <20111224222040.Q2266@besplex.bde.org> <20111224121425.GA31084@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Sun, 25 Dec 2011 15:22:56 +0000 Cc: freebsd-current@FreeBSD.ORG, Bruce Evans , freebsd-arch@FreeBSD.ORG Subject: Re: [rfc] removing -mpreferred-stack-boundary=2 flag for i386? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 15:09:59 -0000 On Sat, 24 Dec 2011, Alexander Best wrote: > On Sat Dec 24 11, Bruce Evans wrote: >> On Sat, 24 Dec 2011, Alexander Best wrote: >> >>> On Sat Dec 24 11, Bruce Evans wrote: >>>> On Fri, 23 Dec 2011, Alexander Best wrote: >>> ... >>>>> the gcc(1) man page states the following: >>>>> >>>>> " >>>>> This extra alignment does consume extra stack space, and generally >>>>> increases code size. Code that is sensitive to stack space usage, >>>>> such as embedded systems and operating system kernels, may want to >>>>> reduce the preferred alignment to -mpreferred-stack-boundary=2. >>>>> " >>>>> >>>>> the comment in sys/conf/kern.mk however sorta suggests that the default >>>>> alignment of 4 bytes might improve performance. >>>> >>>> The default stack alignment is 16 bytes, which unimproves performance. >>> >>> maybe the part of the comment in sys/conf/kern.mk, which mentions that a >>> stack >>> alignment of 16 bytes might improve micro benchmark results should be >>> removed. >>> this would prevent people (like me) from thinking, using a stack alignment >>> of >>> 4 bytes is a compromise between size and efficiently. it isn't! currently a >>> stack alignment of 16 bytes has no advantages towards one with 4 bytes on >>> i386. >> >> I think the comment is clear enough. It it mentions all the tradeoffs. >> It is only slightly cryptic in saying that these are tradeoffs and that >> the configuration is our best guess at the best tradeoff -- it just says >> "while" for both. It goes without saying that we don't use our worst >> guess. Anyone wanting to change this should run benchmarks and beware >> that micro-benchmarks are especially useless. The changed comment is not >> so good since it no longer mentions micro-bencharmarks or says "while". > > if micro benchmark results aren't of any use, why should the claim that the > default stack alignment of 16 bytes might produce better outcome stay? Because: - the actual claim is the opposite of that (it is that the default 16-byte alignments is probably a loss overall) - the claim that the default 16-byte alignment may benefit micro-benchmarks is true, even without the weaselish miswording of "might" in it. There is always at least 1 micro-benchmark that will benefit from almost any change, and here we expect a benefit in many microbenchmarks that don't bust the caches. Except, 16-byte alignment isn't supported (*) in the kernel, so we actually expect a loss from many microbenchmarks that don't bust the caches. - the second claim warns inexperienced benchmarkers not to claim that the default is better because it is better in microbenchmarks. > it doesn't seem as if anybody has micro benchmarked 16 bytes vs. 4 bytes stack > alignment, until now. so the micro benchmark statement in the comment seems to > be pure speculation. No, it is obviously true. > even worse...it indicates that by removing the > -mpreferred-stack-boundary=2 flag, one can gain a performance boost by > sacrifying a few more bytes of kernel (and module) size. No, it is part of the sentence explaining why removing the -mpreferred-stack-boundary=2 flag will probably regain the "overall loss" that is avoided by using the flag. > this suggests that the behavior -mpreferred-stack-boundary=2 vs. not specyfing > it, losely equals the semantics of -Os vs. -O2. No, -Os guarantees slower execution by forcing optimization to prefer space savings over time savings in more ways. Except, -Os is completely broken in -current (in the kernel), and gives very large negative space savings (about 50%). It last worked with gcc-3. Its brokenness with gcc-4 is related to kern.pre.mk still specifying -finline-limit flags that are more suitable for gcc-3 (gcc has _many_ flags for giving more delicate control over inlining, and better defaults for them) and excessive inlining in gcc-4 given by -funit-at-a-time -finline-functions-called-once. These apparently cause gcc's inliner to go insane with -Os. When I tried to fix this by reducing inlining, I couldn't find any threshold that fixed -Os without breaking inlining of functions that are declared inline. (*) A primary part of the lack of support for 16-byte stack alignment in the kernel no special stack alignment for the main kernel entry point, namely syscall(). From i386/exception.s: % SUPERALIGN_TEXT % IDTVEC(int0x80_syscall) At this point, the stack has 5 words on it (it was 16-byte aligned before that). % pushl $2 /* sizeof "int 0x80" */ % subl $4,%esp /* skip over tf_trapno */ % pushal % pushl %ds % pushl %es % pushl %fs % SET_KERNEL_SREGS % cld % FAKE_MCOUNT(TF_EIP(%esp)) % pushl %esp We "push" 14 more words. This gives perfect misaligment to the worst odd word boundary (perfect if only word boundaries are allowed). gcc wants the stack to be aligned to a 4*n word boundary before function calls, but here we have a 4*n+3 word boundary. (4*n+3 is worse than 4*n+1 since 2 more words instead of 4 will cross the next 16-byte boundary). % call syscall Using the default -mpreferred-stack-boundary will preserve the perfect misaligment across all C functions called by syscall(). % add $4, %esp % MEXITCOUNT % jmp doreti Old versions didn't have the pessimization of pushing the frame pointer. This is a minor pessimization, except it uses more stack, unless you use the default -mpreferred-stack-boundary. Without this, only 18 words were pushed, so the misalignment was imperfect (to a 4*n+2 word boundary). If the default stack alignment is any use at all (in the kernel), then it is mainly to prevent 64-bit data types being laid out across cache line boundaries. Alignment to a 4*n+2 word boundary gives that just as well as alignment to a 4*n+0 word boundary. I tested using the default -mpreferred-stack-boundary in FreeBSD-~5.2, which doesn't push the frame pointer. This gave the expected results, except the optimization for a microbenchmark was surprisingly large. For a macro-benchmark, I built some kernels. This seemed to take a little longer (about 0.2%, and not statistically significant). But the time for a clock_gettime() microbenchmark was reduced from 271 ns per call to 263.5 ns per call. That's with the stack for clock_gettime() imperfectly misaligned to a 4*n+2 word boundary. But changing the stack alignment by subtracting more from the stack in syscons made little difference, unless it was changed to an odd byte boundary (then clock_gettime() took about 324 ns). amd64 is of course more careful about this (since its ABI requires 16-byte alignment). According to log messages, the initial %rsp (before anything is pushed onto it in the above) is offset by 8 bytes or so, as necessary to make the final %rsp come out aligned. Pushing the frame pointer would have broken this. However, on amd64, the first arg is passed in %rdi, so there is no push to pass the frame pointer and the stack remains aligned. When the frame pointer was passed "by reference", adjusting the stack after the pushes would have broken the reference, so the offset method was essential. Now it is not needed (unless we want or need frame to be aligned, since %rdi can pass the frame pointer wherever the frame is, and the offset method becomes a minor optimization. If you remove the -mpreferred-stack-boundary=2 optimization, be sure to remove this one too, since it is tinier. Bruce From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 15:48:38 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B1A4106566C; Sun, 25 Dec 2011 15:48:38 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (lrosenman-1-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:3ad::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1CB438FC08; Sun, 25 Dec 2011 15:48:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-Type:MIME-Version:References:Message-ID:In-Reply-To:Subject:cc:To:Sender:From:Date; bh=ORUNhMAxkLHdMtI9imwlqSeJkwuSihtsqKf+BePc66g=; b=F+n7H1p386jMO5vruKzfs0Z3MOvNmQwqIV3tJS5J7x7DgnTh9zIBrmlagRQF/1aXwoghbB+j3MC2lzOLUfV8rdAdFE2sn31iXizCWuxJB8CNqFOUElWgdrQmb8HNK6NaJnm07k4aWd4Is+k3GGiB4+gP5wkMxLBgvjymHlu4hiw=; Received: from cpe-72-177-69-180.austin.res.rr.com ([72.177.69.180]:41323 helo=borg) by thebighonker.lerctr.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1ReqJQ-000Duq-9L; Sun, 25 Dec 2011 09:48:37 -0600 Date: Sun, 25 Dec 2011 09:48:32 -0600 (CST) From: Larry Rosenman Sender: ler@borg To: John Baldwin In-Reply-To: <4EF4AF5C.1060000@lerctr.org> Message-ID: References: <4EF48065.8000802@lerctr.org> <201112230954.57591.jhb@freebsd.org> <4EF4AF5C.1060000@lerctr.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: -2.9 (--) X-LERCTR-Spam-Score: -2.9 (--) X-Spam-Report: SpamScore (-2.9/5.0) ALL_TRUSTED=-1,BAYES_00=-1.9 X-LERCTR-Spam-Report: SpamScore (-2.9/5.0) ALL_TRUSTED=-1,BAYES_00=-1.9 Cc: Alexander Motin , freebsd-current@freebsd.org Subject: Re: scheduler panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 15:48:38 -0000 On Fri, 23 Dec 2011, Larry Rosenman wrote: > On 12/23/2011 8:54 AM, John Baldwin wrote: >> The sloppiest fix might be to do this: >> >> Index: sched_ule.c >> =================================================================== >> >> > - --- sched_ule.c (revision 228777) >> +++ sched_ule.c (working copy) @@ -1434,7 +1434,8 @@ >> sched_priority(struct thread *td) } else { pri = SCHED_PRI_MIN; if >> (td->td_sched->ts_ticks) - pri += SCHED_PRI_TICKS(td->td_sched); >> + pri += min(SCHED_PRI_TICKS(td->td_sched), + >> SCHED_PRI_RANGE); pri += SCHED_PRI_NICE(td->td_proc->p_nice); >> KASSERT(pri >= PRI_MIN_BATCH && pri <= PRI_MAX_BATCH, >> ("sched_priority: invalid priority %d: nice %d, " >> > > I've applied this to both the host and the guest, and am recompiling > the guest kernel (hopefully it'll stay up long enough...). > > I'll report back. > > Do y'all (FreeBSD Devs) want a PR? > > I've run 2 complete buildworld/buildkernel cycles with the patch applied in the guest, and it's made it all the way through. It wouldn't do that without it. Can we get this (or something else like it) applied? Do I need to file a PR? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 16:01:41 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06BDF1065672; Sun, 25 Dec 2011 16:01:41 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from forward10.mail.yandex.net (forward10.mail.yandex.net [IPv6:2a02:6b8:0:202::5]) by mx1.freebsd.org (Postfix) with ESMTP id 17E798FC17; Sun, 25 Dec 2011 16:01:40 +0000 (UTC) Received: from smtp9.mail.yandex.net (smtp9.mail.yandex.net [77.88.61.35]) by forward10.mail.yandex.net (Yandex) with ESMTP id 4118610225DC; Sun, 25 Dec 2011 20:01:38 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1324828898; bh=IlbN3TjqAn+dhOz/gzskEBYjDpZsZpIjNL0B1VDZ/HU=; h=Date:From:Reply-To:Message-ID:To:CC:Subject:In-Reply-To: References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=O1uEpugWBedkPBsX5T4/1yQs0epHDnmjFw984WHU2DcgZWpJpecVU0miv5evnRmd1 ybEIpWgjj62lQoj8JR3RmbDdnT+fvY/LTxej+fYwrHJCY/B+kK7gtEAP6MRxAgaBI2 Q+XPSq4EWhpr3dmlSuNmME70tkaCoEKzzH6n/ewE= Received: from smtp9.mail.yandex.net (localhost [127.0.0.1]) by smtp9.mail.yandex.net (Yandex) with ESMTP id D953715203E1; Sun, 25 Dec 2011 20:01:37 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1324828898; bh=IlbN3TjqAn+dhOz/gzskEBYjDpZsZpIjNL0B1VDZ/HU=; h=Date:From:Reply-To:Message-ID:To:CC:Subject:In-Reply-To: References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=O1uEpugWBedkPBsX5T4/1yQs0epHDnmjFw984WHU2DcgZWpJpecVU0miv5evnRmd1 ybEIpWgjj62lQoj8JR3RmbDdnT+fvY/LTxej+fYwrHJCY/B+kK7gtEAP6MRxAgaBI2 Q+XPSq4EWhpr3dmlSuNmME70tkaCoEKzzH6n/ewE= Received: from unknown (unknown [77.93.52.22]) by smtp9.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 1bBmZVVa-1bBC6wHY; Sun, 25 Dec 2011 20:01:37 +0400 X-Yandex-Spam: 1 Date: Sun, 25 Dec 2011 18:01:33 +0200 From: =?utf-8?B?0JrQvtC90YzQutC+0LIg0JXQstCz0LXQvdC40Lk=?= X-Mailer: The Bat! (v4.0.24) Professional Organization: =?utf-8?B?0KfQnyDQmtC+0L3RjNC60L7QsiwgRnJlZUxpbmU=?= X-Priority: 3 (Normal) Message-ID: <1632420869.20111225180133@yandex.ru> To: John Baldwin In-Reply-To: <201112200952.44690.jhb@freebsd.org> References: <20111022084931.GD1697@garage.freebsd.pl> <201112121100.23567.jhb@freebsd.org> <20111217232125.GA1685@garage.freebsd.pl> <201112200952.44690.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Sun, 25 Dec 2011 16:33:53 +0000 Cc: Andre Oppermann , freebsd-net@freebsd.org, Pawel Jakub Dawidek , freebsd-current@freebsd.org, Kostik Belousov , Lawrence Stewart Subject: Re[2]: 9.0-RC1 panic in tcp_input: negative winow. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?utf-8?B?0JrQvtC90YzQutC+0LIg0JXQstCz0LXQvdC40Lk=?= List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 16:01:41 -0000 Çäðàâñòâóéòå, John. Âû ïèñàëè 20 äåêàáðÿ 2011 ã., 16:52:44: JB> On Saturday, December 17, 2011 6:21:27 pm Pawel Jakub Dawidek wrote: >> On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote: >> > An update. I've sent Pawel a testing patch to see if my hypothesis is correct >> > (www.freebsd.org/~jhb/patches/tcp_negwin_test.patch). If it is then I intend >> > to commit www.freebsd.org/~jhb/patches/tcp_negwin2.patch as the fix. >> >> Unfortunately it paniced today. Take a look at: >> >> http://people.freebsd.org/~pjd/misc/tcp_panic.jpg JB> Ok, the one use case I was worried about is happening regularly before your JB> panic, so that is good. Can you use gdb to figure out which call to JB> tcp_output() is actually panic'ing? I wonder if it is this case: JB> /* JB> * Return any desired output. JB> */ JB> if (needoutput || (tp->t_flags & TF_ACKNOW)) { JB> (void) tcp_output(tp); JB> /* XXX: Debug */ JB> KASSERT(SEQ_GEQ(tp->rcv_adv, tp->rcv_nxt), JB> ("tcp_input: negative window after ACK")); JB> And if 'needoutput' is true, but TF_ACKNOW is not set, and tcp_output() decides JB> to not do anything. I've updated tcp_negwin_test.patch to not panic if that call JB> to tcp_output() doesn't actually send a packet. Please re-test. # uname -a FreeBSD meta-up 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #4: Sat Dec 24 13:59:20 EET 2011 @:/usr/obj/usr/src/sys/KES_KERN_v10 i386 rebooting once per day. Now I compile kernel with debug options. Can you advice me which and where I find debug info when it will reboting next time? so I can help to debug problem -- Ñ óâàæåíèåì, Êîíüêîâ mailto:kes-kes@yandex.ru From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 18:06:55 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D1921065677 for ; Sun, 25 Dec 2011 18:06:55 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3AB5F8FC1D for ; Sun, 25 Dec 2011 18:06:54 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so9315907obb.13 for ; Sun, 25 Dec 2011 10:06:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.192.103 with SMTP id hf7mr19651101obc.29.1324836414049; Sun, 25 Dec 2011 10:06:54 -0800 (PST) Received: by 10.182.220.33 with HTTP; Sun, 25 Dec 2011 10:06:54 -0800 (PST) X-Originating-IP: [93.221.170.138] In-Reply-To: References: Date: Sun, 25 Dec 2011 19:06:54 +0100 Message-ID: From: "C. P. Ghost" To: Stefan Bethke Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: Why does kern.module_path use ";" and not ":"? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 18:06:55 -0000 On Sun, Dec 25, 2011 at 3:55 PM, Stefan Bethke wrote: > I just got tripped up by this difference in a minor way. =A0Is there a pa= rticular reason kern_linker uses semicolon as a seperator instead of the mo= re common colon? A comment in /usr/src/sys/kern/kern_linker.c says: * The search path can be manipulated via sysctl. Note that we use the ';' * character as a separator to be consistent with the bootloader. And the bootloader uses the ';' as path separator, see loader(8): bootfile List of semicolon-separated search path for bootable kernels. The default is ``kernel''. > Stefan > > -- > Stefan Bethke =A0 Fon +49 151 14070811 Regards, -cpghost. --=20 Cordula's Web. http://www.cordula.ws/ From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 21:40:33 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 1592A1065673; Sun, 25 Dec 2011 21:40:33 +0000 (UTC) Date: Sun, 25 Dec 2011 21:40:33 +0000 From: Alexander Best To: freebsd-current@freebsd.org Message-ID: <20111225214033.GA1933@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="liOOAslEiF7prFVr" Content-Disposition: inline Subject: starting the annual discussion regarding top(1)'s CPU usage statistics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 21:40:33 -0000 --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline ok...so we all know that top(1) cannot compute the exact CPU usage for all processes, since some processes get spawned and exit so fast that they don't fall into the calculation range. i think nobody is getting angry when top(1) is off by a few percent. however please take a look at the following top(1) output. this is just ridiculous! out of 800% of CPU power, almost 600% mysteriously vanished. is there really nothing to improve top(1)'s behaviour when the CPU is dealing with a lot of short processes (time wise) with a hugh CPU burst? this output was gathered on HEAD (r227491) running on i386. cheers. alex ps: no, switching between raw and weighted CPU stats did *not* make a difference. ;) --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ridiculous-top-ouput.txt" last pid: 1489; load averages: 7.58, 7.73, 7.01 up 10+01:22:28 21:21:04 170 processes: 2 running, 167 sleeping, 1 waiting CPU 0: 13.4% user, 0.0% nice, 13.4% system, 3.9% interrupt, 69.3% idle CPU 1: 48.8% user, 0.0% nice, 20.8% system, 0.0% interrupt, 30.4% idle CPU 2: 52.8% user, 0.0% nice, 24.8% system, 0.0% interrupt, 22.4% idle CPU 3: 59.2% user, 0.0% nice, 19.2% system, 0.0% interrupt, 21.6% idle CPU 4: 70.4% user, 0.0% nice, 17.6% system, 0.0% interrupt, 12.0% idle CPU 5: 42.5% user, 0.0% nice, 20.5% system, 0.0% interrupt, 37.0% idle CPU 6: 59.5% user, 0.0% nice, 16.7% system, 0.0% interrupt, 23.8% idle CPU 7: 55.2% user, 0.0% nice, 9.6% system, 0.0% interrupt, 35.2% idle Mem: 333M Active, 6577M Inact, 332M Wired, 4436K Cache, 111M Buf, 763M Free Swap: 8192M Total, 444K Used, 8191M Free PID UID THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 0 8 155 ki31 0K 64K CPU7 7 1718.7 200.00% [idle] 12 0 18 -84 - 0K 144K WAIT 0 73:49 3.76% [intr] 1238 1233 1 52 0 8032K 552K wait 5 0:00 0.10% [cc] 1234 1233 1 52 0 9936K 1440K wait 2 0:00 0.10% sh -ev 1236 1233 1 52 0 9936K 1492K wait 2 0:00 0.10% [sh] 7 0 1 16 - 0K 8K syncer 0 55:42 0.00% [syncer] 13 0 3 -8 - 0K 24K - 2 13:43 0.00% [geom] 14 0 1 -16 - 0K 8K - 1 3:31 0.00% [yarrow] 9 0 1 -16 - 0K 8K sdflus 4 3:00 0.00% [softdepflush] 566 0 1 20 0 12128K 2380K select 5 2:59 0.00% /sbin/devd 8 0 1 -16 - 0K 8K vlruwt 2 1:32 0.00% [vnlru] 3 0 1 -16 - 0K 8K psleep 3 1:29 0.00% [pagedaemon] 6 0 1 -16 - 0K 8K psleep 1 1:13 0.00% [bufdaemon] 811 0 1 20 0 9784K 1356K select 1 0:22 0.00% /usr/sbin/rpcbind 975 0 1 20 0 11320K 1928K select 3 0:21 0.00% /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var 1043 0 1 20 0 13080K 2396K select 2 0:20 0.00% /usr/sbin/sshd 1050 0 1 20 0 11340K 2356K select 3 0:12 0.00% sendmail: accepting connections (sendmail) 1006 1 1 20 0 9540K 1088K sbwait 4 0:09 0.00% /usr/sbin/rwhod 1 0 1 20 0 8032K 352K wait 7 0:09 0.00% [init] 1063 0 1 28 0 9656K 1388K nanslp 0 0:07 0.00% /usr/sbin/cron -s 735 0 1 20 0 9624K 1192K select 0 0:06 0.00% /usr/sbin/syslogd -s 814 0 1 20 0 9552K 1308K select 1 0:04 0.00% /usr/sbin/ypbind 0 0 8 -52 0 0K 64K - 7 0:03 0.00% [kernel] 937 0 1 20 0 4408K 404K nanslp 2 0:03 0.00% /root/mfid clusteradm@freebsd.org 59391 1233 1 52 0 28512K 23144K select 6 0:02 0.00% make DIRPRFX=lib/libc/ all 75317 1233 1 52 0 20320K 14032K select 1 0:01 0.00% make DIRPRFX=secure/lib/libcrypto/ all 17282 1233 1 20 0 8032K 616K select 1 0:01 0.00% make buildworld TARGET=arm TARGET_ARCH=armeb 17285 1233 1 20 0 8032K 616K select 6 0:01 0.00% make buildworld TARGET=amd64 TARGET_ARCH=amd64 17279 1233 1 20 0 8032K 616K select 0 0:01 0.00% make buildworld TARGET=arm TARGET_ARCH=arm 17299 1233 1 20 0 8032K 616K select 1 0:01 0.00% make buildworld TARGET=mips TARGET_ARCH=mipsel 17290 1233 1 20 0 8032K 616K select 2 0:01 0.00% make buildworld TARGET=mips TARGET_ARCH=mipseb 17293 1233 1 20 0 8032K 616K select 1 0:01 0.00% make buildworld TARGET=mips TARGET_ARCH=mips64el 17298 1233 1 20 0 8032K 616K select 2 0:01 0.00% make buildworld TARGET=mips TARGET_ARCH=mipsn32eb 17294 1233 1 20 0 8032K 616K select 3 0:01 0.00% make buildworld TARGET=mips TARGET_ARCH=mips64eb 17919 1233 1 20 0 8032K 996K select 1 0:01 0.00% make -m /dumpster/home/arundel/src/share/mk -f Makefile.inc1 17928 1233 1 20 0 8032K 932K select 0 0:01 0.00% make -m /dumpster/home/arundel/src/share/mk -f Makefile.inc1 18122 1233 1 20 0 8032K 996K select 6 0:01 0.00% /scratch/tmp/arundel/obj/dumpster/home/arundel/src/make.i386 17946 1233 1 20 0 8032K 928K select 7 0:01 0.00% make -m /dumpster/home/arundel/src/share/mk -f Makefile.inc1 17902 1233 1 20 0 8032K 932K select 1 0:01 0.00% make -m /dumpster/home/arundel/src/share/mk -f Makefile.inc1 17950 1233 1 20 0 8032K 936K select 3 0:01 0.00% make -m /dumpster/home/arundel/src/share/mk -f Makefile.inc1 17940 1233 1 20 0 8032K 932K select 5 0:01 0.00% make -m /dumpster/home/arundel/src/share/mk -f Makefile.inc1 17951 1233 1 20 0 8032K 932K select 2 0:01 0.00% make -m /dumpster/home/arundel/src/share/mk -f Makefile.inc1 96695 1233 1 20 0 15820K 4344K select 6 0:00 0.00% sshd: arundel@pts/2 (sshd) 37628 937 1 20 0 10280K 2104K select 4 0:00 0.00% screen -e^Bb 97334 1233 1 20 0 8032K 992K select 1 0:00 0.00% /scratch/tmp/arundel/obj/dumpster/home/arundel/src/make.i386 92868 1233 1 20 0 8032K 928K select 3 0:00 0.00% make -f Makefile.inc1 DESTDIR=/scratch/tmp/arundel/obj/mips. 91735 1233 1 20 0 8032K 928K select 5 0:00 0.00% make -f Makefile.inc1 DESTDIR=/scratch/tmp/arundel/obj/mips. 91731 1233 1 20 0 8032K 916K select 0 0:00 0.00% make -f Makefile.inc1 DESTDIR=/scratch/tmp/arundel/obj/arm.a 93498 1233 1 20 0 8032K 928K select 1 0:00 0.00% make -f Makefile.inc1 DESTDIR=/scratch/tmp/arundel/obj/mips. 92535 1233 1 20 0 8032K 928K select 3 0:00 0.00% make -f Makefile.inc1 DESTDIR=/scratch/tmp/arundel/obj/mips. 7980 1233 1 20 0 8032K 928K select 1 0:00 0.00% make -f Makefile.inc1 DESTDIR=/scratch/tmp/arundel/obj/mips. 18132 0 1 -16 - 0K 8K - 7 0:00 0.00% [nfsiod 0] 1056 25 1 20 0 11340K 2228K pause 1 0:00 0.00% sendmail: Queue runner@00:30:00 for /var/spool/clientmqueue 78679 1233 1 21 0 8032K 1020K select 6 0:00 0.00% /scratch/tmp/arundel/obj/dumpster/home/arundel/src/make.i386 75016 1233 1 21 0 8032K 952K select 2 0:00 0.00% make -f Makefile.inc1 _prebuild_libs 80527 1233 1 20 0 8032K 940K select 2 0:00 0.00% make -f Makefile.inc1 _prebuild_libs 79754 1233 1 47 0 8032K 940K select 2 0:00 0.00% make -f Makefile.inc1 _prebuild_libs 80938 1233 1 20 0 8032K 956K select 0 0:00 0.00% make -f Makefile.inc1 _prebuild_libs 79324 1233 1 46 0 8032K 940K select 5 0:00 0.00% make -f Makefile.inc1 _prebuild_libs 94045 1233 1 20 0 8032K 956K select 2 0:00 0.00% make -f Makefile.inc1 _prebuild_libs 36468 0 1 20 0 9656K 1440K pipewr 4 0:00 0.00% cron: running job (cron) 36466 0 1 20 0 9656K 1432K pipewr 3 0:00 0.00% cron: running job (cron) 98751 1233 1 52 0 8032K 3308K select 5 0:00 0.00% make DIRPRFX=kerberos5/lib/libroken/ all 47882 1233 1 20 0 8032K 968K select 1 0:00 0.00% make -f Makefile.inc1 _startup_libs 99001 1233 1 52 0 8032K 3188K select 3 0:00 0.00% make DIRPRFX=kerberos5/lib/libroken/ all 42348 1233 1 20 0 8032K 968K select 6 0:00 0.00% make -f Makefile.inc1 DESTDIR=/scratch/tmp/arundel/obj/amd64 99546 1233 1 52 0 8032K 2172K select 0 0:00 0.00% make DIRPRFX=secure/lib/libssl/ all 99544 1233 1 52 0 8032K 2292K select 2 0:00 0.00% /scratch/tmp/arundel/obj/dumpster/home/arundel/src/make.i386 96711 1233 1 20 0 3304K 2668K pause 0 0:00 0.00% -zsh (zsh) 1467 1233 1 52 0 16548K 10720K nfsreq 0 0:00 0.00% [cc1] 37630 937 1 20 0 10952K 2372K ttyin 4 0:00 0.00% /bin/tcsh 97311 0 1 24 0 15820K 4272K select 0 0:00 0.00% sshd: arundel [priv] (sshd) 4996 1233 1 20 0 8032K 676K select 0 0:00 0.00% make -j8 tinderbox 17207 1233 1 20 0 8032K 720K select 1 0:00 0.00% make DOING_TINDERBOX=YES universe 96675 0 1 21 0 15820K 4324K select 4 0:00 0.00% sshd: arundel [priv] (sshd) 4993 0 1 20 0 9656K 1492K piperd 3 0:00 0.00% cron: running job (cron) 97810 1233 1 20 0 15820K 4280K select 2 0:00 0.00% sshd: arundel@pts/8 (sshd) 97904 1233 1 30 0 3120K 2476K ttyin 2 0:00 0.00% -zsh (zsh) 2634 937 1 20 0 10952K 2348K ttyin 1 0:00 0.00% /bin/tcsh 1224 1233 1 52 0 8032K 908K select 2 0:00 0.00% make DIRPRFX=lib/libopie/ depend 1362 1233 1 52 0 8032K 908K select 5 0:00 0.00% make DIRPRFX=lib/libopie/ depend 1474 1233 1 52 0 13236K 6316K nfsreq 7 0:00 0.00% [cc1] 5 0 1 155 ki31 0K 8K pgzero 6 0:00 0.00% [pagezero] 1128 0 1 20 0 9624K 1052K ttyin 6 0:00 0.00% /usr/libexec/getty std.9600 ttyu0 1476 1233 1 52 0 13164K 5428K nfs 1 0:00 0.00% [cc1] 1477 1233 1 52 0 13164K 5428K nfsreq 6 0:00 0.00% [cc1] 1337 1233 1 20 0 9964K 1972K CPU5 5 0:00 0.00% top -P -d2 99999 1468 1233 1 52 0 8032K 4456K piperd 0 0:00 0.00% /scratch/tmp/arundel/obj/arm.arm/dumpster/home/arundel/src/t 1487 1233 1 52 0 8032K 4456K piperd 3 0:00 0.00% /scratch/tmp/arundel/obj/arm.armeb/dumpster/home/arundel/src 1125 0 1 52 0 9624K 1048K ttyin 6 0:00 0.00% /usr/libexec/getty Pc ttyv5 1122 0 1 52 0 9624K 1048K ttyin 5 0:00 0.00% /usr/libexec/getty Pc ttyv2 17276 1233 1 52 0 9936K 1440K wait 6 0:00 0.00% sh -ev 1123 0 1 52 0 9624K 1044K ttyin 1 0:00 0.00% /usr/libexec/getty Pc ttyv3 1124 0 1 52 0 9624K 1052K ttyin 3 0:00 0.00% /usr/libexec/getty Pc ttyv4 17277 1233 1 52 0 9936K 1440K wait 4 0:00 0.00% sh -ev 1368 1233 1 52 0 8032K 548K wait 5 0:00 0.00% [cc] 17275 1233 1 52 0 9936K 1440K wait 3 0:00 0.00% sh -ev 1120 0 1 52 0 9624K 1048K ttyin 2 0:00 0.00% /usr/libexec/getty Pc ttyv0 17269 1233 1 52 0 9936K 1440K wait 0 0:00 0.00% sh -ev 1126 0 1 52 0 9624K 1048K ttyin 4 0:00 0.00% /usr/libexec/getty Pc ttyv6 1121 0 1 52 0 9624K 1048K ttyin 5 0:00 0.00% /usr/libexec/getty Pc ttyv1 1127 0 1 52 0 9624K 1048K ttyin 0 0:00 0.00% /usr/libexec/getty Pc ttyv7 17893 1233 1 52 0 9936K 1444K wait 3 0:00 0.00% sh -ev 17274 1233 1 52 0 9936K 1440K wait 0 0:00 0.00% sh -ev 1485 1233 1 52 0 8032K 3080K piperd 6 0:00 0.00% /scratch/tmp/arundel/obj/mips.mips64eb/dumpster/home/arundel 17266 1233 1 52 0 9936K 1440K wait 2 0:00 0.00% sh -ev 17936 1233 1 52 0 9936K 1444K wait 6 0:00 0.00% sh -ev 92547 1233 1 32 0 9936K 1444K wait 6 0:00 0.00% sh -ev 17934 1233 1 52 0 9936K 1444K wait 4 0:00 0.00% sh -ev 97333 1233 1 29 0 9936K 1448K wait 3 0:00 0.00% sh -ev 17267 1233 1 52 0 9936K 1440K wait 2 0:00 0.00% sh -ev 17268 1233 1 52 0 9936K 1440K wait 5 0:00 0.00% sh -ev 17937 1233 1 52 0 9936K 1444K wait 1 0:00 0.00% sh -ev 1218 1233 1 52 0 9936K 1452K wait 2 0:00 0.00% sh -ev 98392 1233 1 46 0 9936K 1452K wait 1 0:00 0.00% sh -ev 98630 1233 1 52 0 9936K 1456K wait 0 0:00 0.00% sh -ev 98621 1233 1 52 0 9936K 1452K wait 0 0:00 0.00% sh -ev 1475 1233 1 52 0 8032K 3076K piperd 1 0:00 0.00% /scratch/tmp/arundel/obj/mips.mipsel/dumpster/home/arundel/s 97896 1233 1 45 0 9936K 1452K wait 5 0:00 0.00% sh -ev 17945 1233 1 52 0 9936K 1444K wait 1 0:00 0.00% sh -ev 42345 1233 1 31 0 9936K 1448K wait 7 0:00 0.00% sh -ev 97359 1233 1 32 0 9936K 1448K wait 1 0:00 0.00% sh -ev 66754 1233 1 37 0 9936K 1456K wait 1 0:00 0.00% sh -ev 36465 0 1 20 0 9656K 1440K ppwait 1 0:00 0.00% cron: running job (cron) 91730 1233 1 28 0 9936K 1448K wait 4 0:00 0.00% sh -ev 48744 1233 1 29 0 9936K 1456K wait 3 0:00 0.00% sh -ev 7999 1233 1 33 0 9936K 1448K wait 0 0:00 0.00% sh -ev 17921 1233 1 52 0 9936K 1444K wait 2 0:00 0.00% sh -ev 1351 1233 1 52 0 9936K 1452K wait 4 0:00 0.00% sh -ev 1478 1233 1 52 0 9936K 1432K wait 3 0:00 0.00% sh -ev 1367 1233 1 52 0 9936K 1492K wait 5 0:00 0.00% [sh] 17914 1233 1 52 0 9936K 1444K wait 5 0:00 0.00% sh -ev 92867 1233 1 27 0 9936K 1448K wait 3 0:00 0.00% sh -ev 1484 1233 1 52 0 13164K 4984K nfsreq 5 0:00 0.00% [cc1] 1365 1233 1 52 0 9936K 1440K wait 0 0:00 0.00% sh -ev 92887 1233 1 33 0 9936K 1444K wait 0 0:00 0.00% sh -ev 93509 1233 1 33 0 9936K 1448K wait 1 0:00 0.00% sh -ev 92534 1233 1 30 0 9936K 1448K wait 0 0:00 0.00% sh -ev 91743 1233 1 31 0 9936K 1452K wait 0 0:00 0.00% sh -ev 91733 1233 1 29 0 9936K 1448K wait 7 0:00 0.00% sh -ev 93497 1233 1 28 0 9936K 1448K wait 0 0:00 0.00% sh -ev 7979 1233 1 29 0 9936K 1448K wait 2 0:00 0.00% sh -ev 1481 1233 1 52 0 9936K 1436K wait 5 0:00 0.00% sh -ev 91750 1233 1 33 0 9936K 1444K wait 6 0:00 0.00% sh -ev 1480 1233 1 52 0 9936K 1432K wait 1 0:00 0.00% sh -ev 42369 1233 1 30 0 9936K 1448K wait 0 0:00 0.00% sh -ev 1486 1233 1 52 0 13164K 5068K nfsreq 2 0:00 0.00% [cc1] 18120 1233 1 37 0 9936K 1444K wait 0 0:00 0.00% sh -ev 1472 1233 1 52 0 9936K 1432K wait 6 0:00 0.00% sh -ev 1479 1233 1 52 0 8032K 516K nfsreq 1 0:00 0.00% [cc] 1488 1233 1 52 0 9936K 1432K wait 4 0:00 0.00% sh -ev 1483 1233 1 52 0 8032K 536K wait 1 0:00 0.00% [cc] 1465 1233 1 52 0 9936K 1436K wait 1 0:00 0.00% sh -ev 17206 1233 1 52 0 9936K 1444K wait 0 0:00 0.00% sh -ev 1482 1233 1 52 0 8032K 532K wait 2 0:00 0.00% [cc] 1473 1233 1 52 0 8032K 536K wait 0 0:00 0.00% [cc] 17283 1233 1 52 0 9936K 1452K wait 1 0:00 0.00% sh -ev 17292 1233 1 52 0 9936K 1452K wait 3 0:00 0.00% sh -ev 1466 1233 1 52 0 8032K 536K wait 0 0:00 0.00% [cc] 17295 1233 1 52 0 9936K 1452K wait 5 0:00 0.00% sh -ev 17291 1233 1 52 0 9936K 1452K wait 5 0:00 0.00% sh -ev 17296 1233 1 52 0 9936K 1452K wait 2 0:00 0.00% sh -ev 17280 1233 1 52 0 9936K 1452K wait 6 0:00 0.00% sh -ev 1489 1233 1 52 0 8032K 520K nfsreq 0 0:00 0.00% [cc] 17278 1233 1 52 0 9936K 1452K wait 5 0:00 0.00% sh -ev 17289 1233 1 52 0 9936K 1452K wait 2 0:00 0.00% sh -ev 36464 0 1 20 0 9656K 1432K ppwait 4 0:00 0.00% cron: running job (cron) 2 0 1 -16 - 0K 8K waitin 5 0:00 0.00% [sctp_iterator] 4 0 1 -16 - 0K 8K psleep 2 0:00 0.00% [vmdaemon] 10 0 1 -16 - 0K 8K audit_ 0 0:00 0.00% [audit] --liOOAslEiF7prFVr-- From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 21:50:01 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB46E106566C for ; Sun, 25 Dec 2011 21:50:01 +0000 (UTC) (envelope-from radiomlodychbandytow@o2.pl) Received: from tur.go2.pl (tur.go2.pl [193.17.41.50]) by mx1.freebsd.org (Postfix) with ESMTP id 7B61E8FC0C for ; Sun, 25 Dec 2011 21:50:01 +0000 (UTC) Received: from moh2-ve2.go2.pl (moh2-ve2.go2.pl [193.17.41.200]) by tur.go2.pl (Postfix) with ESMTP id 4BD2D2308B9 for ; Sun, 25 Dec 2011 22:32:11 +0100 (CET) Received: from moh2-ve2.go2.pl (unknown [10.0.0.200]) by moh2-ve2.go2.pl (Postfix) with ESMTP id 0BDB3B006F3 for ; Sun, 25 Dec 2011 22:31:39 +0100 (CET) Received: from unknown (unknown [10.0.0.142]) by moh2-ve2.go2.pl (Postfix) with SMTP for ; Sun, 25 Dec 2011 22:31:39 +0100 (CET) Received: from host892524678.com-promis.3s.pl [89.25.246.78] by poczta.o2.pl with ESMTP id dGYllC; Sun, 25 Dec 2011 22:31:38 +0100 Message-ID: <4EF79636.7080603@o2.pl> Date: Sun, 25 Dec 2011 22:31:34 +0100 From: =?UTF-8?B?UmFkaW8gbcWCb2R5Y2ggYmFuZHl0w7N3?= User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20111219173426.55711106579E@hub.freebsd.org> In-Reply-To: <20111219173426.55711106579E@hub.freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-O2-Trust: 2, 62 X-O2-SPF: neutral X-Mailman-Approved-At: Sun, 25 Dec 2011 22:20:01 +0000 Cc: daniel@digsys.bg Subject: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux, 6.1 Server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 21:50:01 -0000 Well, the post is OT, but I need some vent. On 2011-12-19 18:34, daniel@digsys.bg wrote: >> For example, few checkboxes with common sysctl tuning would be perfect, >> > even if they would be marked as "Experimental", or not recommended. > By following this, we push FreeBSD into the Linux style of doing things: > someone else decides what is good for you, without having a clue of your > circumstances. It's nice to see sb. with similar thoughts. I too find the freedom to administer your system the way you see fit to be very important. I was very saddened when I discovered that in some ways FreeBSD also forces specific behaviour and in some others builds barriers to prevent people from doing things the authors considered stupid. I don't view it as Linux way vs. FreeBSD way ( though it may be because I don't know either too well ). Rather, I see it as the MacOS way. Education is much better than building barriers and it's never true that a developer can predict all the uses of their code. And different uses call for different configurations, artificially limiting it is a time invested to reduce code's value. -- Twoje radio From owner-freebsd-current@FreeBSD.ORG Sun Dec 25 23:53:26 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04B8F106564A for ; Sun, 25 Dec 2011 23:53:26 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id B0C6D8FC08 for ; Sun, 25 Dec 2011 23:53:25 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1Rexsa-0002nq-GZ>; Mon, 26 Dec 2011 00:53:24 +0100 Received: from e178032097.adsl.alicedsl.de ([85.178.32.97] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1Rexsa-00047o-BS>; Mon, 26 Dec 2011 00:53:24 +0100 Message-ID: <4EF7B76E.5090108@zedat.fu-berlin.de> Date: Mon, 26 Dec 2011 00:53:18 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Current FreeBSD X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7A0D942EA3B47985574B6FD9" X-Originating-IP: 85.178.32.97 Subject: FreeBSD 10.0-CURRENT/amd64: /usr/bin/ld: cannot find -lisc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Dec 2011 23:53:26 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7A0D942EA3B47985574B6FD9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I just run into this couriosity on the most recent build of FreeBSD 10.0-CURRENT/amd64 (CLANG). A buildworld fails with the below shown error. No wonder, I issued prior to this buildworld a "make delete-old-files" and a bunch of files, libisc.so, libisc.a, and buddies showed up - and got deleted. I did this now for several times and obviously, after some mystical install, they appeared again. >>> Removing old files (only deletes safe to delete libs) remove /usr/lib/libisc.a? n remove /usr/lib/libisc.so? n remove /usr/lib/libisc_p.a? n nremove /usr/include/isc/assertions.h? n remove /usr/include/isc/heap.h? n remove /usr/include/isc/list.h? n Below the error. What is up? Got my system somehow wrecked? The same appears on all of our FreeBSD 9.0-PRE/amd64 boxes, clang built, the issue with "make delete-old-files" is not sticky with FreeBSD 10. Regards, Oliver gzip -cn /usr/src/usr.bin/dig/../../contrib/bind9/bin/dig/dig.1 > dig.1.g= z clang -O2 -fno-strict-aliasing -pipe -O3 -fno-strict-aliasing -pipe -march=3Dnative -DVERSION=3D'"9.8.1-P1"' -DHAVE_CONFIG_H -D_REENTRANT -D_THREAD_SAFE -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DNS_LOCALSTATEDIR=3D'"/var"' -DNS_SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"' -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb/rndc.key"' -I/usr/src/usr.bin/dig/../../lib/bind -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 -DDIG_SIGCHASE -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/unix/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/pthreads/include -I/usr/src/usr.bin/dig/../dns -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/dns/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isccfg/include -I/usr/src/usr.bin/dig/../isc -I/usr/src/usr.bin/dig/../../contrib/bind9/bin/dig/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/x86_32/include -std=3Dgnu99 -fstack-protector -Wsystem-headers -Wno-pointer-sign -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch-enum -Wno-empty-body -Wno-parentheses -o dig dig.o dighost.o -lbind9 -ldns -lisccc -lisccfg -lisc -llwres -lcrypto -lpthread clang: warning: argument unused during compilation: '-std=3Dgnu99' /usr/bin/ld: cannot find -lisc clang: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 2 errors *** Error code 2 1 error *** Error code 2 1 error --------------enig7A0D942EA3B47985574B6FD9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO97d0AAoJEOgBcD7A/5N8OioH/29UT/NZE1hFScCmzVMArLpO FqNygbPCx8Kzvg8ppipeZPkge1WJyG1LQn7KzqmLMYV7ajW12h4yIINvcn6JP2z5 rf5uAVhgUGx4v4HkQiYZ43DDWEfGttusHc6/h9sXbLwcvydQ1hOOzkrO0+bWaqEN rzgAODYTIeNV72xjMNSdkr9coOgMO4wAqwUtSmNZHzCPtgN3DLpJyLSTptNxDcGD LCnk3p7CABi4kDgFc+/wIGvqYQsYoLjhbf3R61b7RAArNcLL5E5sU5WKoiZsg0lc Ian7hDQJ54QM/GyXviIK4nlbisUsk9oqMppGT5mN83CnjaIDrY/9z+bnD7F7OVM= =cb2o -----END PGP SIGNATURE----- --------------enig7A0D942EA3B47985574B6FD9-- From owner-freebsd-current@FreeBSD.ORG Mon Dec 26 01:23:15 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2CA61065670 for ; Mon, 26 Dec 2011 01:23:15 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 946E58FC08 for ; Mon, 26 Dec 2011 01:23:15 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:3889:b992:a758:b16e] (unknown [IPv6:2001:7b8:3a7:0:3889:b992:a758:b16e]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id A552A5C59; Mon, 26 Dec 2011 02:23:13 +0100 (CET) Message-ID: <4EF7CC7D.4050902@FreeBSD.org> Date: Mon, 26 Dec 2011 02:23:09 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: "O. Hartmann" References: <4EF7B76E.5090108@zedat.fu-berlin.de> In-Reply-To: <4EF7B76E.5090108@zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Current FreeBSD Subject: Re: FreeBSD 10.0-CURRENT/amd64: /usr/bin/ld: cannot find -lisc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2011 01:23:16 -0000 On 2011-12-26 00:53, O. Hartmann wrote: > I just run into this couriosity on the most recent build of FreeBSD > 10.0-CURRENT/amd64 (CLANG). > > A buildworld fails with the below shown error. No wonder, I issued prior > to this buildworld a "make delete-old-files" and a bunch of files, > libisc.so, libisc.a, and buddies showed up - and got deleted. I did this > now for several times and obviously, after some mystical install, they > appeared again. > >>>> Removing old files (only deletes safe to delete libs) > remove /usr/lib/libisc.a? n > remove /usr/lib/libisc.so? n > remove /usr/lib/libisc_p.a? n > nremove /usr/include/isc/assertions.h? n > remove /usr/include/isc/heap.h? n > remove /usr/include/isc/list.h? n Either you have WITH_BIND_LIBS in your src.conf (which you did not post), or you have had one of the bind ports installed with REPLACE_BASE turned on. Normally the libs and headers are not installed. > Below the error. What is up? Got my system somehow wrecked? ... > clang -O2 -fno-strict-aliasing -pipe -O3 -fno-strict-aliasing -pipe > -march=native -DVERSION='"9.8.1-P1"' -DHAVE_CONFIG_H -D_REENTRANT > -D_THREAD_SAFE -DWANT_IPV6 -DOPENSSL -DUSE_MD5 > -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' > -DNAMED_CONFFILE='"/etc/namedb/named.conf"' > -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' > -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' > -I/usr/src/usr.bin/dig/../../lib/bind -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -DDIG_SIGCHASE > -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/include > -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/unix/include > -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/pthreads/include > -I/usr/src/usr.bin/dig/../dns > -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/dns/include > -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isccfg/include > -I/usr/src/usr.bin/dig/../isc > -I/usr/src/usr.bin/dig/../../contrib/bind9/bin/dig/include > -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/x86_32/include > -std=gnu99 -fstack-protector -Wsystem-headers -Wno-pointer-sign > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-conversion -Wno-switch-enum -Wno-empty-body > -Wno-parentheses -o dig dig.o dighost.o -lbind9 -ldns -lisccc -lisccfg > -lisc -llwres -lcrypto -lpthread > clang: warning: argument unused during compilation: '-std=gnu99' > /usr/bin/ld: cannot find -lisc > clang: error: linker command failed with exit code 1 (use -v to see > invocation) Normally during buildworld the temporary copy of ld in ${WORLDTMP} (usually /usr/obj/usr/src/tmp/usr/bin) is used, *not* /usr/bin/ld. Are you possibly running manual make in /usr/src/usr.sbin/named? Or if not, during which stage of buildworld does this happen? In any case, please post at least your make.conf, src.conf, and upload a full buildworld log (without -j) somewhere. From owner-freebsd-current@FreeBSD.ORG Mon Dec 26 10:10:40 2011 Return-Path: Delivered-To: current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 981ED1065673; Mon, 26 Dec 2011 10:10:40 +0000 (UTC) Date: Mon, 26 Dec 2011 10:10:40 +0000 From: Alexander Best To: current@freebsd.org Message-ID: <20111226101040.GA6361@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline Cc: freebsd-toolchain@freebsd.org, freebsd-arch@freebsd.org Subject: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2011 10:10:40 -0000 --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline hi there, i grep'ed through src/sys and found several places where WERROR= was set in order to get rid of the default -Werror setting. i tried to remove those WERROR= overrides from any Makefile, where doing so did not break tinderbox. in those cases, where it couldn't be completely removed, i added conditions to only set WERROR= for the particular achitecture or compiler, where tinderbox did not suceed without the WERROR=. i talked to dim@ on #freebsd-clang@OFTC and he was against enclosing WERROR= in a architecture or compiler condition. his statement was: " dim : I'm not going to riddle all those makefiles with endless comments, people have to learn to look in the commit history for a file. " however the problem is that most of the time the commit message by the person who added WERROR= to a Makefile doesn't state *why* the person did it and most importantly it doesn't state in *which* case tinderbox failed without the WERROR= (see *). so my suggestion would be that instead of setting WERROR= unconditionally in Makefiles, it should be enclosed in a condition to only set it in a particular case, where tinderbox *will* fail. an example is r228861. here dim@ set WERROR= in sys/modules/nve/Makefile unconditionally. however tinderbox will only fail when A) clang is used as compiler B) when building for i386 these facts aren't clear from the commit message. so i'd suggest (please see the attached patch) to conditionalise such settings. another point i'd like to make is that WERROR= might have been set in a Makefile in the past to unbreak tinderbox for a certain arch that is no longer supported. since most of the time the commit logs simply state something like: *) "...remove -Werror for now to unbreak tinderbox..." nobody will notice that after support for a certain arch was removed, the WERROR= line can be removed from that particular Makefile. that's why i'd like to propose the following patch. i ran a full tinderbox run against r228878 and it suceeded. cheers. alex --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="remove-werror.diff" Index: sys/modules/xfs/Makefile =================================================================== --- sys/modules/xfs/Makefile (revision 228878) +++ sys/modules/xfs/Makefile (working copy) @@ -6,8 +6,6 @@ KMOD= xfs -WERROR= - SRCS = vnode_if.h \ xfs_alloc.c \ xfs_alloc_btree.c \ Index: sys/modules/sound/driver/maestro/Makefile =================================================================== --- sys/modules/sound/driver/maestro/Makefile (revision 228878) +++ sys/modules/sound/driver/maestro/Makefile (working copy) @@ -5,6 +5,5 @@ KMOD= snd_maestro SRCS= device_if.h bus_if.h pci_if.h SRCS+= maestro.c -WERROR= .include Index: sys/modules/aic7xxx/ahd/Makefile =================================================================== --- sys/modules/aic7xxx/ahd/Makefile (revision 228878) +++ sys/modules/aic7xxx/ahd/Makefile (working copy) @@ -4,7 +4,6 @@ .PATH: ${.CURDIR}/../../../dev/aic7xxx KMOD= ahd -WERROR= GENSRCS= aic79xx_seq.h aic79xx_reg.h REG_PRINT_OPT= AHD_REG_PRETTY_PRINT=1 Index: sys/modules/ie/Makefile =================================================================== --- sys/modules/ie/Makefile (revision 228878) +++ sys/modules/ie/Makefile (working copy) @@ -6,6 +6,8 @@ KMOD= if_ie SRCS= if_ie.c if_ie_isa.c \ isa_if.h bus_if.h device_if.h +.if ${MACHINE_CPUARCH} == "i386" WERROR= +.endif .include Index: sys/modules/agp/Makefile =================================================================== --- sys/modules/agp/Makefile (revision 228878) +++ sys/modules/agp/Makefile (working copy) @@ -20,7 +20,6 @@ SRCS+= device_if.h bus_if.h agp_if.h pci_if.h SRCS+= opt_agp.h opt_bus.h MFILES= kern/device_if.m kern/bus_if.m dev/agp/agp_if.m dev/pci/pci_if.m -WERROR= EXPORT_SYMS= agp_find_device \ agp_state \ Index: sys/modules/bios/smapi/Makefile =================================================================== --- sys/modules/bios/smapi/Makefile (revision 228878) +++ sys/modules/bios/smapi/Makefile (working copy) @@ -6,7 +6,6 @@ KMOD= smapi SRCS= smapi.c smapi_bios.S \ bus_if.h device_if.h -WERROR= .if ${CC:T:Mclang} == "clang" # XXX: clang integrated-as doesn't grok 16-bit assembly yet CFLAGS+= ${.IMPSRC:T:Msmapi_bios.S:C/^.+$/-no-integrated-as/} Index: sys/modules/nve/Makefile =================================================================== --- sys/modules/nve/Makefile (revision 228878) +++ sys/modules/nve/Makefile (working copy) @@ -7,7 +7,9 @@ device_if.h bus_if.h pci_if.h miibus_if.h \ os+%DIKED-nve.h OBJS+= nvenetlib.o +.if ${MACHINE_CPUARCH} == "i386" && ${CC:T:Mclang} == "clang" WERROR= +.endif CLEANFILES+= nvenetlib.o os+%DIKED-nve.h nvenetlib.o: ${.CURDIR}/../../contrib/dev/nve/${MACHINE}/${.TARGET}.bz2.uu --W/nzBZO5zC0uMSeA-- From owner-freebsd-current@FreeBSD.ORG Mon Dec 26 11:12:49 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 093A61065670 for ; Mon, 26 Dec 2011 11:12:49 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id A0FA58FC19 for ; Mon, 26 Dec 2011 11:12:48 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1Rf8U3-000422-Hl>; Mon, 26 Dec 2011 12:12:47 +0100 Received: from e178037012.adsl.alicedsl.de ([85.178.37.12] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1Rf8U3-0005wE-Bx>; Mon, 26 Dec 2011 12:12:47 +0100 Message-ID: <4EF856A8.7080707@zedat.fu-berlin.de> Date: Mon, 26 Dec 2011 12:12:40 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Dimitry Andric References: <4EF7B76E.5090108@zedat.fu-berlin.de> <4EF7CC7D.4050902@FreeBSD.org> In-Reply-To: <4EF7CC7D.4050902@FreeBSD.org> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig9D3951A74645AE729270CF81" X-Originating-IP: 85.178.37.12 Cc: Current FreeBSD Subject: Re: FreeBSD 10.0-CURRENT/amd64: /usr/bin/ld: cannot find -lisc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2011 11:12:49 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9D3951A74645AE729270CF81 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 12/26/11 02:23, Dimitry Andric wrote: > On 2011-12-26 00:53, O. Hartmann wrote: >> I just run into this couriosity on the most recent build of FreeBSD >> 10.0-CURRENT/amd64 (CLANG). >> >> A buildworld fails with the below shown error. No wonder, I issued pri= or >> to this buildworld a "make delete-old-files" and a bunch of files, >> libisc.so, libisc.a, and buddies showed up - and got deleted. I did th= is >> now for several times and obviously, after some mystical install, they= >> appeared again. >> >>>>> Removing old files (only deletes safe to delete libs) >> remove /usr/lib/libisc.a? n >> remove /usr/lib/libisc.so? n >> remove /usr/lib/libisc_p.a? n >> nremove /usr/include/isc/assertions.h? n >> remove /usr/include/isc/heap.h? n >> remove /usr/include/isc/list.h? n >=20 > Either you have WITH_BIND_LIBS in your src.conf (which you did not > post), or you have had one of the bind ports installed with REPLACE_BAS= E > turned on. Normally the libs and headers are not installed. >=20 >=20 >> Below the error. What is up? Got my system somehow wrecked? > ... >> clang -O2 -fno-strict-aliasing -pipe -O3 -fno-strict-aliasing -pipe >> -march=3Dnative -DVERSION=3D'"9.8.1-P1"' -DHAVE_CONFIG_H -D_REENTRANT >> -D_THREAD_SAFE -DWANT_IPV6 -DOPENSSL -DUSE_MD5 >> -DNS_LOCALSTATEDIR=3D'"/var"' -DNS_SYSCONFDIR=3D'"/etc/namedb"' >> -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"' >> -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' >> -DRNDC_KEYFILE=3D'"/etc/namedb/rndc.key"' >> -I/usr/src/usr.bin/dig/../../lib/bind -D_LARGEFILE_SOURCE >> -D_FILE_OFFSET_BITS=3D64 -DDIG_SIGCHASE >> -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/include >> -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/unix/include >> -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/pthreads/include >> -I/usr/src/usr.bin/dig/../dns >> -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/dns/include >> -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isccfg/include >> -I/usr/src/usr.bin/dig/../isc >> -I/usr/src/usr.bin/dig/../../contrib/bind9/bin/dig/include >> -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/x86_32/include >> -std=3Dgnu99 -fstack-protector -Wsystem-headers -Wno-pointer-sign >> -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality >> -Wno-unused-function -Wno-conversion -Wno-switch-enum -Wno-empty-body >> -Wno-parentheses -o dig dig.o dighost.o -lbind9 -ldns -lisccc -lisccf= g >> -lisc -llwres -lcrypto -lpthread >> clang: warning: argument unused during compilation: '-std=3Dgnu99' >> /usr/bin/ld: cannot find -lisc >> clang: error: linker command failed with exit code 1 (use -v to see >> invocation) >=20 > Normally during buildworld the temporary copy of ld in ${WORLDTMP} > (usually /usr/obj/usr/src/tmp/usr/bin) is used, *not* /usr/bin/ld. Are= > you possibly running manual make in /usr/src/usr.sbin/named? Or if not= , > during which stage of buildworld does this happen? >=20 > In any case, please post at least your make.conf, src.conf, and upload = a > full buildworld log (without -j) somewhere. My bad, sorry. Yes, I do have WITH_BIND_LIBS on the boxes enabled: (/etc/src.conf): WITH_CLANG=3D YES WITH_CLANG_EXTRAS=3D YES # WITH_BIND_LIBS=3D YES WITH_BIND_SIGCHASE=3D YES WITH_BIND_LARGE_FILE=3D YES # WITH_IDEA=3D YES WITH_HESIOD=3D YES # #WITH_ICONV=3D YES WITH_BSD_GREP=3D YES # WITH_LIBCPLUSPLUS=3D YES # #WITH_OFED=3D YES The errornous output created is from a make build_world, so no manually build in the named-source-folder. A knob REPLACE_BASE is not used either in src.conf, nor in make.conf. Not by intention. Regards, Oliver --------------enig9D3951A74645AE729270CF81 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO+FauAAoJEOgBcD7A/5N8S8IIANaEwxtC9paA6OfbACUsm2za v6lIEewwvq7Bmr9yRKvSSU2scm0zbYg287Rs6XIP2cRnly5MH+SlVVSyigNPD/y5 NdVr2hwSdkY2eREojulaZ7jkIwRM87SW85fjPWpZK8LNYakSmLMu72zTSn9o18/T OMhs5biaULbEhgt0Pu+dj5Ot9ITcZs61XMsdLRje7CshfK0jZ4JZQl4DWgPjsNEy 55Z5Rjwu7Xu9nelZL5wdo8lzYElP5OSMnYl0Jj7O5M47yfk8Bw1Eh8Ur24LZ1kD5 2NENiW25d5paL02Jj3c3kEEzPjsTY4s15wqBBzUBnlnX9JyTuW/OJSYA89bruMA= =M9Rl -----END PGP SIGNATURE----- --------------enig9D3951A74645AE729270CF81-- From owner-freebsd-current@FreeBSD.ORG Mon Dec 26 21:51:21 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 085A4106566B for ; Mon, 26 Dec 2011 21:51:21 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7CD908FC08 for ; Mon, 26 Dec 2011 21:51:20 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:7062:3674:b8da:c969] (unknown [IPv6:2001:7b8:3a7:0:7062:3674:b8da:c969]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 0155D5C37; Mon, 26 Dec 2011 22:51:17 +0100 (CET) Message-ID: <4EF8EC51.2020504@FreeBSD.org> Date: Mon, 26 Dec 2011 22:51:13 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: "O. Hartmann" References: <4EF7B76E.5090108@zedat.fu-berlin.de> <4EF7CC7D.4050902@FreeBSD.org> <4EF856A8.7080707@zedat.fu-berlin.de> In-Reply-To: <4EF856A8.7080707@zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Current FreeBSD Subject: Re: FreeBSD 10.0-CURRENT/amd64: /usr/bin/ld: cannot find -lisc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2011 21:51:21 -0000 On 2011-12-26 12:12, O. Hartmann wrote: ... > Yes, I do have WITH_BIND_LIBS on the boxes enabled: > > (/etc/src.conf): > WITH_CLANG= YES > WITH_CLANG_EXTRAS= YES > # > WITH_BIND_LIBS= YES > WITH_BIND_SIGCHASE= YES > WITH_BIND_LARGE_FILE= YES > # > WITH_IDEA= YES > WITH_HESIOD= YES > # > #WITH_ICONV= YES > WITH_BSD_GREP= YES > # > WITH_LIBCPLUSPLUS= YES > # > #WITH_OFED= YES I have done a buildworld with exactly these settings, and there is no problem linking dig at all. Stage 4.2 (building libraries) builds and installs the libraries and headers into the temproot: -------------------------------------------------------------- >>> stage 4.2: building libraries -------------------------------------------------------------- [...] ===> lib/bind (install) ===> lib/bind/isc (install) sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libisc.a /usr/obj/usr/src/tmp/usr/lib sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libisc.so.83 /usr/obj/usr/src/tmp/usr/lib ln -fs libisc.so.83 /usr/obj/usr/src/tmp/usr/lib/libisc.so [...] And later in stage 4.4 (building everything), those libs get used for linking dig: -------------------------------------------------------------- >>> stage 4.4: building everything -------------------------------------------------------------- [...] ===> usr.bin/dig (all) clang -O2 -pipe -DVERSION='"9.8.1-P1"' -DHAVE_CONFIG_H -D_REENTRANT -D_THREAD_SAFE -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/usr/src/usr.bin/dig/../../lib/bind -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DDIG_SIGCHASE -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/unix/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/pthreads/include -I/usr/src/usr.bin/dig/../dns -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/dns/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isccfg/include -I/usr/src/usr.bin/dig/../isc -I/usr/src/usr.bin/dig/../../contrib/bind9/bin/dig/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/x86_32/include -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -Wno-tautological-c ompare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch-enum -Wno-empty-body -Wno-parentheses -c /usr/src/usr.bin/dig/../../contrib/bind9/bin/dig/dig.c clang -O2 -pipe -DVERSION='"9.8.1-P1"' -DHAVE_CONFIG_H -D_REENTRANT -D_THREAD_SAFE -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/usr/src/usr.bin/dig/../../lib/bind -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DDIG_SIGCHASE -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/unix/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/pthreads/include -I/usr/src/usr.bin/dig/../dns -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/dns/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isccfg/include -I/usr/src/usr.bin/dig/../isc -I/usr/src/usr.bin/dig/../../contrib/bind9/bin/dig/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/x86_32/include -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -Wno-tautological-c ompare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch-enum -Wno-empty-body -Wno-parentheses -c /usr/src/usr.bin/dig/../../contrib/bind9/bin/dig/dighost.c clang -O2 -pipe -DVERSION='"9.8.1-P1"' -DHAVE_CONFIG_H -D_REENTRANT -D_THREAD_SAFE -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/usr/src/usr.bin/dig/../../lib/bind -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DDIG_SIGCHASE -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/unix/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/pthreads/include -I/usr/src/usr.bin/dig/../dns -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/dns/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isccfg/include -I/usr/src/usr.bin/dig/../isc -I/usr/src/usr.bin/dig/../../contrib/bind9/bin/dig/include -I/usr/src/usr.bin/dig/../../contrib/bind9/lib/isc/x86_32/include -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -Wno-tautological-c ompare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch-enum -Wno-empty-body -Wno-parentheses -o dig dig.o dighost.o -lbind9 -ldns -lisccc -lisccfg -lisc -llwres -lcrypto -lpthread clang: warning: argument unused during compilation: '-std=gnu99' gzip -cn /usr/src/usr.bin/dig/../../contrib/bind9/bin/dig/dig.1 > dig.1.gz ===> usr.bin/dirname (all) [...] Can you please upload a full buildworld log somewhere? Preferably without using -j. From owner-freebsd-current@FreeBSD.ORG Mon Dec 26 23:36:18 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id CF9E3106566B for ; Mon, 26 Dec 2011 23:36:18 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 96B6614F9ED for ; Mon, 26 Dec 2011 23:36:18 +0000 (UTC) Message-ID: <4EF904F2.4020109@FreeBSD.org> Date: Mon, 26 Dec 2011 15:36:18 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-current X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2011 23:36:18 -0000 The story so far ... sysinstall was removed from HEAD in October. I (and others) objected on the basis that at this time there is no replacement for the post-install configuration role that sysinstall played. More sysinstall components were then removed. Then the old version of libdialog (which sysinstall used) was removed. Thus at this point it's not possible to easily restore sysinstall. So my question is, how much do you care? Is lack of that functionality in HEAD something that we care about? Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Mon Dec 26 23:54:01 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54B6A106564A for ; Mon, 26 Dec 2011 23:54:01 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1DE5B8FC12 for ; Mon, 26 Dec 2011 23:54:00 +0000 (UTC) Received: by iadj38 with SMTP id j38so23383124iad.13 for ; Mon, 26 Dec 2011 15:54:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=TbgL6SrywybziR3J7KX2dB21giNxSjtw9glyL3bSqo8=; b=Zs+la4DpUIw4Gt25YYJ1BY+R6OVmOYlTzDd7kFwtU5/0W9DRaDF74dA9n5liI8W1Hb bPIL99gIkpvuPZiTEBEuXrlj8j+BwC01DzBMM6qLyu7zkDWvk38Bu7d3LXA3IfhQsOkO aCN1jOoU8ce6BxBhJ9TPmpbA1+mow6cxCDj4k= MIME-Version: 1.0 Received: by 10.42.175.134 with SMTP id ba6mr26262402icb.23.1324943640496; Mon, 26 Dec 2011 15:54:00 -0800 (PST) Received: by 10.231.20.12 with HTTP; Mon, 26 Dec 2011 15:54:00 -0800 (PST) In-Reply-To: References: Date: Tue, 27 Dec 2011 01:54:00 +0200 Message-ID: From: George Kontostanos To: Garrett Cooper , FreeBSD-Current Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: 9-RC3 & Super Micro IPMI disconnects X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2011 23:54:01 -0000 On Sat, Dec 24, 2011 at 8:55 PM, Garrett Cooper wrote: > On Sat, Dec 24, 2011 at 6:08 AM, George Kontostanos > wrote: >> Hi everyone, >> >> I started running FreeBSD9-RC1 on this server. Yesterday, RC3, I >> noticed that I could not get IPMI console to apply the necessary >> security patches. A reset in IPMI fixed the problem temporarily. I >> keep getting those messages: > > Have you updated your firmware to the latest version? What motherboard is this? > -Garrett I apologize for the delayed response. I had no knowledge of the exact board. The board is Supermicro X9SCL-F running the latest Firmware Revision: 01.27. -- George Kontostanos From owner-freebsd-current@FreeBSD.ORG Mon Dec 26 23:01:34 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E997C106564A for ; Mon, 26 Dec 2011 23:01:34 +0000 (UTC) (envelope-from lidl@hydra.pix.net) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::3c]) by mx1.freebsd.org (Postfix) with ESMTP id A79B38FC08 for ; Mon, 26 Dec 2011 23:01:34 +0000 (UTC) Received: from hydra.pix.net (localhost [127.0.0.1]) by hydra.pix.net (8.14.4/8.14.4) with ESMTP id pBQN1Xf7095005 for ; Mon, 26 Dec 2011 18:01:33 -0500 (EST) (envelope-from lidl@hydra.pix.net) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.97.1 at mail.pix.net Received: (from lidl@localhost) by hydra.pix.net (8.14.4/8.14.4/Submit) id pBQN1Xwu095004 for freebsd-current@freebsd.org; Mon, 26 Dec 2011 18:01:33 -0500 (EST) (envelope-from lidl) Date: Mon, 26 Dec 2011 18:01:33 -0500 From: Kurt Lidl To: freebsd-current@freebsd.org Message-ID: <20111226230132.GA94850@pix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Tue, 27 Dec 2011 02:33:46 +0000 Subject: sparc64 9.0-RC3 install failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2011 23:01:35 -0000 I downloaded the 9.0-RC3 disc1 image for sparc64 and attempted to install it onto a Netra-T1 105 that is currently running FreeBSD 8.2-RELEASE. (1024MB memory, 2x36GB scsi drives, quad-port HME card in the PCI slot) It failed to install, but not before destroying my partitions. .............Error............... . The checksum for base.txz . . does not match. It may have . . become corrupted, and should . . be redownloaded. . ................................. . < OK > . ................................. After I exited from the installer, I manually ran sha256 on all the .txz files in /usr/freebsd-dist: # sha256 *txz SHA256 (base.txz) = 23c116d439368f612d7a774435002075e9f11cfe7443190b22868b485a53ffff SHA256 (doc.txz) = ba5887aac341f5c21293d76df5debfaba812adcd9b65153e977b5db4a347afdc SHA256 (games.txz) = 0869a7fe76440247e12b915aa7811a7b04d5fa9c8d6d98f3c8defb4c78f390b2 SHA256 (kernel.txz) = 5e9940390fa0ac93806ede8c955e50a5a46e1e8d631509de67f0635999ea9a57 SHA256 (ports.txz) = cd3f2365755bb6c0fe0e8fbec331cae2fd163112ab7fec35aed7ae837d761593 SHA256 (src.txz) = a4d515b25e3938da6c0fd1cf79c2c7057f77df3a8141d599d28373e838923d35 Sure enough, those checksums don't match the contents of the MANIFEST file. I then took the CD-ROM that I burned, popped it into a amd64 machine running FreeBSD 8.2-RELEASE, and after mounting the CD-ROM, ran sha256 on the same files. This time, all the checksums for the .txz files match the contents of the MANIFEST file. So, the media that I burned is definately good when I read it on the amd64 machine. Has anyone successfully installed the sparc64-RC3 bits from the disc1 ISO onto a sparc64 machine? -Kurt From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 02:41:08 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id EBC95106566B; Tue, 27 Dec 2011 02:41:08 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 95B3914F4EB; Tue, 27 Dec 2011 02:41:08 +0000 (UTC) Message-ID: <4EF93044.80408@FreeBSD.org> Date: Mon, 26 Dec 2011 18:41:08 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Justin Hibbits References: <4EF904F2.4020109@FreeBSD.org> <69C4832E-BECB-4DD3-B1CF-56A70BBB3A98@freebsd.org> In-Reply-To: <69C4832E-BECB-4DD3-B1CF-56A70BBB3A98@freebsd.org> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 02:41:09 -0000 On 12/26/2011 18:23, Justin Hibbits wrote: > Hi Doug, > > I do agree that it would be nice to have a post-install configuration > utility. However, I think it might be better served with a separate > tool, rather than a swiss army knife that sysinstall was. If someone is > willing to do the work, I think a suitable replacement could be written > in sh+dialog, along the lines of bsdinstall. I don't think anyone would disagree that it would be nice to have a new tool, but that's not the question. > That being said, I remove myself from the nomination pool. ... and this is why "would we like to have a new tool?" is not the question. :) Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 02:51:58 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5094D106566C for ; Tue, 27 Dec 2011 02:51:58 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 128588FC0C for ; Tue, 27 Dec 2011 02:51:57 +0000 (UTC) Received: by iadj38 with SMTP id j38so23657035iad.13 for ; Mon, 26 Dec 2011 18:51:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; bh=WqD+Q7pdWEKL8C9sSoaDuWGkrPntUWDvsqqoriER4Io=; b=UPBDSoZDAFUHtuwvzbEyzXV7HUClyAo2ol4a6OwMo60p2eyGjOKXYvHbF1zlOuIqAX 6UQ4P/tiYJwwxl8YMMGRKvz/jRbKTR+WETqu/fF6xrozDX3puFbp3qZ2CYeomwotimvs Bv0/kjxpc4Z2L8eeLPpTQDJ8EzA/7l0wvI+/M= Received: by 10.42.156.195 with SMTP id a3mr26508725icx.25.1324952703111; Mon, 26 Dec 2011 18:25:03 -0800 (PST) Received: from triad.knownspace (216-15-41-8.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com. [216.15.41.8]) by mx.google.com with ESMTPS id gh9sm63431439igb.3.2011.12.26.18.25.01 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 26 Dec 2011 18:25:02 -0800 (PST) Sender: Justin Hibbits Message-Id: <69C4832E-BECB-4DD3-B1CF-56A70BBB3A98@freebsd.org> From: Justin Hibbits To: Doug Barton In-Reply-To: <4EF904F2.4020109@FreeBSD.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 26 Dec 2011 21:23:42 -0500 References: <4EF904F2.4020109@FreeBSD.org> X-Mailer: Apple Mail (2.936) Cc: freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 02:51:58 -0000 On Dec 26, 2011, at 6:36 PM, Doug Barton wrote: > The story so far ... > > sysinstall was removed from HEAD in October. I (and others) objected > on > the basis that at this time there is no replacement for the post- > install > configuration role that sysinstall played. More sysinstall components > were then removed. Then the old version of libdialog (which sysinstall > used) was removed. Thus at this point it's not possible to easily > restore sysinstall. > > So my question is, how much do you care? Is lack of that functionality > in HEAD something that we care about? > > > Doug Hi Doug, I do agree that it would be nice to have a post-install configuration utility. However, I think it might be better served with a separate tool, rather than a swiss army knife that sysinstall was. If someone is willing to do the work, I think a suitable replacement could be written in sh+dialog, along the lines of bsdinstall. That being said, I remove myself from the nomination pool. - Justin From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 03:42:37 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 670A7106564A for ; Tue, 27 Dec 2011 03:42:37 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 215E08FC08 for ; Tue, 27 Dec 2011 03:42:36 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EACk++U6DaFvO/2dsb2JhbABDhQ+kFoQoghxLQAINGQJyFJ1kjgKRGIEviUqBFgSIN4xLklI X-IronPort-AV: E=Sophos;i="4.71,413,1320642000"; d="scan'208";a="149973152" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 26 Dec 2011 22:42:36 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 28F25B3EA4 for ; Mon, 26 Dec 2011 22:42:36 -0500 (EST) Date: Mon, 26 Dec 2011 22:42:36 -0500 (EST) From: Rick Macklem To: freebsd-current@freebsd.org Message-ID: <2003190153.640689.1324957356113.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Subject: license question w.r.t. NFSv4.1 Layout drivers - calling all amateur lawyers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 03:42:37 -0000 First off, I had no idea which mailing list would be appropriate for this, so apologies in advance if I chose the wrong one. For NFSv4.1 pNFS, there are layout drivers in Linux that I would like to reuse for the FreeBSD client. (Re-writing these drivers from scratch would be a lot of work and difficult to maintain. The Linux drivers are being actively developed with the assistance of server vendors.) Two of these drivers carry a University of Michigan copyright notice which looks pretty liberal to me. (Rather similar to MIT's copyright.) I realize it would have to be approved by core@, but I think it could be. (The 3rd is GPLv2'd, but that one doesn't concern me at this time. I believe that Panasas might be able to release the code for this one under a different license, but haven't explored this as of yet.) However, there is a catch... After the copyright notice on the .c files, but not the .h files, there is also this: MODULE_LICENSE("GPL"); and in linux/module.h, there is the following for the above: /* * The following license idents are currently accepted as indicating free * software modules * * "GPL" [GNU Public License v2 or later] * "GPL v2" [GNU Public License v2] * "GPL and additional rights" [GNU Public License v2 rights and more] * "Dual BSD/GPL" [GNU Public License v2 * or BSD license choice] * "Dual MIT/GPL" [GNU Public License v2 * or MIT license choice] * "Dual MPL/GPL" [GNU Public License v2 * or Mozilla license choice] * * The following other idents are available * * "Proprietary" [Non free products] * * There are dual licensed components, but when running with Linux it is the * GPL that is relevant so this is a non issue. Similarly LGPL linked with GPL * is a GPL combined work. * * This exists for several reasons * 1. So modinfo can show license info for users wanting to vet their setup * is free * 2. So the community can ignore bug reports including proprietary modules * 3. So vendors can do likewise based on their own policies */ #define MODULE_LICENSE(_license) MODULE_INFO(license, _license) Now, from what little I know, this does not imply that the .c file is GPL'd, since it doesn't have any GPL copyright notice in the file, nor does it #include one via MODULE_LICENSE(). Does anyone happen to know if I am correct or how to confirm this? Thanks in advance for any help with this, rick ps: Here's what's on the .c file, in case you're interested. The .h files just have what is in the comment. /* * Module for the pnfs nfs4 file layout driver. * Defines all I/O and Policy interface operations, plus code * to register itself with the pNFS client. * * Copyright (c) 2002 * The Regents of the University of Michigan * All Rights Reserved * * Dean Hildebrand * * Permission is granted to use, copy, create derivative works, and * redistribute this software and such derivative works for any purpose, * so long as the name of the University of Michigan is not used in * any advertising or publicity pertaining to the use or distribution * of this software without specific, written prior authorization. If * the above copyright notice or any other identification of the * University of Michigan is included in any copy of any portion of * this software, then the disclaimer below must also be included. * * This software is provided as is, without representation or warranty * of any kind either express or implied, including without limitation * the implied warranties of merchantability, fitness for a particular * purpose, or noninfringement. The Regents of the University of * Michigan shall not be liable for any damages, including special, * indirect, incidental, or consequential damages, with respect to any * claim arising out of or in connection with the use of the software, * even if it has been or is hereafter advised of the possibility of * such damages. */ #include #include #include #include "internal.h" #include "nfs4filelayout.h" #define NFSDBG_FACILITY NFSDBG_PNFS_LD MODULE_LICENSE("GPL"); MODULE_AUTHOR("Dean Hildebrand "); MODULE_DESCRIPTION("The NFSv4 file layout driver"); From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 03:55:51 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D51451065670 for ; Tue, 27 Dec 2011 03:55:51 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 93A7D8FC17 for ; Tue, 27 Dec 2011 03:55:51 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap0EALVA+U6DaFvO/2dsb2JhbABDhQ+oPoFyAQYjVhsaAg0ZAlkzq2KRGYEvh0aCBIEWBIg3jEuSUg X-IronPort-AV: E=Sophos;i="4.71,413,1320642000"; d="scan'208";a="149973613" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 26 Dec 2011 22:55:51 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id E6A7DB3FCB; Mon, 26 Dec 2011 22:55:50 -0500 (EST) Date: Mon, 26 Dec 2011 22:55:50 -0500 (EST) From: Rick Macklem To: pyunyh@gmail.com Message-ID: <1480355747.640765.1324958150892.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20101108014022.GG1279@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-current@freebsd.org Subject: Re: re(4) driver dropping packets when reading NFS files X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 03:55:51 -0000 Way back in Nov 2010, this thread was related to a problem I had, where an re(4) { 810xE PCIe 10/100baseTX, according to the driver } interface dropped received packets, resulting in a significant impact of NFS performance. Well, it turns out that a recent (post r224506) commit seems to have fixed the problem. It hasn't dropped any packets since I upgraded to a kernel with a r228281 version of if_re.c. So, good news. Thanks to those maintaining this driver, rick ps: If you have a need to know which commit fixed this, I can probably test variants to find out. Otherwise, I'm just happy that it's fixed.:-) From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 05:00:23 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2131C106566B for ; Tue, 27 Dec 2011 05:00:23 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id CCC2B8FC16 for ; Tue, 27 Dec 2011 05:00:22 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so10507767obb.13 for ; Mon, 26 Dec 2011 21:00:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UUN35XnGgSKtnAiIfVCoQ0cKZ7SZdhEfHHdhzk2HlBw=; b=ubihIkhG7pDSWZLhKYtKL8XK0vB41zKTyANS11tlIv/lJBByW/jfm5D5k2jh2skQVe s/bK0M5ugkmnF2I4oLENgJ/K9auWEuiDfad75c5f937spxW+B3zfa0VC+tPKsVdRD9cp WivzxdrXjsgFYcf9kmLTa2GDhsvqjI5lhBk5Q= MIME-Version: 1.0 Received: by 10.182.227.7 with SMTP id rw7mr24054053obc.70.1324960147305; Mon, 26 Dec 2011 20:29:07 -0800 (PST) Received: by 10.182.67.163 with HTTP; Mon, 26 Dec 2011 20:29:07 -0800 (PST) In-Reply-To: <4EF904F2.4020109@FreeBSD.org> References: <4EF904F2.4020109@FreeBSD.org> Date: Mon, 26 Dec 2011 20:29:07 -0800 Message-ID: From: Xin LI To: Doug Barton Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 05:00:23 -0000 On Mon, Dec 26, 2011 at 3:36 PM, Doug Barton wrote: > The story so far ... > > sysinstall was removed from HEAD in October. I (and others) objected on > the basis that at this time there is no replacement for the post-install > configuration role that sysinstall played. More sysinstall components > were then removed. Then the old version of libdialog (which sysinstall > used) was removed. Thus at this point it's not possible to easily > restore sysinstall. > > So my question is, how much do you care? Is lack of that functionality > in HEAD something that we care about? Perhaps make it a port instead? I personally don't use sysinstall for post-install tasks at all, but it won't hurt to have such functionality. Cheers, -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 05:05:58 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 7F524106564A for ; Tue, 27 Dec 2011 05:05:58 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id AFFF414F864; Tue, 27 Dec 2011 05:05:57 +0000 (UTC) Message-ID: <4EF95235.7020502@FreeBSD.org> Date: Mon, 26 Dec 2011 21:05:57 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Xin LI References: <4EF904F2.4020109@FreeBSD.org> In-Reply-To: X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 05:05:58 -0000 On 12/26/2011 20:29, Xin LI wrote: > On Mon, Dec 26, 2011 at 3:36 PM, Doug Barton wrote: >> The story so far ... >> >> sysinstall was removed from HEAD in October. I (and others) objected on >> the basis that at this time there is no replacement for the post-install >> configuration role that sysinstall played. More sysinstall components >> were then removed. Then the old version of libdialog (which sysinstall >> used) was removed. Thus at this point it's not possible to easily >> restore sysinstall. >> >> So my question is, how much do you care? Is lack of that functionality >> in HEAD something that we care about? > > Perhaps make it a port instead? I personally don't use sysinstall for > post-install tasks at all, but it won't hurt to have such > functionality. You're not the first person to suggest that, but I don't see how it's actually responsive to the problem. This issue only affects HEAD, so a port would not be generally useful. It would also be an enormous amount of work to make it into a port. It would be much easier to revert the necessary changes to bring back the old libdialog and sysinstall itself. Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 05:13:18 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D685E106566C; Tue, 27 Dec 2011 05:13:18 +0000 (UTC) (envelope-from rcm@fuzzwad.org) Received: from mail.volente.us (unknown [IPv6:2001:470:7:d47::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9A9AD8FC0A; Tue, 27 Dec 2011 05:13:18 +0000 (UTC) Received: from zombie.fuzzwad.net (localhost [127.0.0.1]) by mail.volente.us (8.14.4/8.14.4) with ESMTP id pBR5DHUT097592; Mon, 26 Dec 2011 23:13:17 -0600 (CST) (envelope-from rcm@fuzzwad.org) Message-ID: <4EF953ED.9060905@fuzzwad.org> Date: Mon, 26 Dec 2011 23:13:17 -0600 From: Ron McDowell User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Doug Barton References: <4EF904F2.4020109@FreeBSD.org> In-Reply-To: <4EF904F2.4020109@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 05:13:18 -0000 Doug Barton wrote: > The story so far ... > > sysinstall was removed from HEAD in October. I (and others) objected on > the basis that at this time there is no replacement for the post-install > configuration role that sysinstall played. More sysinstall components > were then removed. Then the old version of libdialog (which sysinstall > used) was removed. Thus at this point it's not possible to easily > restore sysinstall. > > So my question is, how much do you care? Is lack of that functionality > in HEAD something that we care about? > > > Doug > We have around 90 web servers running 8.2p5 right now [and yes, I did update the lot on Christmas Eve but that's a different story] and they will not be upgraded to 9.0 until/unless the post-install functionality that was lost by the removal of sysinstall is reintegrated in some way. I also complained about it and was told in effect, "too bad." Everyone who commented said sysinstall caused more problems than it solved, although I've been using it for any system changes I needed that it was capable of doing for as long back as I can remember, and my first FreeBSD box was v2.2. I think removing any functionality that was in a previous release without providing an equal-or-better alternative is a bad idea, and that needs to be considered more carefully in the future. So this is not just a +1 vote, it's a +90. -- Ron McDowell San Antonio TX From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 06:25:36 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DE70106568D; Tue, 27 Dec 2011 06:25:36 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id EA4628FC0C; Tue, 27 Dec 2011 06:25:35 +0000 (UTC) Received: by ggnp1 with SMTP id p1so11110801ggn.13 for ; Mon, 26 Dec 2011 22:25:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=JxdYaKWUIsSCDeRu94yK2IIQeO0ho+gzQUPEBaDC5k0=; b=TXAf2OYbZRRW+vrKRD3sPuj1GqLYRWMWxpZZHQgOqtpuGAnMmXgC8VjRI+HPzfl2E1 3tMqq+DmrrO9oQtftIABi9M6TZDmiVLxeuN9nbK1QKdfufAL0m2D14SifOU9VM56PdBT 2jvlI2JDCEiPTE+eIjFcUV9IlR5yijLaPvqrc= Received: by 10.101.125.17 with SMTP id c17mr7539544ann.42.1324967135157; Mon, 26 Dec 2011 22:25:35 -0800 (PST) Received: from [192.168.2.5] (dpc691944246.direcpc.com. [69.19.44.246]) by mx.google.com with ESMTPS id e66sm37296790yhk.6.2011.12.26.22.25.26 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 26 Dec 2011 22:25:34 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=windows-1252 From: Garrett Cooper In-Reply-To: <4EF953ED.9060905@fuzzwad.org> Date: Mon, 26 Dec 2011 22:25:13 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> To: Ron McDowell X-Mailer: Apple Mail (2.1251.1) Cc: Doug Barton , freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 06:25:36 -0000 On Dec 26, 2011, at 9:13 PM, Ron McDowell wrote: > Doug Barton wrote: >> The story so far ... >>=20 >> sysinstall was removed from HEAD in October. I (and others) objected = on >> the basis that at this time there is no replacement for the = post-install >> configuration role that sysinstall played. More sysinstall components >> were then removed. Then the old version of libdialog (which = sysinstall >> used) was removed. Thus at this point it's not possible to easily >> restore sysinstall. >>=20 >> So my question is, how much do you care? Is lack of that = functionality >> in HEAD something that we care about?=20 >=20 > We have around 90 web servers running 8.2p5 right now [and yes, I did = update the lot on Christmas Eve but that's a different story] and they = will not be upgraded to 9.0 until/unless the post-install functionality = that was lost by the removal of sysinstall is reintegrated in some way. = I also complained about it and was told in effect, "too bad." Everyone = who commented said sysinstall caused more problems than it solved, = although I've been using it for any system changes I needed that it was = capable of doing for as long back as I can remember, and my first = FreeBSD box was v2.2. >=20 > I think removing any functionality that was in a previous release = without providing an equal-or-better alternative is a bad idea, and that = needs to be considered more carefully in the future. >=20 > So this is not just a +1 vote, it's a +90. I hate to steal Devin's thunder, but=85 http://lists.freebsd.org/pipermail/freebsd-rc/2010-October/002077.html It's been around for a while and does many of the things needed by the = sysinstall 'post-install' replacement (minus having a registry of = commands vs services to pick from to configure with a slightly more = humanized interface *and it's written almost purely with shell logic and = built-ins, plus is widely tested and adopted in other BSD distros!*. Most of the other stuff is trivial (configuring an interface, a package = installer/configuration tool, etc), and if someone actually said "hey -- = I'll help you get it done!" then yes I'd do it, maintain it, and cherish = it. Offer is on the table for a committer who really wants this task = done. Thanks, -Garrett= From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 10:42:03 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B82E106564A; Tue, 27 Dec 2011 10:42:03 +0000 (UTC) (envelope-from philip@paeps.cx) Received: from rincewind.paeps.cx (rincewind.paeps.cx [IPv6:2002:596a:f092::149]) by mx1.freebsd.org (Postfix) with ESMTP id F00338FC20; Tue, 27 Dec 2011 10:42:02 +0000 (UTC) Received: from twoflower.paeps.cx (unknown [176.99.70.219]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "twoflower.paeps.cx", Issuer "CAcert Class 3 Root" (verified OK)) by rincewind.paeps.cx (Postfix) with ESMTPS id 0CE3BD74495; Tue, 27 Dec 2011 11:41:53 +0100 (CET) Received: by twoflower.paeps.cx (Postfix, from userid 1001) id F13EB3E2106; Tue, 27 Dec 2011 02:04:49 +0100 (CET) Date: Tue, 27 Dec 2011 02:04:49 +0100 From: Philip Paeps To: freebsd-current@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Message-ID: <20111227010449.GA6244@twoflower.paeps.cx> Mail-Followup-To: freebsd-current@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org References: <20111226101040.GA6361@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20111226101040.GA6361@freebsd.org> X-PGP-Fingerprint: 356B AE02 4763 F739 2FA2 E438 2649 E628 C5D3 4D05 X-Date: Today is Sweetmorn, the 69th day of The Aftermath in the YOLD 3177 X-Phase-of-Moon: The Moon is Waxing Crescent (7% of Full) X-Philip-Conspiracy: There is no conspiracy User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 10:42:03 -0000 On 2011-12-26 10:10:40 (+0000), Alexander Best wrote: > i grep'ed through src/sys and found several places where WERROR= was set in > order to get rid of the default -Werror setting. i tried to remove those > WERROR= overrides from any Makefile, where doing so did not break tinderbox. > > in those cases, where it couldn't be completely removed, i added conditions to > only set WERROR= for the particular achitecture or compiler, where tinderbox > did not suceed without the WERROR=. Wouldn't it be better to set WARNS=x rather than WERROR=? WERROR= says "this code has bugs, it breaks tinderbox" whereas WARNS=x says "this code has the following kind of bugs which break tinderbox". Possibly wrapped in an architecture-test where appropriate. - Philip -- Philip Paeps Senior Reality Engineer Ministry of Information From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 10:42:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B82E106564A; Tue, 27 Dec 2011 10:42:03 +0000 (UTC) (envelope-from philip@paeps.cx) Received: from rincewind.paeps.cx (rincewind.paeps.cx [IPv6:2002:596a:f092::149]) by mx1.freebsd.org (Postfix) with ESMTP id F00338FC20; Tue, 27 Dec 2011 10:42:02 +0000 (UTC) Received: from twoflower.paeps.cx (unknown [176.99.70.219]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "twoflower.paeps.cx", Issuer "CAcert Class 3 Root" (verified OK)) by rincewind.paeps.cx (Postfix) with ESMTPS id 0CE3BD74495; Tue, 27 Dec 2011 11:41:53 +0100 (CET) Received: by twoflower.paeps.cx (Postfix, from userid 1001) id F13EB3E2106; Tue, 27 Dec 2011 02:04:49 +0100 (CET) Date: Tue, 27 Dec 2011 02:04:49 +0100 From: Philip Paeps To: freebsd-current@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Message-ID: <20111227010449.GA6244@twoflower.paeps.cx> Mail-Followup-To: freebsd-current@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org References: <20111226101040.GA6361@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20111226101040.GA6361@freebsd.org> X-PGP-Fingerprint: 356B AE02 4763 F739 2FA2 E438 2649 E628 C5D3 4D05 X-Date: Today is Sweetmorn, the 69th day of The Aftermath in the YOLD 3177 X-Phase-of-Moon: The Moon is Waxing Crescent (7% of Full) X-Philip-Conspiracy: There is no conspiracy User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 10:42:03 -0000 On 2011-12-26 10:10:40 (+0000), Alexander Best wrote: > i grep'ed through src/sys and found several places where WERROR= was set in > order to get rid of the default -Werror setting. i tried to remove those > WERROR= overrides from any Makefile, where doing so did not break tinderbox. > > in those cases, where it couldn't be completely removed, i added conditions to > only set WERROR= for the particular achitecture or compiler, where tinderbox > did not suceed without the WERROR=. Wouldn't it be better to set WARNS=x rather than WERROR=? WERROR= says "this code has bugs, it breaks tinderbox" whereas WARNS=x says "this code has the following kind of bugs which break tinderbox". Possibly wrapped in an architecture-test where appropriate. - Philip -- Philip Paeps Senior Reality Engineer Ministry of Information From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 11:27:43 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 2183D1065678; Tue, 27 Dec 2011 11:27:43 +0000 (UTC) Date: Tue, 27 Dec 2011 11:27:43 +0000 From: Alexander Best To: freebsd-current@freebsd.org, freebsd-arch@freebsd.org Message-ID: <20111227112743.GA154@freebsd.org> References: <20111226101040.GA6361@freebsd.org> <20111227010449.GA6244@twoflower.paeps.cx> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <20111227010449.GA6244@twoflower.paeps.cx> Cc: Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 11:27:43 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue Dec 27 11, Philip Paeps wrote: > On 2011-12-26 10:10:40 (+0000), Alexander Best wrote: > > i grep'ed through src/sys and found several places where WERROR= was set in > > order to get rid of the default -Werror setting. i tried to remove those > > WERROR= overrides from any Makefile, where doing so did not break tinderbox. > > > > in those cases, where it couldn't be completely removed, i added conditions to > > only set WERROR= for the particular achitecture or compiler, where tinderbox > > did not suceed without the WERROR=. > > Wouldn't it be better to set WARNS=x rather than WERROR=? WERROR= says "this > code has bugs, it breaks tinderbox" whereas WARNS=x says "this code has the > following kind of bugs which break tinderbox". > > Possibly wrapped in an architecture-test where appropriate. well there are a few issues here: 1) Jan Beich informed me via a private email that enclosing WERROR in arch specific conditions is a bad idea. if the code gets ported to a new architecture WERROR doesn't get set and so for every new architecture one has to evaluate again, whether WERROR needs to be set or not. so i'm inclined to agree with dim@ that we should not add architecture specific conditions -- however i think adding compiler specific conditions is a good idea. 2) the problem with settings WARNS= or specific -Wno-X or -Wno-error=X is that expecially GCC doesn't have specific -WX flags for certain warnings. some warnings are implied by -Wall and cannot be turned off seperately. so in order to get rid of these warnings (which are being handled as errors), we would need to disable -Wall. and i think setting WERROR= in order to handle all warnings for specific code as warnings rather than as errors is the better solution. i've reworked the patch to only remove WERROR=, where it is not needed anymore for any supported arch, or where it can be wrapped in a compiler condition. cheers. alex > > - Philip > > -- > Philip Paeps > Senior Reality Engineer > Ministry of Information --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="remove-werror.diff2" Index: sys/modules/xfs/Makefile =================================================================== --- sys/modules/xfs/Makefile (revision 228911) +++ sys/modules/xfs/Makefile (working copy) @@ -6,8 +6,6 @@ KMOD= xfs -WERROR= - SRCS = vnode_if.h \ xfs_alloc.c \ xfs_alloc_btree.c \ Index: sys/modules/sound/driver/maestro/Makefile =================================================================== --- sys/modules/sound/driver/maestro/Makefile (revision 228911) +++ sys/modules/sound/driver/maestro/Makefile (working copy) @@ -5,6 +5,5 @@ KMOD= snd_maestro SRCS= device_if.h bus_if.h pci_if.h SRCS+= maestro.c -WERROR= .include Index: sys/modules/aic7xxx/ahd/Makefile =================================================================== --- sys/modules/aic7xxx/ahd/Makefile (revision 228911) +++ sys/modules/aic7xxx/ahd/Makefile (working copy) @@ -4,7 +4,6 @@ .PATH: ${.CURDIR}/../../../dev/aic7xxx KMOD= ahd -WERROR= GENSRCS= aic79xx_seq.h aic79xx_reg.h REG_PRINT_OPT= AHD_REG_PRETTY_PRINT=1 Index: sys/modules/agp/Makefile =================================================================== --- sys/modules/agp/Makefile (revision 228911) +++ sys/modules/agp/Makefile (working copy) @@ -20,7 +20,6 @@ SRCS+= device_if.h bus_if.h agp_if.h pci_if.h SRCS+= opt_agp.h opt_bus.h MFILES= kern/device_if.m kern/bus_if.m dev/agp/agp_if.m dev/pci/pci_if.m -WERROR= EXPORT_SYMS= agp_find_device \ agp_state \ Index: sys/modules/bios/smapi/Makefile =================================================================== --- sys/modules/bios/smapi/Makefile (revision 228911) +++ sys/modules/bios/smapi/Makefile (working copy) @@ -6,7 +6,6 @@ KMOD= smapi SRCS= smapi.c smapi_bios.S \ bus_if.h device_if.h -WERROR= .if ${CC:T:Mclang} == "clang" # XXX: clang integrated-as doesn't grok 16-bit assembly yet CFLAGS+= ${.IMPSRC:T:Msmapi_bios.S:C/^.+$/-no-integrated-as/} Index: sys/modules/nve/Makefile =================================================================== --- sys/modules/nve/Makefile (revision 228911) +++ sys/modules/nve/Makefile (working copy) @@ -7,7 +7,9 @@ device_if.h bus_if.h pci_if.h miibus_if.h \ os+%DIKED-nve.h OBJS+= nvenetlib.o +.if ${CC:T:Mclang} == "clang" WERROR= +.endif CLEANFILES+= nvenetlib.o os+%DIKED-nve.h nvenetlib.o: ${.CURDIR}/../../contrib/dev/nve/${MACHINE}/${.TARGET}.bz2.uu --Dxnq1zWXvFF0Q93v-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 11:47:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47E9C106564A; Tue, 27 Dec 2011 11:47:32 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id E07F48FC13; Tue, 27 Dec 2011 11:47:31 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 658C17300A; Tue, 27 Dec 2011 13:04:09 +0100 (CET) Date: Tue, 27 Dec 2011 13:04:09 +0100 From: Luigi Rizzo To: Alexander Best Message-ID: <20111227120409.GA64631@onelab2.iet.unipi.it> References: <20111226101040.GA6361@freebsd.org> <20111227010449.GA6244@twoflower.paeps.cx> <20111227112743.GA154@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111227112743.GA154@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 11:47:32 -0000 On Tue, Dec 27, 2011 at 11:27:43AM +0000, Alexander Best wrote: > On Tue Dec 27 11, Philip Paeps wrote: > > On 2011-12-26 10:10:40 (+0000), Alexander Best wrote: > > > i grep'ed through src/sys and found several places where WERROR= was set in > > > order to get rid of the default -Werror setting. i tried to remove those > > > WERROR= overrides from any Makefile, where doing so did not break tinderbox. > > > > > > in those cases, where it couldn't be completely removed, i added conditions to > > > only set WERROR= for the particular achitecture or compiler, where tinderbox > > > did not suceed without the WERROR=. > > > > Wouldn't it be better to set WARNS=x rather than WERROR=? WERROR= says "this > > code has bugs, it breaks tinderbox" whereas WARNS=x says "this code has the > > following kind of bugs which break tinderbox". > > > > Possibly wrapped in an architecture-test where appropriate. > > well there are a few issues here: > > 1) Jan Beich informed me via a private email that enclosing WERROR in arch > specific conditions is a bad idea. if the code gets ported to a new > architecture WERROR doesn't get set and so for every new architecture one > has to evaluate again, whether WERROR needs to be set or not. > so i'm inclined to agree with dim@ that we should not add architecture > specific conditions -- however i think adding compiler specific conditions > is a good idea. > > 2) the problem with settings WARNS= or specific -Wno-X or -Wno-error=X is that > expecially GCC doesn't have specific -WX flags for certain warnings. some > warnings are implied by -Wall and cannot be turned off seperately. so in > order to get rid of these warnings (which are being handled as errors), we > would need to disable -Wall. and i think setting WERROR= in order to handle > all warnings for specific code as warnings rather than as errors is the > better solution. > > i've reworked the patch to only remove WERROR=, where it is not needed anymore > for any supported arch, or where it can be wrapped in a compiler condition. It seems to me that the removal of unnecessary WERROR= needed no discussion since day one so why don't you go ahead and commit it. I don't understand the comment on issue #1 above. There is a minuscule (six, before your patch ?) number of Makefiles with WERROR= . If you make the assignment architecture-specific, the worst it can happen is that the variable is not cleared, and if the build breaks, all you need is to add the extra architecture in these few places. cheers luigi > cheers. > alex > > > > > - Philip > > > > -- > > Philip Paeps > > Senior Reality Engineer > > Ministry of Information > Index: sys/modules/xfs/Makefile > =================================================================== > --- sys/modules/xfs/Makefile (revision 228911) > +++ sys/modules/xfs/Makefile (working copy) > @@ -6,8 +6,6 @@ > > KMOD= xfs > > -WERROR= > - > SRCS = vnode_if.h \ > xfs_alloc.c \ > xfs_alloc_btree.c \ > Index: sys/modules/sound/driver/maestro/Makefile > =================================================================== > --- sys/modules/sound/driver/maestro/Makefile (revision 228911) > +++ sys/modules/sound/driver/maestro/Makefile (working copy) > @@ -5,6 +5,5 @@ > KMOD= snd_maestro > SRCS= device_if.h bus_if.h pci_if.h > SRCS+= maestro.c > -WERROR= > > .include > Index: sys/modules/aic7xxx/ahd/Makefile > =================================================================== > --- sys/modules/aic7xxx/ahd/Makefile (revision 228911) > +++ sys/modules/aic7xxx/ahd/Makefile (working copy) > @@ -4,7 +4,6 @@ > .PATH: ${.CURDIR}/../../../dev/aic7xxx > KMOD= ahd > > -WERROR= > GENSRCS= aic79xx_seq.h aic79xx_reg.h > REG_PRINT_OPT= > AHD_REG_PRETTY_PRINT=1 > Index: sys/modules/agp/Makefile > =================================================================== > --- sys/modules/agp/Makefile (revision 228911) > +++ sys/modules/agp/Makefile (working copy) > @@ -20,7 +20,6 @@ > SRCS+= device_if.h bus_if.h agp_if.h pci_if.h > SRCS+= opt_agp.h opt_bus.h > MFILES= kern/device_if.m kern/bus_if.m dev/agp/agp_if.m dev/pci/pci_if.m > -WERROR= > > EXPORT_SYMS= agp_find_device \ > agp_state \ > Index: sys/modules/bios/smapi/Makefile > =================================================================== > --- sys/modules/bios/smapi/Makefile (revision 228911) > +++ sys/modules/bios/smapi/Makefile (working copy) > @@ -6,7 +6,6 @@ > KMOD= smapi > SRCS= smapi.c smapi_bios.S \ > bus_if.h device_if.h > -WERROR= > .if ${CC:T:Mclang} == "clang" > # XXX: clang integrated-as doesn't grok 16-bit assembly yet > CFLAGS+= ${.IMPSRC:T:Msmapi_bios.S:C/^.+$/-no-integrated-as/} > Index: sys/modules/nve/Makefile > =================================================================== > --- sys/modules/nve/Makefile (revision 228911) > +++ sys/modules/nve/Makefile (working copy) > @@ -7,7 +7,9 @@ > device_if.h bus_if.h pci_if.h miibus_if.h \ > os+%DIKED-nve.h > OBJS+= nvenetlib.o > +.if ${CC:T:Mclang} == "clang" > WERROR= > +.endif > > CLEANFILES+= nvenetlib.o os+%DIKED-nve.h > nvenetlib.o: ${.CURDIR}/../../contrib/dev/nve/${MACHINE}/${.TARGET}.bz2.uu > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 12:06:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3EE9106566C for ; Tue, 27 Dec 2011 12:06:03 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 887AB8FC13 for ; Tue, 27 Dec 2011 12:06:03 +0000 (UTC) Received: from lstewart1.loshell.room52.net (ppp59-167-184-191.static.internode.on.net [59.167.184.191]) by lauren.room52.net (Postfix) with ESMTPSA id 40CA87E824; Tue, 27 Dec 2011 22:48:42 +1100 (EST) Message-ID: <4EF9B09A.4070103@freebsd.org> Date: Tue, 27 Dec 2011 22:48:42 +1100 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111016 Thunderbird/7.0.1 MIME-Version: 1.0 To: Ron McDowell References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> In-Reply-To: <4EF953ED.9060905@fuzzwad.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lauren.room52.net Cc: Doug Barton , freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 12:06:03 -0000 On 12/27/11 16:13, Ron McDowell wrote: > Doug Barton wrote: >> The story so far ... >> >> sysinstall was removed from HEAD in October. I (and others) objected on >> the basis that at this time there is no replacement for the post-install >> configuration role that sysinstall played. More sysinstall components >> were then removed. Then the old version of libdialog (which sysinstall >> used) was removed. Thus at this point it's not possible to easily >> restore sysinstall. >> >> So my question is, how much do you care? Is lack of that functionality >> in HEAD something that we care about? >> >> >> Doug > > We have around 90 web servers running 8.2p5 right now [and yes, I did > update the lot on Christmas Eve but that's a different story] and they > will not be upgraded to 9.0 until/unless the post-install functionality > that was lost by the removal of sysinstall is reintegrated in some way. > I also complained about it and was told in effect, "too bad." Everyone > who commented said sysinstall caused more problems than it solved, > although I've been using it for any system changes I needed that it was > capable of doing for as long back as I can remember, and my first > FreeBSD box was v2.2. > > I think removing any functionality that was in a previous release > without providing an equal-or-better alternative is a bad idea, and that > needs to be considered more carefully in the future. > > So this is not just a +1 vote, it's a +90. Sysintall is in 9 and will not be removed from the 9 branch. The installer used on the release media has changed, but as far as I understand, there is nothing stopping you from running sysinstall from a installer shell or using it for post installation configuration. Doug is only referring to the head branch (which will eventually in ~18-24 months become the 10 branch), so you should be able to have the best of both worlds with 9 i.e. try bsdinstall, fall back to sysinstall when you find bugs or missing features (don't forget to lodge bug reports for problems you find so that bsdinstall can be improved). On the topic of Doug's actual question, I see minimal sense in resurrecting sysinstall in head now. I would suggest it be done much closer to (say, 6 months before) the 10.0 release cycle, if no suitable post-installation configuration tool has materialised. In the meantime, cajole everyone who pops up saying "I really want post installation configuration support" to get involved with writing a bsdinstaller-like script (I think it should be completely separate to bsdinstaller, but perhaps use the same backend shell script functions/infrastructure) to do the job. Cheers, Lawrence From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 16:55:52 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74F03106566C; Tue, 27 Dec 2011 16:55:52 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 06C4C8FC17; Tue, 27 Dec 2011 16:55:52 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id ECBEFE6227; Tue, 27 Dec 2011 16:55:50 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=subject :references:from:content-transfer-encoding:content-type :in-reply-to:message-id:date:cc:to:mime-version; s=mail; bh=jYJQ Ki4m4EQuhSpGx+il8KkGxbs=; b=AF1o2Zpp+QLejrF3B4H6DD9CUSpVu+0SYZpj 0xF+W2kJ8ii6IgemeSagPYXEOhuuiQayjFPv4VovxBhj/5oJ30WOYOrF2BN/ZWrP C6KKVASYkj+1AAmzbfISjV8UyxuqplsfbxFiW+O2N5k9Tdwzff0g4FtHXiL6YxF9 rvDmVuM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=subject :references:from:content-transfer-encoding:content-type :in-reply-to:message-id:date:cc:to:mime-version; q=dns; s=mail; b= QXC/0p2aX/1pkuIr0YGcCDUf5/kePaOf2JyL0NA78iJVRBtk2JX8qp3JYsfEERzx xt7jU524T0jyP7UjfM8go/RsAegMwrVkQSsawp+HNGJk8SMA7zCP5m7pPoGNt7a3 48eUCJuoB1ZSnzNtEZZp/3kQm8m1xMDb1Ae/8dL21qY= Received: from [192.168.1.73] (188-222-18-231.zone13.bethere.co.uk [188.222.18.231]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id CB5D7E621E; Tue, 27 Dec 2011 16:55:50 +0000 (GMT) References: <4EF904F2.4020109@FreeBSD.org> <4EF95235.7020502@FreeBSD.org> From: Bruce Cran Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii In-Reply-To: <4EF95235.7020502@FreeBSD.org> Message-Id: Date: Tue, 27 Dec 2011 16:54:21 +0000 To: Doug Barton Mime-Version: 1.0 (1.0) X-Mailer: iPad Mail (9A405) Cc: freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 16:55:52 -0000 I think such a tool should /not/ be a port, since I expect it would include a= package browser in it. I think it's something that could really help new us= ers get used to FreeBSD without having to trawl through man pages right at t= he start. --=20 Bruce Cran Sent from my iPad On 27 Dec 2011, at 05:05, Doug Barton wrote: > On 12/26/2011 20:29, Xin LI wrote: >> On Mon, Dec 26, 2011 at 3:36 PM, Doug Barton wrote: >>> The story so far ... >>>=20 >>> sysinstall was removed from HEAD in October. I (and others) objected on >>> the basis that at this time there is no replacement for the post-install= >>> configuration role that sysinstall played. More sysinstall components >>> were then removed. Then the old version of libdialog (which sysinstall >>> used) was removed. Thus at this point it's not possible to easily >>> restore sysinstall. >>>=20 >>> So my question is, how much do you care? Is lack of that functionality >>> in HEAD something that we care about? >>=20 >> Perhaps make it a port instead? I personally don't use sysinstall for >> post-install tasks at all, but it won't hurt to have such >> functionality. >=20 > You're not the first person to suggest that, but I don't see how it's > actually responsive to the problem. This issue only affects HEAD, so a > port would not be generally useful. It would also be an enormous amount > of work to make it into a port. It would be much easier to revert the > necessary changes to bring back the old libdialog and sysinstall itself. >=20 >=20 > Doug >=20 > --=20 >=20 > [^L] >=20 > Breadth of IT experience, and depth of knowledge in the DNS. > Yours for the right price. :) http://SupersetSolutions.com/ >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"= From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 17:50:56 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7ECC1065672; Tue, 27 Dec 2011 17:50:56 +0000 (UTC) (envelope-from rcm@fuzzwad.org) Received: from mail.volente.us (unknown [IPv6:2001:470:7:d47::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8A5D68FC1D; Tue, 27 Dec 2011 17:50:56 +0000 (UTC) Received: from zombie.fuzzwad.net (localhost [127.0.0.1]) by mail.volente.us (8.14.4/8.14.4) with ESMTP id pBRHothR067717; Tue, 27 Dec 2011 11:50:55 -0600 (CST) (envelope-from rcm@fuzzwad.org) Message-ID: <4EFA057E.4030500@fuzzwad.org> Date: Tue, 27 Dec 2011 11:50:54 -0600 From: Ron McDowell User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Lawrence Stewart References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> <4EF9B09A.4070103@freebsd.org> In-Reply-To: <4EF9B09A.4070103@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Doug Barton , freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 17:50:56 -0000 Lawrence Stewart wrote: > On 12/27/11 16:13, Ron McDowell wrote: >> Doug Barton wrote: >>> The story so far ... >>> >>> sysinstall was removed from HEAD in October. I (and others) objected on >>> the basis that at this time there is no replacement for the >>> post-install >>> configuration role that sysinstall played. More sysinstall components >>> were then removed. Then the old version of libdialog (which sysinstall >>> used) was removed. Thus at this point it's not possible to easily >>> restore sysinstall. >>> >>> So my question is, how much do you care? Is lack of that functionality >>> in HEAD something that we care about? >>> >>> >>> Doug >> >> We have around 90 web servers running 8.2p5 right now [and yes, I did >> update the lot on Christmas Eve but that's a different story] and they >> will not be upgraded to 9.0 until/unless the post-install functionality >> that was lost by the removal of sysinstall is reintegrated in some way. >> I also complained about it and was told in effect, "too bad." Everyone >> who commented said sysinstall caused more problems than it solved, >> although I've been using it for any system changes I needed that it was >> capable of doing for as long back as I can remember, and my first >> FreeBSD box was v2.2. >> >> I think removing any functionality that was in a previous release >> without providing an equal-or-better alternative is a bad idea, and that >> needs to be considered more carefully in the future. >> >> So this is not just a +1 vote, it's a +90. > > Sysintall is in 9 and will not be removed from the 9 branch. The > installer used on the release media has changed, but as far as I > understand, there is nothing stopping you from running sysinstall from > a installer shell or using it for post installation configuration. You're right. I stand corrected and am happy to see I'll be able to upgrade to 9.0 after -RELEASE. > Doug is only referring to the head branch (which will eventually in > ~18-24 months become the 10 branch), so you should be able to have the > best of both worlds with 9 i.e. try bsdinstall, fall back to > sysinstall when you find bugs or missing features (don't forget to > lodge bug reports for problems you find so that bsdinstall can be > improved). > > On the topic of Doug's actual question, I see minimal sense in > resurrecting sysinstall in head now. I would suggest it be done much > closer to (say, 6 months before) the 10.0 release cycle, if no > suitable post-installation configuration tool has materialised. > > In the meantime, cajole everyone who pops up saying "I really want > post installation configuration support" to get involved with writing > a bsdinstaller-like script (I think it should be completely separate > to bsdinstaller, but perhaps use the same backend shell script > functions/infrastructure) to do the job. I guess this is a good time for me to quit bitching, get off my butt, and contribute something back to a project I've been using daily for almost 20 years. Having done similar sysadm development work [way back] on Tandy Xenix, SCO Xenix/Unix, and Dell SVR4 Unix, this is an area where I actually might know enough to be useful. To that end, the first task I'm assigning myself is to poke around in bsdinstall/libdialog and see how they work. As a related question, is there a good primer somewhere about how to use SVN? I'm using csup at present. -- Ron McDowell San Antonio TX From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 18:14:42 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16296106564A for ; Tue, 27 Dec 2011 18:14:42 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id D00878FC0A for ; Tue, 27 Dec 2011 18:14:41 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so11430259obb.13 for ; Tue, 27 Dec 2011 10:14:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=n5j6iqVk0xLsaDAmIREkfP1tGCUqcXAPwuPCN0b8CYc=; b=b0fNC9cQAwE8gK2e6dJEFYrDxNz5LJ7j7K6kHbU6z7PPlxoT3n+gJ+BOU2nwcqlHvY J5ZC4kzJfH/1PkYXTX0Qt6mDV6OXAJK0jfl8PwqZscSBPvmhYR3Ci0ivAHLRaVo9Bqua pOCqOqlj3ocwgWfLoWMSpk4x1HE1N9ops9P8k= Received: by 10.50.85.199 with SMTP id j7mr32501954igz.25.1325009681100; Tue, 27 Dec 2011 10:14:41 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id py4sm67659808igc.2.2011.12.27.10.14.37 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 27 Dec 2011 10:14:40 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 27 Dec 2011 10:12:43 -0800 From: YongHyeon PYUN Date: Tue, 27 Dec 2011 10:12:43 -0800 To: Rick Macklem Message-ID: <20111227181243.GA1664@michelle.cdnetworks.com> References: <20101108014022.GG1279@michelle.cdnetworks.com> <1480355747.640765.1324958150892.JavaMail.root@erie.cs.uoguelph.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1480355747.640765.1324958150892.JavaMail.root@erie.cs.uoguelph.ca> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: re(4) driver dropping packets when reading NFS files X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 18:14:42 -0000 On Mon, Dec 26, 2011 at 10:55:50PM -0500, Rick Macklem wrote: > Way back in Nov 2010, this thread was related to a problem I > had, where an re(4) { 810xE PCIe 10/100baseTX, according to the > driver } interface dropped received packets, resulting in a > significant impact of NFS performance. > > Well, it turns out that a recent (post r224506) commit seems to > have fixed the problem. It hasn't dropped any packets since I > upgraded to a kernel with a r228281 version of if_re.c. > > So, good news. > > Thanks to those maintaining this driver, rick > ps: If you have a need to know which commit fixed this, I can > probably test variants to find out. Otherwise, I'm just > happy that it's fixed.:-) Glad to know the issue was fixed. Probably the change made in r227593 or 227854 might have fixed it. From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 18:30:07 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED520106566B; Tue, 27 Dec 2011 18:30:06 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id A81548FC17; Tue, 27 Dec 2011 18:30:06 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.5/8.14.5) with ESMTP id pBRIU6Y9089304; Tue, 27 Dec 2011 10:30:06 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.5/8.14.5/Submit) id pBRIU6gx089303; Tue, 27 Dec 2011 10:30:06 -0800 (PST) (envelope-from sgk) Date: Tue, 27 Dec 2011 10:30:06 -0800 From: Steve Kargl To: Ron McDowell Message-ID: <20111227183006.GB83779@troutmask.apl.washington.edu> References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> <4EF9B09A.4070103@freebsd.org> <4EFA057E.4030500@fuzzwad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EFA057E.4030500@fuzzwad.org> User-Agent: Mutt/1.4.2.3i Cc: Lawrence Stewart , Doug Barton , freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 18:30:07 -0000 On Tue, Dec 27, 2011 at 11:50:54AM -0600, Ron McDowell wrote: > > As a related question, is there a good primer somewhere about how to use > SVN? I'm using csup at present. > http://wiki.freebsd.org/SubversionPrimer -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 19:21:10 2011 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7EF41065672 for ; Tue, 27 Dec 2011 19:21:10 +0000 (UTC) (envelope-from flo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B0C358FC0A; Tue, 27 Dec 2011 19:21:10 +0000 (UTC) Received: from nibbler-wlan.fritz.box (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBRJL9M4046188; Tue, 27 Dec 2011 19:21:10 GMT (envelope-from flo@FreeBSD.org) Message-ID: <4EFA1AA5.9090404@FreeBSD.org> Date: Tue, 27 Dec 2011 20:21:09 +0100 From: Florian Smeets User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0) Gecko/20111222 Thunderbird/10.0 MIME-Version: 1.0 To: Sean Bruno References: <1323868832.5283.9.camel@hitfishpass-lx.corp.yahoo.com> In-Reply-To: <1323868832.5283.9.camel@hitfishpass-lx.corp.yahoo.com> X-Enigmail-Version: 1.4a1pre Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7D4CBF9D72B3CD03D6E84C75" Cc: "current@freebsd.org" Subject: Re: dogfooding over in clusteradm land X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 19:21:10 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7D4CBF9D72B3CD03D6E84C75 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 14.12.11 14:20, Sean Bruno wrote: > We're seeing what looks like a syncher/ufs resource starvation on 9.0 o= n > the cvs2svn ports conversion box. I'm not sure what resource is tapped= > out. Effectively, I cannot access the directory under use and the > converter application stalls out waiting for some resource that isn't > clear. (Peter had posited kmem of some kind). >=20 > I've upped maxvnodes a bit on the host, turned off SUJ and mounted the > f/s in question with async and noatime for performance reasons. >=20 > Can someone hit me up with the cluebat? I can give you direct access t= o > the box for debuginationing. >=20 Just for the archives. This is fixed or at least considerably improved by r228838. The ports cvs2svn run went down from panicking after about ~22h to being finished after ~10h. Thanks to Sean and Attilio for giving me access to test boxes. Florian --------------enig7D4CBF9D72B3CD03D6E84C75 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAk76GqUACgkQapo8P8lCvwnH4gCgwOssyGWuxSi9eKx/qjEVVKNg QSAAniUtRH55/6wH5Eg9R2REaV9nhNjl =YAyF -----END PGP SIGNATURE----- --------------enig7D4CBF9D72B3CD03D6E84C75-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 19:27:08 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 1D47E1065676; Tue, 27 Dec 2011 19:27:08 +0000 (UTC) Date: Tue, 27 Dec 2011 19:27:08 +0000 From: Alexander Best To: Luigi Rizzo Message-ID: <20111227192708.GA58521@freebsd.org> References: <20111226101040.GA6361@freebsd.org> <20111227010449.GA6244@twoflower.paeps.cx> <20111227112743.GA154@freebsd.org> <20111227120409.GA64631@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111227120409.GA64631@onelab2.iet.unipi.it> Cc: freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 19:27:08 -0000 On Tue Dec 27 11, Luigi Rizzo wrote: > On Tue, Dec 27, 2011 at 11:27:43AM +0000, Alexander Best wrote: > > On Tue Dec 27 11, Philip Paeps wrote: > > > On 2011-12-26 10:10:40 (+0000), Alexander Best wrote: > > > > i grep'ed through src/sys and found several places where WERROR= was set in > > > > order to get rid of the default -Werror setting. i tried to remove those > > > > WERROR= overrides from any Makefile, where doing so did not break tinderbox. > > > > > > > > in those cases, where it couldn't be completely removed, i added conditions to > > > > only set WERROR= for the particular achitecture or compiler, where tinderbox > > > > did not suceed without the WERROR=. > > > > > > Wouldn't it be better to set WARNS=x rather than WERROR=? WERROR= says "this > > > code has bugs, it breaks tinderbox" whereas WARNS=x says "this code has the > > > following kind of bugs which break tinderbox". > > > > > > Possibly wrapped in an architecture-test where appropriate. > > > > well there are a few issues here: > > > > 1) Jan Beich informed me via a private email that enclosing WERROR in arch > > specific conditions is a bad idea. if the code gets ported to a new > > architecture WERROR doesn't get set and so for every new architecture one > > has to evaluate again, whether WERROR needs to be set or not. > > so i'm inclined to agree with dim@ that we should not add architecture > > specific conditions -- however i think adding compiler specific conditions > > is a good idea. > > > > 2) the problem with settings WARNS= or specific -Wno-X or -Wno-error=X is that > > expecially GCC doesn't have specific -WX flags for certain warnings. some > > warnings are implied by -Wall and cannot be turned off seperately. so in > > order to get rid of these warnings (which are being handled as errors), we > > would need to disable -Wall. and i think setting WERROR= in order to handle > > all warnings for specific code as warnings rather than as errors is the > > better solution. > > > > i've reworked the patch to only remove WERROR=, where it is not needed anymore > > for any supported arch, or where it can be wrapped in a compiler condition. > > It seems to me that the removal of unnecessary WERROR= needed no > discussion since day one so why don't you go ahead and commit it. anybody is free to commit this part, since i don't own a commit bit. ;) > > I don't understand the comment on issue #1 above. There is a minuscule > (six, before your patch ?) > number of Makefiles with WERROR= . If you make the assignment > architecture-specific, the worst it can happen is that the variable > is not cleared, and if the build breaks, all you need is to > add the extra architecture in these few places. good point. basically the question with WERROR is: should it be a big hammer to disable turning warnings into errors for all archs or do we want to set WERROR in a more specific manor, where it's absolutely necessary. cheers. alex > > cheers > luigi > > > cheers. > > alex > > > > > > > > - Philip > > > > > > -- > > > Philip Paeps > > > Senior Reality Engineer > > > Ministry of Information > > > Index: sys/modules/xfs/Makefile > > =================================================================== > > --- sys/modules/xfs/Makefile (revision 228911) > > +++ sys/modules/xfs/Makefile (working copy) > > @@ -6,8 +6,6 @@ > > > > KMOD= xfs > > > > -WERROR= > > - > > SRCS = vnode_if.h \ > > xfs_alloc.c \ > > xfs_alloc_btree.c \ > > Index: sys/modules/sound/driver/maestro/Makefile > > =================================================================== > > --- sys/modules/sound/driver/maestro/Makefile (revision 228911) > > +++ sys/modules/sound/driver/maestro/Makefile (working copy) > > @@ -5,6 +5,5 @@ > > KMOD= snd_maestro > > SRCS= device_if.h bus_if.h pci_if.h > > SRCS+= maestro.c > > -WERROR= > > > > .include > > Index: sys/modules/aic7xxx/ahd/Makefile > > =================================================================== > > --- sys/modules/aic7xxx/ahd/Makefile (revision 228911) > > +++ sys/modules/aic7xxx/ahd/Makefile (working copy) > > @@ -4,7 +4,6 @@ > > .PATH: ${.CURDIR}/../../../dev/aic7xxx > > KMOD= ahd > > > > -WERROR= > > GENSRCS= aic79xx_seq.h aic79xx_reg.h > > REG_PRINT_OPT= > > AHD_REG_PRETTY_PRINT=1 > > Index: sys/modules/agp/Makefile > > =================================================================== > > --- sys/modules/agp/Makefile (revision 228911) > > +++ sys/modules/agp/Makefile (working copy) > > @@ -20,7 +20,6 @@ > > SRCS+= device_if.h bus_if.h agp_if.h pci_if.h > > SRCS+= opt_agp.h opt_bus.h > > MFILES= kern/device_if.m kern/bus_if.m dev/agp/agp_if.m dev/pci/pci_if.m > > -WERROR= > > > > EXPORT_SYMS= agp_find_device \ > > agp_state \ > > Index: sys/modules/bios/smapi/Makefile > > =================================================================== > > --- sys/modules/bios/smapi/Makefile (revision 228911) > > +++ sys/modules/bios/smapi/Makefile (working copy) > > @@ -6,7 +6,6 @@ > > KMOD= smapi > > SRCS= smapi.c smapi_bios.S \ > > bus_if.h device_if.h > > -WERROR= > > .if ${CC:T:Mclang} == "clang" > > # XXX: clang integrated-as doesn't grok 16-bit assembly yet > > CFLAGS+= ${.IMPSRC:T:Msmapi_bios.S:C/^.+$/-no-integrated-as/} > > Index: sys/modules/nve/Makefile > > =================================================================== > > --- sys/modules/nve/Makefile (revision 228911) > > +++ sys/modules/nve/Makefile (working copy) > > @@ -7,7 +7,9 @@ > > device_if.h bus_if.h pci_if.h miibus_if.h \ > > os+%DIKED-nve.h > > OBJS+= nvenetlib.o > > +.if ${CC:T:Mclang} == "clang" > > WERROR= > > +.endif > > > > CLEANFILES+= nvenetlib.o os+%DIKED-nve.h > > nvenetlib.o: ${.CURDIR}/../../contrib/dev/nve/${MACHINE}/${.TARGET}.bz2.uu > > > _______________________________________________ > > freebsd-arch@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 19:29:42 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 430241065693; Tue, 27 Dec 2011 19:29:42 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 9794715EFF1; Tue, 27 Dec 2011 19:29:32 +0000 (UTC) Message-ID: <4EFA1C9C.60601@FreeBSD.org> Date: Tue, 27 Dec 2011 11:29:32 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Lawrence Stewart References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> <4EF9B09A.4070103@freebsd.org> In-Reply-To: <4EF9B09A.4070103@freebsd.org> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current , Ron McDowell Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 19:29:42 -0000 On 12/27/2011 03:48, Lawrence Stewart wrote: > On the topic of Doug's actual question, I see minimal sense in > resurrecting sysinstall in head now. I would suggest it be done much > closer to (say, 6 months before) the 10.0 release cycle, if no suitable > post-installation configuration tool has materialised. My concern about that approach is that 9.0 hasn't even been released yet and we've already seen changes that are going to make it hard to resurrect sysinstall if that's the decision we come to. Waiting another year or 2 would make it impossible. Doug -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 19:31:17 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F784106567B for ; Tue, 27 Dec 2011 19:31:17 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw12.york.ac.uk (mail-gw12.york.ac.uk [144.32.129.162]) by mx1.freebsd.org (Postfix) with ESMTP id 2FC5E8FC19 for ; Tue, 27 Dec 2011 19:31:16 +0000 (UTC) Received: from ury.york.ac.uk ([144.32.108.81]:43935) by mail-gw12.york.ac.uk with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1RfcXS-0002UL-W5; Tue, 27 Dec 2011 19:18:19 +0000 Received: from gavin (helo=localhost) by ury.york.ac.uk with local-esmtp (Exim 4.77) (envelope-from ) id 1RfcXS-0002WZ-Pg; Tue, 27 Dec 2011 19:18:18 +0000 Date: Tue, 27 Dec 2011 19:18:18 +0000 (GMT) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: Ron McDowell In-Reply-To: <4EFA057E.4030500@fuzzwad.org> Message-ID: References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> <4EF9B09A.4070103@freebsd.org> <4EFA057E.4030500@fuzzwad.org> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Cc: freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 19:31:17 -0000 On Tue, 27 Dec 2011, Ron McDowell wrote: > As a related question, is there a good primer somewhere about how to use SVN? > I'm using csup at present. - Install the subversion port - Downlaod the source. To get HEAD code: svn co svn://svn.freebsd.org/base/head/ or to get 9-stable code: svn co svn://svn.freebsd.org/base/stable/9 (If you want to check it out into a different directory, append the dir name, for example: "svn co svn://svn.freebsd.org/base/head/ src") - Make your changes :) - To get a diff of your changes, you can just use "svn diff" Gavin From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 20:32:14 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B11DE106567A; Tue, 27 Dec 2011 20:32:14 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 636D88FC0C; Tue, 27 Dec 2011 20:32:14 +0000 (UTC) Received: from [10.0.0.63] (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id pBRKSisK039899 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Tue, 27 Dec 2011 13:28:46 -0700 (MST) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20111227010449.GA6244@twoflower.paeps.cx> Date: Tue, 27 Dec 2011 13:28:44 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <8DD9BAA5-78E0-491A-9E4E-6915B0A9FBAA@bsdimp.com> References: <20111226101040.GA6361@freebsd.org> <20111227010449.GA6244@twoflower.paeps.cx> To: Philip Paeps X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Tue, 27 Dec 2011 13:28:46 -0700 (MST) Cc: freebsd-current@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 20:32:14 -0000 On Dec 26, 2011, at 6:04 PM, Philip Paeps wrote: > On 2011-12-26 10:10:40 (+0000), Alexander Best = wrote: >> i grep'ed through src/sys and found several places where WERROR=3D = was set in >> order to get rid of the default -Werror setting. i tried to remove = those >> WERROR=3D overrides from any Makefile, where doing so did not break = tinderbox. >>=20 >> in those cases, where it couldn't be completely removed, i added = conditions to >> only set WERROR=3D for the particular achitecture or compiler, where = tinderbox >> did not suceed without the WERROR=3D. >=20 > Wouldn't it be better to set WARNS=3Dx rather than WERROR=3D? WERROR=3D= says "this > code has bugs, it breaks tinderbox" whereas WARNS=3Dx says "this code = has the > following kind of bugs which break tinderbox". Agreed... > Possibly wrapped in an architecture-test where appropriate. Not so much... When you make architecture-specific tests, experience = has shown that we don't fix bugs and they languish for a long time. = Many times, these warnings are real. Sadly, we've found no way to tag = the ones that aren't real yet as safe to ignore... Warner From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 20:32:14 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B11DE106567A; Tue, 27 Dec 2011 20:32:14 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 636D88FC0C; Tue, 27 Dec 2011 20:32:14 +0000 (UTC) Received: from [10.0.0.63] (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id pBRKSisK039899 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Tue, 27 Dec 2011 13:28:46 -0700 (MST) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20111227010449.GA6244@twoflower.paeps.cx> Date: Tue, 27 Dec 2011 13:28:44 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <8DD9BAA5-78E0-491A-9E4E-6915B0A9FBAA@bsdimp.com> References: <20111226101040.GA6361@freebsd.org> <20111227010449.GA6244@twoflower.paeps.cx> To: Philip Paeps X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Tue, 27 Dec 2011 13:28:46 -0700 (MST) Cc: freebsd-current@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 20:32:14 -0000 On Dec 26, 2011, at 6:04 PM, Philip Paeps wrote: > On 2011-12-26 10:10:40 (+0000), Alexander Best = wrote: >> i grep'ed through src/sys and found several places where WERROR=3D = was set in >> order to get rid of the default -Werror setting. i tried to remove = those >> WERROR=3D overrides from any Makefile, where doing so did not break = tinderbox. >>=20 >> in those cases, where it couldn't be completely removed, i added = conditions to >> only set WERROR=3D for the particular achitecture or compiler, where = tinderbox >> did not suceed without the WERROR=3D. >=20 > Wouldn't it be better to set WARNS=3Dx rather than WERROR=3D? WERROR=3D= says "this > code has bugs, it breaks tinderbox" whereas WARNS=3Dx says "this code = has the > following kind of bugs which break tinderbox". Agreed... > Possibly wrapped in an architecture-test where appropriate. Not so much... When you make architecture-specific tests, experience = has shown that we don't fix bugs and they languish for a long time. = Many times, these warnings are real. Sadly, we've found no way to tag = the ones that aren't real yet as safe to ignore... Warner From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 22:20:13 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0A46106564A for ; Tue, 27 Dec 2011 22:20:13 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: from redundancy.redundancy.org (75-101-96-57.dsl.static.sonic.net [75.101.96.57]) by mx1.freebsd.org (Postfix) with SMTP id 758DF8FC16 for ; Tue, 27 Dec 2011 22:20:13 +0000 (UTC) Received: (qmail 73876 invoked by uid 1001); 27 Dec 2011 21:53:55 -0000 Date: Tue, 27 Dec 2011 13:53:55 -0800 From: David Thiel To: freebsd-current@freebsd.org Message-ID: <20111227215330.GI45484@redundancy.redundancy.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13 X-OpenPGP-Key-available: http://redundancy.redundancy.org/lx.gpg X-Face: %H~{$1~NOw1y#%mM6{|4:/ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 22:20:13 -0000 I've had multiple machines now (9.0-RC3, amd64, i386 and earlier 9-CURRENT on ppc) running SU+J that have had unexplained panics and crashes start happening relating to disk I/O. When I end up running a full fsck, it keeps turning out that the disk is dirty and corrupted, but no mechanism is in place with SU+J to detect and fix this. A bgfsck never happens, but a manual fsck in single-user does indeed fix the crashing and weird behavior. Others have tested their SU+J volumes and found them to have errors as well. This makes me super nervous. Basically, the way SU+J seems to operate is this: http://redundancy.redundancy.org/fscklog2 "Oh hey, I see you shut down uncleanly, let's check everything looks good, off you go, whee" Until I actually go and fsck, when I get: http://redundancy.redundancy.org/fscklog1 So, I understand that journalling doesn't replace the need for a potential fsck (though I never had this problem with gjournal), but without a way for the system to detect that a fsck is necessary, this seems pretty much a guaranteed recipe for data corruption, and seems to offer little to no benefit over plain SU+fsck, or even just mounting async. So: is everyone else seeing this? Am I misunderstanding how SU+J should be used? How should the error resolution process really happen? Thanks, David From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 22:28:06 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A22B71065672 for ; Tue, 27 Dec 2011 22:28:06 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 6BD1E8FC14 for ; Tue, 27 Dec 2011 22:28:06 +0000 (UTC) Received: from julian-mac.elischer.org (c-67-180-24-15.hsd1.ca.comcast.net [67.180.24.15]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id pBRM9vcd045614 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 27 Dec 2011 14:09:58 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <4EFA425B.8090304@freebsd.org> Date: Tue, 27 Dec 2011 14:10:35 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.25) Gecko/20111213 Thunderbird/3.1.17 MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: fetch reading one char at a time X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 22:28:06 -0000 I noted the following behaviour from "fetch" today.. I am actually hunting another problem so I'm just posting it here in case anyone recognises it and knows where to fix it... "d" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte " " 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "s" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "u" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "c" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "c" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "e" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "s" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "s" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "f" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "u" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "l" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "." 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte "\r" 48885 fetch RET read 1 48885 fetch CALL gettimeofday(0x7fffffffcda0,0) 48885 fetch RET gettimeofday 0 48885 fetch CALL read(0x3,0x7fffffffce0f,0x1) 48885 fetch GIO fd 3 read 1 byte From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 22:29:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DD751065670 for ; Tue, 27 Dec 2011 22:29:29 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id DA6818FC1A for ; Tue, 27 Dec 2011 22:29:28 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so11739104obb.13 for ; Tue, 27 Dec 2011 14:29:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oU3xYWNvNf3PzC1Q6oJ6+gI1N8p86jzEE/73vFPJuZI=; b=gHy0QqMEZY++L5d2RyxWOZFeA8ImRV/DFw+nL2Kt9Gk163pEnT5mSIEVlVghs3LtXN IzMe5xX03SyEeMoXJSk5qgJal4/JKms6lpTSAfk3TZfdCkCcxppveMaQbGrCXvezpJkQ Mb4AHw21f8uOcXXBF8fK+Ii/qpSYrhFIrZLj0= MIME-Version: 1.0 Received: by 10.182.45.102 with SMTP id l6mr26769391obm.0.1325024967240; Tue, 27 Dec 2011 14:29:27 -0800 (PST) Received: by 10.182.67.163 with HTTP; Tue, 27 Dec 2011 14:29:27 -0800 (PST) In-Reply-To: <20111227215330.GI45484@redundancy.redundancy.org> References: <20111227215330.GI45484@redundancy.redundancy.org> Date: Tue, 27 Dec 2011 14:29:27 -0800 Message-ID: From: Xin LI To: David Thiel Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org Subject: Re: SU+J systems do not fsck themselves X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 22:29:29 -0000 On Tue, Dec 27, 2011 at 1:53 PM, David Thiel wrote: > I've had multiple machines now (9.0-RC3, amd64, i386 and earlier > 9-CURRENT on ppc) running SU+J that have had unexplained panics and > crashes start happening relating to disk I/O. When I end up running a > full fsck, it keeps turning out that the disk is dirty and corrupted, > but no mechanism is in place with SU+J to detect and fix this. A bgfsck > never happens, but a manual fsck in single-user does indeed fix the > crashing and weird behavior. Others have tested their SU+J volumes and > found them to have errors as well. This makes me super nervous. > > Basically, the way SU+J seems to operate is this: > > http://redundancy.redundancy.org/fscklog2 > > "Oh hey, I see you shut down uncleanly, let's check everything looks > good, off you go, whee" > > Until I actually go and fsck, when I get: > > http://redundancy.redundancy.org/fscklog1 > > So, I understand that journalling doesn't replace the need for a > potential fsck (though I never had this problem with gjournal), but > without a way for the system to detect that a fsck is necessary, this > seems pretty much a guaranteed recipe for data corruption, and seems to > offer little to no benefit over plain SU+fsck, or even just mounting > async. > > So: is everyone else seeing this? Am I misunderstanding how SU+J should > be used? How should the error resolution process really happen? I'm not sure if your experiments are right here, the second log shows you're running it read-only, which is likely caused by running it on live file system. What I would suggest to do is: - Reset the system while it's running; - Boot into single user mode; - 'dd' the disk image to an image; - Boot the system normally and: - use mdconfig -a -t vnode -f on copy of the image - use journalled fsck; - use normal fsck to check if the journalled fsck did the right thing. This would rule out possible after-mount introduced changes, etc. I personally did not hit problems a few months ago but I didn't re-test recently. Cheers, -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 22:36:38 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1F3A106566C for ; Tue, 27 Dec 2011 22:36:38 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: from redundancy.redundancy.org (75-101-96-57.dsl.static.sonic.net [75.101.96.57]) by mx1.freebsd.org (Postfix) with SMTP id 9433F8FC13 for ; Tue, 27 Dec 2011 22:36:38 +0000 (UTC) Received: (qmail 74731 invoked by uid 1001); 27 Dec 2011 22:37:02 -0000 Date: Tue, 27 Dec 2011 14:37:02 -0759 From: David Thiel To: Xin LI Message-ID: <20111227223638.GK45484@redundancy.redundancy.org> References: <20111227215330.GI45484@redundancy.redundancy.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13 X-OpenPGP-Key-available: http://redundancy.redundancy.org/lx.gpg X-Face: %H~{$1~NOw1y#%mM6{|4:/ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 22:36:38 -0000 On Tue, Dec 27, 2011 at 02:29:03PM -0800, Xin LI wrote: > I'm not sure if your experiments are right here, the second log shows > you're running it read-only, which is likely caused by running it on > live file system. Yes, this most recent instance is me running it on a live FS, because I'm using that machine to type this right now. :) However, I've had the issues fixed in single-user on other systems and had the problems go away. At least for a bit. > - use journalled fsck; > - use normal fsck to check if the journalled fsck did the right thing. When you say "use journalled fsck", what's the proper way to initiate that? I don't see any journal-related options in the man page. From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 22:48:48 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F504106566B for ; Tue, 27 Dec 2011 22:48:48 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) by mx1.freebsd.org (Postfix) with ESMTP id 6EC848FC0C for ; Tue, 27 Dec 2011 22:48:47 +0000 (UTC) Received: from delta.delphij.net (drawbridge.ixsystems.com [206.40.55.65]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 2544914CE6; Tue, 27 Dec 2011 14:48:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1325026127; bh=TcF6VaoN4bHgtMyx9ye8GeESY6E5jIDpxwM/GaNqQqo=; h=Message-ID:Date:From:Reply-To:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ct7+RwGrHdlZQbK7exPkR7nszNDS2hvlln67ICq3nbzEsOlEvjzIt03BjH0K1EmwS hxZUm893WRyGwZSoxtysSnKNHPHz04bIuvMgYBS6Vd+lhm/qv2JhjtZkh3Fk2G5OjG bDSRoni1wsQDnyh9hA1qBIwYqMTn5If8UcSHYXAo= Message-ID: <4EFA4B4E.201@delphij.net> Date: Tue, 27 Dec 2011 14:48:46 -0800 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: David Thiel References: <20111227215330.GI45484@redundancy.redundancy.org> <20111227223638.GK45484@redundancy.redundancy.org> In-Reply-To: <20111227223638.GK45484@redundancy.redundancy.org> X-Enigmail-Version: undefined Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: d@delphij.net, freebsd-current@freebsd.org Subject: Re: SU+J systems do not fsck themselves X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 22:48:48 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/27/11 14:36, David Thiel wrote: > On Tue, Dec 27, 2011 at 02:29:03PM -0800, Xin LI wrote: >> I'm not sure if your experiments are right here, the second log >> shows you're running it read-only, which is likely caused by >> running it on live file system. > > Yes, this most recent instance is me running it on a live FS, > because I'm using that machine to type this right now. :) However, > I've had the issues fixed in single-user on other systems and had > the problems go away. At least for a bit. > >> - use journalled fsck; - use normal fsck to check if the >> journalled fsck did the right thing. > > When you say "use journalled fsck", what's the proper way to > initiate that? I don't see any journal-related options in the man > page. fsck -p perhaps? IIRC the fsck_ufs(8) would use journal if it's available and up-to-date. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk76S04ACgkQOfuToMruuMChEACfXyh1Y7IGiATqJdnFKeuIS2vB vJMAn0gCPy98kohAh3LD9ieIASPmksHd =L7lN -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 22:54:28 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 60B701065673; Tue, 27 Dec 2011 22:54:28 +0000 (UTC) Date: Tue, 27 Dec 2011 22:54:28 +0000 From: Alexander Best To: Warner Losh Message-ID: <20111227225428.GA12771@freebsd.org> References: <20111226101040.GA6361@freebsd.org> <20111227010449.GA6244@twoflower.paeps.cx> <8DD9BAA5-78E0-491A-9E4E-6915B0A9FBAA@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8DD9BAA5-78E0-491A-9E4E-6915B0A9FBAA@bsdimp.com> Cc: freebsd-arch@freebsd.org, freebsd-current@freebsd.org, Philip Paeps Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 22:54:28 -0000 On Tue Dec 27 11, Warner Losh wrote: > > On Dec 26, 2011, at 6:04 PM, Philip Paeps wrote: > > > On 2011-12-26 10:10:40 (+0000), Alexander Best wrote: > >> i grep'ed through src/sys and found several places where WERROR= was set in > >> order to get rid of the default -Werror setting. i tried to remove those > >> WERROR= overrides from any Makefile, where doing so did not break tinderbox. > >> > >> in those cases, where it couldn't be completely removed, i added conditions to > >> only set WERROR= for the particular achitecture or compiler, where tinderbox > >> did not suceed without the WERROR=. > > > > Wouldn't it be better to set WARNS=x rather than WERROR=? WERROR= says "this > > code has bugs, it breaks tinderbox" whereas WARNS=x says "this code has the > > following kind of bugs which break tinderbox". > > Agreed... in this case it would have to be WARNS=1 then, because anything > 1 will enable -Wall, which is the warning that breaks sys/modules/ie. cheers. alex > > > Possibly wrapped in an architecture-test where appropriate. > > Not so much... When you make architecture-specific tests, experience has shown that we don't fix bugs and they languish for a long time. Many times, these warnings are real. Sadly, we've found no way to tag the ones that aren't real yet as safe to ignore... > > Warner > From owner-freebsd-current@FreeBSD.ORG Tue Dec 27 23:49:21 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D49EB106566B; Tue, 27 Dec 2011 23:49:21 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 935BE8FC0A; Tue, 27 Dec 2011 23:49:21 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:2838:1eb:929f:da87] (unknown [IPv6:2001:7b8:3a7:0:2838:1eb:929f:da87]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id B2E4A5C37; Wed, 28 Dec 2011 00:49:19 +0100 (CET) Message-ID: <4EFA597D.3000508@FreeBSD.org> Date: Wed, 28 Dec 2011 00:49:17 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-arch@freebsd.org References: <20111226101040.GA6361@freebsd.org> <20111227010449.GA6244@twoflower.paeps.cx> In-Reply-To: <20111227010449.GA6244@twoflower.paeps.cx> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 23:49:21 -0000 On 2011-12-27 02:04, Philip Paeps wrote: > On 2011-12-26 10:10:40 (+0000), Alexander Best wrote: >> i grep'ed through src/sys and found several places where WERROR= was set in >> order to get rid of the default -Werror setting. i tried to remove those >> WERROR= overrides from any Makefile, where doing so did not break tinderbox. >> >> in those cases, where it couldn't be completely removed, i added conditions to >> only set WERROR= for the particular achitecture or compiler, where tinderbox >> did not suceed without the WERROR=. > > Wouldn't it be better to set WARNS=x rather than WERROR=? WERROR= says "this > code has bugs, it breaks tinderbox" whereas WARNS=x says "this code has the > following kind of bugs which break tinderbox". In my opinion, WERROR= says: there are warnings in this code which cannot be fixed right now, due to varying reasons, but we don't want to muffle them entirely, so somebody will eventually fix them in the future (or just delete the code, if it is unmaintained, or unmaintainable, like nve). If you set WARNS to a low level, you can be sure nobody ever sees the warnings, and they will never be fixed. That may be appropriate in some cases, but not the ones I just added WERROR= to. Those are just crufty drivers, that nobody wants to burn their fingers on. :) From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 02:32:54 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE90D1065678; Wed, 28 Dec 2011 02:32:54 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id ADEF78FC29; Wed, 28 Dec 2011 02:32:54 +0000 (UTC) Received: from lstewart1.loshell.room52.net (ppp59-167-184-191.static.internode.on.net [59.167.184.191]) by lauren.room52.net (Postfix) with ESMTPSA id 0D0107E820; Wed, 28 Dec 2011 13:32:53 +1100 (EST) Message-ID: <4EFA7FD4.10600@freebsd.org> Date: Wed, 28 Dec 2011 13:32:52 +1100 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111016 Thunderbird/7.0.1 MIME-Version: 1.0 To: Doug Barton References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> <4EF9B09A.4070103@freebsd.org> <4EFA1C9C.60601@FreeBSD.org> In-Reply-To: <4EFA1C9C.60601@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lauren.room52.net Cc: freebsd-current , Ron McDowell Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 02:32:55 -0000 On 12/28/11 06:29, Doug Barton wrote: > On 12/27/2011 03:48, Lawrence Stewart wrote: >> On the topic of Doug's actual question, I see minimal sense in >> resurrecting sysinstall in head now. I would suggest it be done much >> closer to (say, 6 months before) the 10.0 release cycle, if no suitable >> post-installation configuration tool has materialised. > > My concern about that approach is that 9.0 hasn't even been released yet > and we've already seen changes that are going to make it hard to > resurrect sysinstall if that's the decision we come to. Waiting another > year or 2 would make it impossible. Which changes are you referring to? I would have thought a reverse merge to undo the deletion of the sysinstall and old libdialog sources would be very minimal work. We'd also probably need a few extra build system changes to make sure old libdialog is perhaps statically compiled into sysinstall as it would be the only in-tree consumer, but that's not hard either. I may be lacking some imagination, but don't really see why it would become harder the longer we wait. Cheers, Lawrence From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 03:33:22 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id C5EF8106564A; Wed, 28 Dec 2011 03:33:22 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 49E1D15218C; Wed, 28 Dec 2011 03:33:22 +0000 (UTC) Message-ID: <4EFA8E01.6050101@FreeBSD.org> Date: Tue, 27 Dec 2011 19:33:21 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Lawrence Stewart References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> <4EF9B09A.4070103@freebsd.org> <4EFA1C9C.60601@FreeBSD.org> <4EFA7FD4.10600@freebsd.org> In-Reply-To: <4EFA7FD4.10600@freebsd.org> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current , Ron McDowell Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 03:33:22 -0000 On 12/27/2011 18:32, Lawrence Stewart wrote: > On 12/28/11 06:29, Doug Barton wrote: >> On 12/27/2011 03:48, Lawrence Stewart wrote: >>> On the topic of Doug's actual question, I see minimal sense in >>> resurrecting sysinstall in head now. I would suggest it be done much >>> closer to (say, 6 months before) the 10.0 release cycle, if no suitable >>> post-installation configuration tool has materialised. >> >> My concern about that approach is that 9.0 hasn't even been released yet >> and we've already seen changes that are going to make it hard to >> resurrect sysinstall if that's the decision we come to. Waiting another >> year or 2 would make it impossible. > > Which changes are you referring to? I would have thought a reverse merge > to undo the deletion of the sysinstall and old libdialog sources would > be very minimal work. Then I admire your mad skillz, because it sounds like a lot of work to me. :) > We'd also probably need a few extra build system > changes to make sure old libdialog is perhaps statically compiled into > sysinstall as it would be the only in-tree consumer, but that's not hard > either. I may be lacking some imagination, but don't really see why it > would become harder the longer we wait. My concern is that it's going to get worse as time goes along. Without sysinstall in the base people are going to feel free to make changes to things that sysinstall depends on (as they have already), and waiting a year or 2 to resurrect it will cause that problem to grow exponentially. Doug -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 05:14:04 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6D801065673 for ; Wed, 28 Dec 2011 05:14:04 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: from redundancy.redundancy.org (75-101-96-57.dsl.static.sonic.net [75.101.96.57]) by mx1.freebsd.org (Postfix) with SMTP id 9B9538FC0C for ; Wed, 28 Dec 2011 05:14:04 +0000 (UTC) Received: (qmail 82671 invoked by uid 1001); 28 Dec 2011 05:14:28 -0000 Date: Tue, 27 Dec 2011 21:14:28 -0800 From: David Thiel To: d@delphij.net Message-ID: <20111228051404.GL45484@redundancy.redundancy.org> References: <20111227215330.GI45484@redundancy.redundancy.org> <20111227223638.GK45484@redundancy.redundancy.org> <4EFA4B4E.201@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EFA4B4E.201@delphij.net> X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13 X-OpenPGP-Key-available: http://redundancy.redundancy.org/lx.gpg X-Face: %H~{$1~NOw1y#%mM6{|4:/ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 05:14:04 -0000 On Tue, Dec 27, 2011 at 02:48:22PM -0800, Xin Li wrote: > >> - use journalled fsck; - use normal fsck to check if the > >> journalled fsck did the right thing. Ok, here is the log of fsck with and without journal. http://redundancy.redundancy.org/fscklog3 That was done the very next boot, after a clean shutdown. The errors from the previous live fsck aren't there (oddly), but there are still are apparently some corrections made. The next fsck still complains, but doesn't give any salvage prompts. Here is jsa@'s, done on a live FS with SU+J: http://redundancy.redundancy.org/fscklog4 I'm not actually looking to solve my particular problem per se. The issue is that almost everyone I've checked with that's running SU+J gets unref'd file and other errors when they check their filesystem (with the fs live). Unless I'm missing something, a running FS should never have those kinds of errors unless you deliberately disabled fsck. This leaves only a couple options: - SU+J and fsck do not work correctly together to fix corruption on boot, i.e. bgfsck isn't getting run when it should - Stuff is getting completely screwed up after boot - fsck is giving incorrect results - I'm completely clueless about how SU+J is supposed to behave or be deployed I'm pretty certain that the first is the issue here. It would be great if others could check their own SU+J filesystems so we could get a few more data points. From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 06:08:28 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E1151065672; Wed, 28 Dec 2011 06:08:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id BD1698FC15; Wed, 28 Dec 2011 06:08:27 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so16684552vcb.13 for ; Tue, 27 Dec 2011 22:08:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=5jzksAvwTG5vlk3yhE0VGpBgwaa9K9CG6U9fKpJtxkc=; b=o4IVi0oaLJK3qQ/Og934cBEp19+tvnTriJMXYduV3Q1WoBrv8cjtZtAdeXYwOlurUY rNXyFHqzAdLjI4dUX1oDKcsjTaYZEB7HKEMaRVIhS5PTImApP3AEEwFmsPiQWKWdcv1g Ovsn545nTch6UhLsMmj+V5OK8rujjCCmP9eTY= MIME-Version: 1.0 Received: by 10.220.213.200 with SMTP id gx8mr18011261vcb.13.1325052507073; Tue, 27 Dec 2011 22:08:27 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Tue, 27 Dec 2011 22:08:26 -0800 (PST) In-Reply-To: <4EFA8E01.6050101@FreeBSD.org> References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> <4EF9B09A.4070103@freebsd.org> <4EFA1C9C.60601@FreeBSD.org> <4EFA7FD4.10600@freebsd.org> <4EFA8E01.6050101@FreeBSD.org> Date: Tue, 27 Dec 2011 22:08:26 -0800 X-Google-Sender-Auth: Ubwy22LC6JFI8KFJESej0IyV0IQ Message-ID: From: Adrian Chadd To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Cc: Lawrence Stewart , freebsd-current , Ron McDowell Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 06:08:28 -0000 Hi, Why not just list the things that sysinstall did that people like, and extract out / reimplement those bits? Noone's going to complain if you write say, a stand-alone package browser, or a stand-alone gui upgrade tool, or stand-alone configuration program, etc. Adrian From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 06:31:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 057CA106564A; Wed, 28 Dec 2011 06:31:03 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id DBC73150C57; Wed, 28 Dec 2011 06:30:32 +0000 (UTC) Message-ID: <4EFAB788.2040508@FreeBSD.org> Date: Tue, 27 Dec 2011 22:30:32 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Adrian Chadd References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> <4EF9B09A.4070103@freebsd.org> <4EFA1C9C.60601@FreeBSD.org> <4EFA7FD4.10600@freebsd.org> <4EFA8E01.6050101@FreeBSD.org> In-Reply-To: X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Lawrence Stewart , freebsd-current , Ron McDowell Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 06:31:03 -0000 On 12/27/2011 22:08, Adrian Chadd wrote: > Hi, > > Why not just list the things that sysinstall did that people like, and > extract out / reimplement those bits? That's sounds great. As soon as that's done, we can remove sysinstall from the base. Until those things exist, removing it is premature. -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 07:14:18 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65807106564A for ; Wed, 28 Dec 2011 07:14:18 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 2B8DF8FC08 for ; Wed, 28 Dec 2011 07:14:17 +0000 (UTC) Received: from [127.0.0.1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.5/8.14.5) with ESMTP id pBS6siaq035502; Tue, 27 Dec 2011 23:54:44 -0700 (MST) (envelope-from scottl@samsco.org) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: Scott Long In-Reply-To: <20111228051404.GL45484@redundancy.redundancy.org> Date: Tue, 27 Dec 2011 23:54:44 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <6F3ACDEE-B656-46D0-AB11-FF1B23E70A27@samsco.org> References: <20111227215330.GI45484@redundancy.redundancy.org> <20111227223638.GK45484@redundancy.redundancy.org> <4EFA4B4E.201@delphij.net> <20111228051404.GL45484@redundancy.redundancy.org> To: David Thiel X-Mailer: Apple Mail (2.1251.1) X-Spam-Status: No, score=-50.0 required=3.8 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org Cc: freebsd-current@freebsd.org, d@delphij.net Subject: Re: SU+J systems do not fsck themselves X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 07:14:18 -0000 On Dec 27, 2011, at 10:14 PM, David Thiel wrote: > On Tue, Dec 27, 2011 at 02:48:22PM -0800, Xin Li wrote: >>>> - use journalled fsck; - use normal fsck to check if the >>>> journalled fsck did the right thing. >=20 > Ok, here is the log of fsck with and without journal. >=20 > http://redundancy.redundancy.org/fscklog3 >=20 The first run of fsck, using the journal, gives results that I would = expect. The second run seems to imply that the fixes made on the first = run didn't actually get written to disk. This is definitely an oddity. = I see that you're using geli, maybe there's some strange side-effect = there. No idea. Report as a bug, this is definitely undesired = behavior. > That was done the very next boot, after a clean shutdown. The errors=20= > from the previous live fsck aren't there (oddly), but there are still=20= > are apparently some corrections made. The next fsck still complains, = but=20 > doesn't give any salvage prompts. >=20 > Here is jsa@'s, done on a live FS with SU+J: >=20 > http://redundancy.redundancy.org/fscklog4 >=20 For the love that is all good and holy, don't ever run fsck on a live = filesystem. It's going to report these kinds of problems! It's normal; = filesystem metadata updates stay cached in memory, and fsck bypasses = that cache. Also, what you see in your log is a file that has been = unlinked but held open. This is a common Unix idiom, and one that gets = cleaned up by fsck on reboot, whether through the SUJ intent log = processing or through a traditional fsck. > I'm not actually looking to solve my particular problem per se. The=20 > issue is that almost everyone I've checked with that's running SU+J = gets=20 > unref'd file and other errors when they check their filesystem (with = the=20 > fs live). Unless I'm missing something, a running FS should never have=20= > those kinds of errors unless you deliberately disabled fsck. >=20 Nope, you are completely incorrect here. > This leaves only a couple options: >=20 > - SU+J and fsck do not work correctly together to fix corruption on=20 > boot, i.e. bgfsck isn't getting run when it should The point of SUJ is to eliminate the need for bgfsck. Effectively, they = are exclusive ideas. It's possible that there are still problems with = SUJ and how fsck processes and commits the journal entires. However, = bgfsck has nothing to do with this, and I'd also like to know if your = use of geli is complicating the problem. > - Stuff is getting completely screwed up after boot Possibly but unlikely > - fsck is giving incorrect results Very unlikely > - I'm completely clueless about how SU+J is supposed to behave or be=20= > deployed No comment =3D-) >=20 > I'm pretty certain that the first is the issue here. It would be great=20= > if others could check their own SU+J filesystems so we could get a few=20= > more data points. >=20 Indeed, more data is needed. Scott From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 07:34:43 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE72A106566B for ; Wed, 28 Dec 2011 07:34:43 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: from redundancy.redundancy.org (75-101-96-57.dsl.static.sonic.net [75.101.96.57]) by mx1.freebsd.org (Postfix) with SMTP id 79F748FC08 for ; Wed, 28 Dec 2011 07:34:43 +0000 (UTC) Received: (qmail 85477 invoked by uid 1001); 28 Dec 2011 07:35:07 -0000 Date: Tue, 27 Dec 2011 23:35:07 -0759 From: David Thiel To: Scott Long Message-ID: <20111228073442.GM45484@redundancy.redundancy.org> References: <20111227215330.GI45484@redundancy.redundancy.org> <20111227223638.GK45484@redundancy.redundancy.org> <4EFA4B4E.201@delphij.net> <20111228051404.GL45484@redundancy.redundancy.org> <6F3ACDEE-B656-46D0-AB11-FF1B23E70A27@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6F3ACDEE-B656-46D0-AB11-FF1B23E70A27@samsco.org> X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13 X-OpenPGP-Key-available: http://redundancy.redundancy.org/lx.gpg X-Face: %H~{$1~NOw1y#%mM6{|4:/ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 07:34:43 -0000 On Tue, Dec 27, 2011 at 11:54:20PM -0700, Scott Long wrote: > The first run of fsck, using the journal, gives results that I would > expect. The second run seems to imply that the fixes made on the > first run didn't actually get written to disk. This is definitely an > oddity. I see that you're using geli, maybe there's some strange > side-effect there. No idea. Report as a bug, this is definitely > undesired behavior. Not impossible, but I was seeing similar issues on two non-geli systems as well, i.e. tons of errors fixed when doing a single-user non-journalled fsck, but journalled fsck not fixing stuff. I'll try to replicate on a test machine, as I already lost data on the last (non-geli) machine this happened to. > For the love that is all good and holy, don't ever run fsck on a live > filesystem. It's going to report these kinds of problems! It's > normal; filesystem metadata updates stay cached in memory, and fsck > bypasses that cache. Ok. I expected fsck would be softupdate-aware in that way, but I understand it not doing so. > > - SU+J and fsck do not work correctly together to fix corruption on > > boot, i.e. bgfsck isn't getting run when it should > > The point of SUJ is to eliminate the need for bgfsck. Effectively, > they are exclusive ideas. This is surprising to me. It is my impression that under Linux at least, ext3fs is checked against the journal, and gets a full e2fsck if it finds it's still dirty. Additionally, there's a periodic fsck after 180 days continuous runtime or x number of mounts (see tune2fs -i and -c). Is SU+J somehow implemented in such a way that this is unnecessary? What does it do that the ext3fs people have missed? From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 07:58:02 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21A7D106566B for ; Wed, 28 Dec 2011 07:58:02 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id E929A8FC12 for ; Wed, 28 Dec 2011 07:58:01 +0000 (UTC) Received: from [127.0.0.1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.5/8.14.5) with ESMTP id pBS7vtWN035916; Wed, 28 Dec 2011 00:57:55 -0700 (MST) (envelope-from scottl@samsco.org) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: Scott Long In-Reply-To: <20111228073442.GM45484@redundancy.redundancy.org> Date: Wed, 28 Dec 2011 00:57:55 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <9DAD04BE-D330-4DC8-9307-597834EEA2CA@samsco.org> References: <20111227215330.GI45484@redundancy.redundancy.org> <20111227223638.GK45484@redundancy.redundancy.org> <4EFA4B4E.201@delphij.net> <20111228051404.GL45484@redundancy.redundancy.org> <6F3ACDEE-B656-46D0-AB11-FF1B23E70A27@samsco.org> <20111228073442.GM45484@redundancy.redundancy.org> To: David Thiel X-Mailer: Apple Mail (2.1251.1) X-Spam-Status: No, score=-50.0 required=3.8 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org Cc: freebsd-current@freebsd.org, d@delphij.net Subject: Re: SU+J systems do not fsck themselves X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 07:58:02 -0000 On Dec 28, 2011, at 12:34 AM, David Thiel wrote: > On Tue, Dec 27, 2011 at 11:54:20PM -0700, Scott Long wrote: >> The first run of fsck, using the journal, gives results that I would=20= >> expect. The second run seems to imply that the fixes made on the=20 >> first run didn't actually get written to disk. This is definitely an=20= >> oddity. I see that you're using geli, maybe there's some strange=20 >> side-effect there. No idea. Report as a bug, this is definitely=20 >> undesired behavior. >=20 > Not impossible, but I was seeing similar issues on two non-geli = systems=20 > as well, i.e. tons of errors fixed when doing a single-user=20 > non-journalled fsck, but journalled fsck not fixing stuff. I'll try to=20= > replicate on a test machine, as I already lost data on the last=20 > (non-geli) machine this happened to. >=20 >> For the love that is all good and holy, don't ever run fsck on a live=20= >> filesystem. It's going to report these kinds of problems! It's=20 >> normal; filesystem metadata updates stay cached in memory, and fsck=20= >> bypasses that cache. =20 >=20 > Ok. I expected fsck would be softupdate-aware in that way, but I=20 > understand it not doing so. >=20 >>> - SU+J and fsck do not work correctly together to fix corruption on=20= >>> boot, i.e. bgfsck isn't getting run when it should >>=20 >> The point of SUJ is to eliminate the need for bgfsck. Effectively,=20= >> they are exclusive ideas. =20 >=20 > This is surprising to me. It is my impression that under Linux at = least,=20 > ext3fs is checked against the journal, and gets a full e2fsck if it=20 > finds it's still dirty. Additionally, there's a periodic fsck after = 180=20 > days continuous runtime or x number of mounts (see tune2fs -i and -c). = =20 > Is SU+J somehow implemented in such a way that this is unnecessary? = What=20 > does it do that the ext3fs people have missed? >=20 SUJ isn't like ext3 journaling, it doesn't do 100% metadata logging. = Instead, it's an extension of softupdates. Softupdates (SU) is still = responsible for ordering dependent writes to the disk to maintain = consistency. What SU can't handle is the Unix/POSIX idiom of unlinking = a file from the namespace but keeping its inode active through = refcounts. When you have an unclean shutdown, you wind up with stale = blocks allocated to orphaned inodes. The point of bgfsck was to scan = the filesystem for these allocations and free them, just like fsck does, = but to do it in the background so that the boot could continue. SUJ is = basically just an intent log for this case; it tells fsck where to find = these allocations so that fsck doesn't have to do the lengthy scan. = FWIW, this problem is present in most any journaling implementation and = is usually solved via the use of intent records in a journal, not unlike = SUJ. So, there's an assumption with SUJ+fsck that SU is keeping the = filesystem consistent. Maybe that's a bad assumption, and I'm not = trying to discredit your report. But the intention with SUJ is to = eliminate the need for anything more than a cursory check of the = superblocks and a processing of the SUJ intent log. If either of these = fails then fsck reverts to a traditional scan. In the same vein, ext3 = and most other traditional journaling filesystems assume that the = journal is correct and is preserving consistency, and don't do anything = more than a cursory data structure scan and journal replay as well, but = then revert to a full scan if that fails (zfs seems to be an exception = here, with there being no actual fsck available for it). As for the 180 day forced scan on ext3, I have no public comment. SU = has matured nicely over the last 10+ years, and I'm happy with the = progress that SUJ has made in the last 2-3 years. If there are bugs, = they need to be exposed and addressed ASAP. Scott From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 10:47:28 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7DCA1065675 for ; Wed, 28 Dec 2011 10:47:28 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 497678FC16 for ; Wed, 28 Dec 2011 10:47:27 +0000 (UTC) Received: by wibhr1 with SMTP id hr1so10805357wib.13 for ; Wed, 28 Dec 2011 02:47:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; bh=53NITPcuWslOHB4GG7js1a3lbSDbkFGOHjL/do/9mVY=; b=RwyxtGBu8hpHHgVhclaAtSuAGIPZhQPd+5jRisrTYiK9FYkhXp5gbAvTlh5RQngpLD cCijZH+sbunkxtI0qKX/Q6LcnlzArwyEXomrF2s32gF3IHSF1oMzs/uRdNnAJJuxPo1V ikBuC8iklVuavo7Hr5dpTZx7bbzgCAwXgm5eA= Received: by 10.180.93.193 with SMTP id cw1mr34806806wib.5.1325069247152; Wed, 28 Dec 2011 02:47:27 -0800 (PST) Received: from ernst.jennejohn.org (p578E2D1E.dip.t-dialin.net. [87.142.45.30]) by mx.google.com with ESMTPS id fq7sm31370041wbb.1.2011.12.28.02.47.25 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Dec 2011 02:47:26 -0800 (PST) Date: Wed, 28 Dec 2011 11:47:23 +0100 From: Gary Jennejohn To: Rick Macklem Message-ID: <20111228114723.3370c8a2@ernst.jennejohn.org> In-Reply-To: <2003190153.640689.1324957356113.JavaMail.root@erie.cs.uoguelph.ca> References: <2003190153.640689.1324957356113.JavaMail.root@erie.cs.uoguelph.ca> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: license question w.r.t. NFSv4.1 Layout drivers - calling all amateur lawyers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 10:47:28 -0000 On Mon, 26 Dec 2011 22:42:36 -0500 (EST) Rick Macklem wrote: > First off, I had no idea which mailing list would be appropriate > for this, so apologies in advance if I chose the wrong one. > > For NFSv4.1 pNFS, there are layout drivers in Linux that I would > like to reuse for the FreeBSD client. (Re-writing these drivers > from scratch would be a lot of work and difficult to maintain. The > Linux drivers are being actively developed with the assistance of > server vendors.) > > Two of these drivers carry a University of Michigan copyright notice > which looks pretty liberal to me. (Rather similar to MIT's copyright.) > I realize it would have to be approved by core@, but I think it could > be. (The 3rd is GPLv2'd, but that one doesn't concern me at this time. > I believe that Panasas might be able to release the code for this one > under a different license, but haven't explored this as of yet.) > > However, there is a catch... > After the copyright notice on the .c files, but not the .h files, > there is also this: > > MODULE_LICENSE("GPL"); > > and in linux/module.h, there is the following for the above: > /* > * The following license idents are currently accepted as indicating free > * software modules > * > * "GPL" [GNU Public License v2 or later] > * "GPL v2" [GNU Public License v2] > * "GPL and additional rights" [GNU Public License v2 rights and more] > * "Dual BSD/GPL" [GNU Public License v2 > * or BSD license choice] > * "Dual MIT/GPL" [GNU Public License v2 > * or MIT license choice] > * "Dual MPL/GPL" [GNU Public License v2 > * or Mozilla license choice] > * > * The following other idents are available > * > * "Proprietary" [Non free products] > * > * There are dual licensed components, but when running with Linux it is the > * GPL that is relevant so this is a non issue. Similarly LGPL linked with GPL > * is a GPL combined work. > * > * This exists for several reasons > * 1. So modinfo can show license info for users wanting to vet their setup > * is free > * 2. So the community can ignore bug reports including proprietary modules > * 3. So vendors can do likewise based on their own policies > */ > #define MODULE_LICENSE(_license) MODULE_INFO(license, _license) > > Now, from what little I know, this does not imply that the .c file is GPL'd, > since it doesn't have any GPL copyright notice in the file, nor does it #include > one via MODULE_LICENSE(). > > Does anyone happen to know if I am correct or how to confirm this? > > Thanks in advance for any help with this, rick > ps: Here's what's on the .c file, in case you're interested. The .h > files just have what is in the comment. > /* > * Module for the pnfs nfs4 file layout driver. > * Defines all I/O and Policy interface operations, plus code > * to register itself with the pNFS client. > * > * Copyright (c) 2002 > * The Regents of the University of Michigan > * All Rights Reserved > * > * Dean Hildebrand > * > * Permission is granted to use, copy, create derivative works, and > * redistribute this software and such derivative works for any purpose, > * so long as the name of the University of Michigan is not used in > * any advertising or publicity pertaining to the use or distribution > * of this software without specific, written prior authorization. If > * the above copyright notice or any other identification of the > * University of Michigan is included in any copy of any portion of > * this software, then the disclaimer below must also be included. > * > * This software is provided as is, without representation or warranty > * of any kind either express or implied, including without limitation > * the implied warranties of merchantability, fitness for a particular > * purpose, or noninfringement. The Regents of the University of > * Michigan shall not be liable for any damages, including special, > * indirect, incidental, or consequential damages, with respect to any > * claim arising out of or in connection with the use of the software, > * even if it has been or is hereafter advised of the possibility of > * such damages. > */ > > #include > #include > #include > > #include "internal.h" > #include "nfs4filelayout.h" > > #define NFSDBG_FACILITY NFSDBG_PNFS_LD > > MODULE_LICENSE("GPL"); > MODULE_AUTHOR("Dean Hildebrand "); > MODULE_DESCRIPTION("The NFSv4 file layout driver"); > IANAL but IMO the university copyriught notice takes precedence over the MODULE_LICENSE(), which is basically there so that the in-kernel linker won't brand the result of loading this module as "tainted." This is based on 10 years of doing embedded Linux work and encountering this "problem" myself. -- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 10:48:37 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 075C0106566B; Wed, 28 Dec 2011 10:48:37 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 9F01E8FC18; Wed, 28 Dec 2011 10:48:36 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1Rfr3j-0008HZ-Fn>; Wed, 28 Dec 2011 11:48:35 +0100 Received: from e178027189.adsl.alicedsl.de ([85.178.27.189] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1Rfr3j-0000HI-9A>; Wed, 28 Dec 2011 11:48:35 +0100 Message-ID: <4EFAF3FC.60002@zedat.fu-berlin.de> Date: Wed, 28 Dec 2011 11:48:28 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Current FreeBSD , Ports FreeBSD X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6A8E02CD4CCBF754D277C977" X-Originating-IP: 85.178.27.189 Cc: Subject: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 10:48:37 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6A8E02CD4CCBF754D277C977 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hello out here. I run into a problem since one of the last portupdates and I do not know whether this has to do with binutils or gcc46 or even FreeBSD 9.0/10.0 AMD64. Background: We use a scientific graphical toolset for planetary research called ISIS3, which is provided by the USGS. We patched ISIS3 to run on FreeBSD 8/9/10 so far and it ran well with FreeBSD 8.2-STABLE and 9.0-PRE a couple of weeks ago. On all of my boxes, I do frequently a portupgrade, so I saw binutils got bumped up and gcc 4.6 is also getting really frequently changed these day= s. After a some portupdates within the last weeks, I just decided to compile ISIS3 again to keep it "fresh and on track", but it won't compile anymore. On all FreeBSD 9.0-PRERELEASE and FreeBSD 10.0-CURRENT (all AMD64 and CLANG built) I receive in some subfolders containing sources the follwoing error: [...] Adding API object [UniqueIOCachingAlgorithm] Adding API object [UniversalGroundMap] Adding API object [UserInterface] Adding API object [VariableLineScanCameraDetectorMap] Adding API object [VecFilter] Adding API object [WorldMapper] Adding API object [iException] Adding API object [iString] Adding API object [iTime] Working on Package [mex] (11:30:15) Adding API object [HrscCamera] /usr/local/bin/ld: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a(functexcept.o): relocation R_X86_64_32 against `std::bad_exception::~bad_exception()' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a: could not read symbols: Bad value collect2: ld returned 1 exit status gmake[5]: *** [plugin] Error 1 cp: libHrscCamera.so: No such file or directory gmake[4]: *** [install] Error 1 Working on Package [control] (11:30:15) Adding API object [BundleAdjust] Adding API object [ControlCubeGraphNode] Adding API object [ControlGraph] Adding API object [ControlMeasure] Adding API object [ControlMeasureLogData] Adding API object [ControlNet] Adding API object [ControlNetFilter] Adding API object [ControlNetStatistics] Adding API object [ControlNetValidMeasure] Adding API object [ControlNetVersioner] Adding API object [ControlPoint] Adding API object [ControlPointList] Adding API object [InterestOperator] Adding API object [InterestOperatorFactory] Working on Package [lro] (11:30:22) Adding API object [LroNarrowAngleCamera] /usr/local/bin/ld: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a(functexcept.o): relocation R_X86_64_32 against `std::bad_exception::~bad_exception()' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a: could not read symbols: Bad value collect2: ld returned 1 exit status gmake[5]: *** [plugin] Error 1 cp: libLroNarrowAngleCamera.so: No such file or directory gmake[4]: *** [install] Error 1 Adding API object [LroWideAngleCamera] /usr/local/bin/ld: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a(functexcept.o): relocation R_X86_64_32 against `std::bad_exception::~bad_exception()' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a: could not read symbols: Bad value collect2: ld returned 1 exit status gmake[5]: *** [plugin] Error 1 cp: libLroWideAngleCamera.so: No such file or directory gmake[4]: *** [install] Error 1 Adding API object [MiniRF] [...] Working on Package [system] (11:30:32) Adding API object [KernelDb] Working on Package [viking] (11:30:33) Adding API object [VikingCamera] /usr/local/bin/ld: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a(ios_init.o): relocation R_X86_64_32 against `std::cout' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a: could not read symbols: Bad value collect2: ld returned 1 exit status gmake[5]: *** [plugin] Error 1 cp: libVikingCamera.so: No such file or directory gmake[4]: *** [install] Error 1 Working on Package [rolo] (11:30:33) Finished adding API objects Creating Shared Libraries ... /usr/local/bin/ld: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a(ctype.o): relocation R_X86_64_32S against `vtable for std::ctype' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a: could not read symbols: Bad value collect2: ld returned 1 exit status gmake[1]: *** [libisis3.3.0.so] Error 1 gmake: *** [api] Error 2 *** Error code 1 Stop in /usr/ports/science/isis3. #>: I try to figure out what changed in the Mk-framework causing this problem recently, since the code compiled weeks ago on 9.0-PRE and 10.0-CUR without a problem. Well, I also looked into compile options for the code. They are set by a archaic script mechanism (USGS doesn't provide a more modern way of build environment and they are very, very Linux-restricted and not "open"). All compile options are set via a central framework of scripts and even the linker options get set in such a way. Well, I saw such an error often when a static library got confused with a dynamical library, correct me please, I'm not very firm in this stuff y= et. I won't provide at this stage my silly port to the public since it is not bright and shiny yet, so excuse please the lack of more information. Perhaps the above error is common and can be fixed. I'm glad to read some hints and thanks in advance, Oliver --------------enig6A8E02CD4CCBF754D277C977 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO+vQCAAoJEOgBcD7A/5N8NtQH+wXQFSGcwToNt1yqnWOSK6d9 vbkRwqOgt+WzSMG380nqtmQs0x0Lyz9bT/of12CxDa8Ym4keDOSm7VUTrlGWT+E4 pHV5og6RlO5gmxHwaQJjtJ4x9UHsMGOSzjQOTC6RmgQD5tEv8KNhQtA0mcFndh0H 3DuWjjPVHc0YAq5cF8VoBXgvtj0yV5E0v8odvHeeVhFn3OVFk5OqnLk0kBUt9gYw BHHfkhYvHA0aXqPb56hHv3HxnKDJwOImwQzK+crYmsQ2VhCZIrV4wayDmwPelrGr PYdHUbTbCCSYQCv6mwYslWo9gDKeKfkVS8xoq3iSp59oZrGfFAzJLGDhJImEGPA= =NvN6 -----END PGP SIGNATURE----- --------------enig6A8E02CD4CCBF754D277C977-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 13:25:14 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 897BC106566C; Wed, 28 Dec 2011 13:25:14 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 175A88FC15; Wed, 28 Dec 2011 13:25:13 +0000 (UTC) Received: from vhoffman-macbooklocal.local ([10.10.10.20]) (authenticated bits=0) by unsane.co.uk (8.14.4/8.14.4) with ESMTP id pBSDPBuF050186 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 28 Dec 2011 13:25:12 GMT (envelope-from vince@unsane.co.uk) Message-ID: <4EFB18B7.8050207@unsane.co.uk> Date: Wed, 28 Dec 2011 13:25:11 +0000 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Doug Barton References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> <4EF9B09A.4070103@freebsd.org> <4EFA1C9C.60601@FreeBSD.org> <4EFA7FD4.10600@freebsd.org> <4EFA8E01.6050101@FreeBSD.org> <4EFAB788.2040508@FreeBSD.org> In-Reply-To: <4EFAB788.2040508@FreeBSD.org> X-Enigmail-Version: 1.3.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Lawrence Stewart , Adrian Chadd , freebsd-current , Ron McDowell Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 13:25:14 -0000 On 28/12/2011 06:30, Doug Barton wrote: > On 12/27/2011 22:08, Adrian Chadd wrote: >> Hi, >> >> Why not just list the things that sysinstall did that people like, and >> extract out / reimplement those bits? > That's sounds great. As soon as that's done, we can remove sysinstall > from the base. Until those things exist, removing it is premature. > In that case can I suggest a wiki page or other viewable/editable list of desirable features from sysinstall? I only used it for the basic disklayout and component install so I'm not in a position to start it off or I would. Vince From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 13:58:17 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E69E91065673 for ; Wed, 28 Dec 2011 13:58:16 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 68A198FC13 for ; Wed, 28 Dec 2011 13:58:16 +0000 (UTC) Received: from alf.home (alf.kiev.zoral.com.ua [10.1.1.177]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id pBSDw8WR099151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Dec 2011 15:58:08 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from alf.home (kostik@localhost [127.0.0.1]) by alf.home (8.14.5/8.14.5) with ESMTP id pBSDw86M008261; Wed, 28 Dec 2011 15:58:08 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by alf.home (8.14.5/8.14.5/Submit) id pBSDw8Es008260; Wed, 28 Dec 2011 15:58:08 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: alf.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 28 Dec 2011 15:58:08 +0200 From: Kostik Belousov To: "O. Hartmann" Message-ID: <20111228135808.GW50300@deviant.kiev.zoral.com.ua> References: <4EFAF3FC.60002@zedat.fu-berlin.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Rfkum36+UScbsJHk" Content-Disposition: inline In-Reply-To: <4EFAF3FC.60002@zedat.fu-berlin.de> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Current FreeBSD , Ports FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 13:58:17 -0000 --Rfkum36+UScbsJHk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote: > Hello out here. >=20 > I run into a problem since one of the last portupdates and I do not know > whether this has to do with binutils or gcc46 or even FreeBSD 9.0/10.0 > AMD64. >=20 > Background: > We use a scientific graphical toolset for planetary research called > ISIS3, which is provided by the USGS. We patched ISIS3 to run on FreeBSD > 8/9/10 so far and it ran well with FreeBSD 8.2-STABLE and 9.0-PRE a > couple of weeks ago. > On all of my boxes, I do frequently a portupgrade, so I saw binutils got > bumped up and gcc 4.6 is also getting really frequently changed these day= s. > After a some portupdates within the last weeks, I just decided to > compile ISIS3 again to keep it "fresh and on track", but it won't > compile anymore. >=20 > On all FreeBSD 9.0-PRERELEASE and FreeBSD 10.0-CURRENT (all AMD64 and > CLANG built) I receive in some subfolders containing sources the > follwoing error: >=20 > [...] > Adding API object [UniqueIOCachingAlgorithm] > Adding API object [UniversalGroundMap] > Adding API object [UserInterface] > Adding API object [VariableLineScanCameraDetectorMap] > Adding API object [VecFilter] > Adding API object [WorldMapper] > Adding API object [iException] > Adding API object [iString] > Adding API object [iTime] > Working on Package [mex] (11:30:15) > Adding API object [HrscCamera] > /usr/local/bin/ld: > /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a(functexcept.o): > relocation R_X86_64_32 against `std::bad_exception::~bad_exception()' > can not be used when making a shared object; recompile with -fPIC > /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc= ++.a: > could not read symbols: Bad value > collect2: ld returned 1 exit status > gmake[5]: *** [plugin] Error 1 > cp: libHrscCamera.so: No such file or directory > gmake[4]: *** [install] Error 1 The error is completely clear as it is: the build tries to link static library libstdc++.so into shared object. This is not supported. --Rfkum36+UScbsJHk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk77IG8ACgkQC3+MBN1Mb4gDEQCfWOoZNIAO6Y553SuFbxq784fp KeMAniadnwi1Vcx5mv9jA3k9ALzRK75V =+Yxf -----END PGP SIGNATURE----- --Rfkum36+UScbsJHk-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 14:10:14 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4ECF71065675; Wed, 28 Dec 2011 14:10:14 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 027E08FC14; Wed, 28 Dec 2011 14:10:13 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1RfuCq-0005I7-Un>; Wed, 28 Dec 2011 15:10:13 +0100 Received: from e178027189.adsl.alicedsl.de ([85.178.27.189] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1RfuCq-0001Xl-PY>; Wed, 28 Dec 2011 15:10:12 +0100 Message-ID: <4EFB2344.3000302@zedat.fu-berlin.de> Date: Wed, 28 Dec 2011 15:10:12 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Kostik Belousov References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> In-Reply-To: <20111228135808.GW50300@deviant.kiev.zoral.com.ua> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0297CE99AF91EBDA30C23244" X-Originating-IP: 85.178.27.189 Cc: Current FreeBSD , Ports FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 14:10:14 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0297CE99AF91EBDA30C23244 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 12/28/11 14:58, schrieb Kostik Belousov: > On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote: >> Hello out here. >> >> I run into a problem since one of the last portupdates and I do not kn= ow >> whether this has to do with binutils or gcc46 or even FreeBSD 9.0/10.0= >> AMD64. >> >> Background: >> We use a scientific graphical toolset for planetary research called >> ISIS3, which is provided by the USGS. We patched ISIS3 to run on FreeB= SD >> 8/9/10 so far and it ran well with FreeBSD 8.2-STABLE and 9.0-PRE a >> couple of weeks ago. >> On all of my boxes, I do frequently a portupgrade, so I saw binutils g= ot >> bumped up and gcc 4.6 is also getting really frequently changed these = days. >> After a some portupdates within the last weeks, I just decided to >> compile ISIS3 again to keep it "fresh and on track", but it won't >> compile anymore. >> >> On all FreeBSD 9.0-PRERELEASE and FreeBSD 10.0-CURRENT (all AMD64 and >> CLANG built) I receive in some subfolders containing sources the >> follwoing error: >> >> [...] >> Adding API object [UniqueIOCachingAlgorithm] >> Adding API object [UniversalGroundMap] >> Adding API object [UserInterface] >> Adding API object [VariableLineScanCameraDetectorMap] >> Adding API object [VecFilter] >> Adding API object [WorldMapper] >> Adding API object [iException] >> Adding API object [iString] >> Adding API object [iTime] >> Working on Package [mex] (11:30:15) >> Adding API object [HrscCamera] >> /usr/local/bin/ld: >> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libs= tdc++.a(functexcept.o): >> relocation R_X86_64_32 against `std::bad_exception::~bad_exception()' >> can not be used when making a shared object; recompile with -fPIC >> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libs= tdc++.a: >> could not read symbols: Bad value >> collect2: ld returned 1 exit status >> gmake[5]: *** [plugin] Error 1 >> cp: libHrscCamera.so: No such file or directory >> gmake[4]: *** [install] Error 1 > The error is completely clear as it is: the build tries to link static > library libstdc++.so into shared object. This is not supported. Thanks, Kostik, for the fast response. The error isn't so clear to me, sorry. I thought libstdc++.a is the static library and it is taken to be referenced/compiled into a shared object created by the application I try to compile. I'm much more confused now, since I thought the last time I compiled that piece of software, I never got any error like that. Well, clang fails with some obscure errors on the code itself and I'm unwilling to correct them, I'll try the legacy gcc 4.2.1 and will report what's happening. Thank you very much, Oliver --------------enig0297CE99AF91EBDA30C23244 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO+yNEAAoJEOgBcD7A/5N8LdUH/jsP/Tc7ny/CrV3Uv98ovYbU udKfvA30SEACLKax4w6kp8K4sdZLJOMouHO5Qd/mulnXPQfrhE1Lqg68sJpuTNmP HQusAUDjoBZRF7LmSnoRGjExJNjhU4YGeGVYzhp71fBgIl/8DErS5u4/qrSF2wkc ZgNt1n5etLq/reFiN6K1CRZCgs+8V8zv13xRDPWjLjA9VkFWbEzXcNXLm9pWhZYu V0HAYFkmvyQIHFM+ooMOxZ5fSiG3rrnaTDmz9tvCm6kIN/r8Y4GicaljGn5efQwv X3C4p7DM6lEtBaq0xe1b9ACuOPzeONzL+MM+dUgYoavuxXkRKj8ksdhXUos13/A= =l8eV -----END PGP SIGNATURE----- --------------enig0297CE99AF91EBDA30C23244-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 14:26:00 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F18C5106564A for ; Wed, 28 Dec 2011 14:26:00 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 6B3148FC12 for ; Wed, 28 Dec 2011 14:26:00 +0000 (UTC) Received: from outgoing.leidinger.net (p4FC41A17.dip.t-dialin.net [79.196.26.23]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 5A99184400D; Wed, 28 Dec 2011 15:25:44 +0100 (CET) Received: from localhost (unknown [85.94.224.20]) by outgoing.leidinger.net (Postfix) with ESMTPSA id B130251FB; Wed, 28 Dec 2011 15:25:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1325082341; bh=PAgEIOmi1KRJz1Hf+ZIIs0L5yA9AI83fpHHUTZ12mGI=; h=Date:Subject:Message-ID:From:To:Cc:MIME-Version:Content-Type; b=aa36BiFb6i1l8ouUxnfhVO9BZ0tmPqd3rXcvTe8OjAEOhOB2uXqaxR6M48FGYe5nV HNmbm7BN8PL1tnXOsA74FYfSDe1sJWOP3U5hVY7Cvg4FtUgbXNO2BiOZquOvGg6oun SIvt9qZZJKXRJx5SCiwVnphh37lvLldZIk/g0kvhyVEI7z8pTu8epqJBnJVf1v6UNo xOXJ2cXLQ1wpfvoCA05VNs0KwNC6UKlsBz/23iOd1H0gzgJi31y3u3YQIIhb1ZV4nS OyDVMuDZkXNNliqa/BPnMotZnJk4FFQ5kGDPJyHSWSeyve+Dfehshia7ThSaN55jp8 5dOBS+xDec1zw== Date: Wed, 28 Dec 2011 15:24:39 +0100 Message-ID: <9sn6eev7rlv8kylsdufdw3mh.1325082279096@email.android.com> Importance: normal From: Alexander Leidinger To: ohartman@mail.zedat.fu-berlin.de, arundel@freebsd.org MIME-Version: 1.0 X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 5A99184400D.A173A X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=1.401, required 6, autolearn=disabled, ALL_TRUSTED -1.00, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, HTML_MESSAGE 0.00, SARE_ADLTSUB4 2.50) X-EBL-MailScanner-SpamScore: s X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1325687145.67627@dvj8hte+1N5hLApnTW1Wyg X-EBL-Spam-Status: No Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Linuxulator (was: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 14:26:01 -0000 CkhpLAoKeW91IGFzc3VtZSBpbiB5b3VyIGNvbW1lbnQgdGhhdCBkZXZlbG9wbWVudCB0aW1lICJ3 YXN0ZWQiIGluIHRoZSBsaW51eHVsYXRvciBpcyB0aW1lIGxvc3QgZm9yIG90aGVyIGRldmVsb3Bt ZW50LiBUaGlzIGFzc3VtcHRpb24gY291bGQgYmUgdmFsaWQgZm9yIGEgY29tbWVyY2lhbGx5IGRl dmVsb3BlZCBPUywgYnV0IGlzIHdyb25nIGZvciBGcmVlQlNELiBJIHRlbGwgdGhpcyBhcyBhIHBl cnNvbiB3aG8gc3BlbmQgYSBsb3Qgb2YgdGltZSB3aXRoIHRoZSBsaW51eCBwb3J0cywgbWVudG9y ZWQgYSBHU29DIHN0dWRlbnQgd2hvIHdvcmtlZCBvbiB0aGUgbGludXh1bGF0b3IgYW5kIGFsc28g cHV0IHNvbWUgdGltZSBpbnRvIHRoZSBrZXJuZWwgcGFydHMuCgpUaGUgdXNlIGNhc2UgZm9yIGl0 IGlzOiBydW4gbGludXggcHJvZ3JhbXMgd2hpY2ggYXJlIG5vdCBhdmFpbGFibGUgd2l0aCBzb3Vy Y2Ugb3Igd2hlcmUgIndlIiBhcmUgbm90IGFibGUgdG8gZ2V0IGl0IGNvbXBpbGVkIG9uIEZyZWVC U0Qgd2l0aCBhIHJlYXNvbmFibGUgZWZmb3J0LiBBcyBhIGRhdGEgcG9pbnQsICJ3ZSIgbWFuYWdl ZCBpbiB0aGUgcGFzdCB0byB0YWtlIHRoZSBjbG9zZWQgc291cmNlIGxpbnV4IHZlcnNpb24gb2Yg dGhlIEludGVsIEMvQysrIGNvbXBpbGVyIGFuZCBtYW5pcHVsYXRlIGl0IGluIGEgd2F5IHRvIHJ1 biBpbiB0aGUgbGludXh1bGF0b3IgYnV0IHByb2R1Y2UgRnJlZUJTRCBiaW5hcmllcy4gSSBnb3Qg cmVwb3J0cyB0aGF0IGl0IHdhcyB1c2VkIGluIHNvbWUgSFBDIHNjZW5hcmlvcy4KCldhc24ndCBp dCB5b3Ugd2hvIGFza2VkIGlmIHRoZXJlJ3MgYSB3YXkgdG8gcnVuIENVREEgb24gRnJlZUJTRD8g UGVzc2ltaXN0aWMgYnV0IGludGVyZXN0ZWQgc291bHMgd291bGQgbm90IHdhaXQgdW50aWwgdGhl cmUgaXMgbWF5YmUgc29tZSByZXN1bHQgZnJvbSBvcGVuIHNvdXJjaW5nIHRoZSBudmlkaWEgY29t cGlsZXIgYW5kIGluc3RlYWQgZWl0aGVyIHRyeSB0byBnZXQgc29tZXRoaW5nIHNpbWlsYXIgdXAg YW5kIHJ1bm5pbmcsIG9yIHRvIGdldCBhIDY0IGJpdCB2ZXJzaW9uIG9mIHRoZSBsaW51eHVsYXRv ci4gVGhlIGxhdGVyIG9uZSBtYXkgYmUgbW9yZSBiZW5lZmljaWFsIGZvciBtb3JlIHBlb3BsZSwg YW5kIG1heSBldmVuIG1vcmUgZWFzeSBhcyB0aGUgcGFydHMgYXJlIG9wZW4gc291cmNlIGFuZCB0 aGVyZSdzIGV2ZW4gc29tZSBjb2RlIHNvbWV3aGVyZSBpbiBhIFZDUyAobWF5YmUgaW4gcGVyZm9y Y2UpLgoKQnllLApBbGV4YW5kZXIuCgotLSAKU2VuZCB2aWEgYW4gQW5kcm9pZCBkZXZpY2UsIHBs ZWFzZSBmb3JnaXZlIGJyZXZpdHkgYW5kIHR5cG9ncmFwaGljIGFuZCBzcGVsbGluZyBlcnJvcnMu IAoKIk8uIEhhcnRtYW5uIiA8b2hhcnRtYW5AbWFpbC56ZWRhdC5mdS1iZXJsaW4uZGU+IGhhdCBn ZXNjaHJpZWJlbjpPbiAxMi8yMy8xMSAxMjo0NCwgQWxleGFuZGVyIEJlc3Qgd3JvdGU6ClsuLi5d Cj4+IE1hbnkgc3VnZ2VzdGVkIHRoYXQgdGhlIExpbnV4IGJpbmFyaWVzIGJlIHJ1biB2aWEgdGhl IEZyZWVCU0QgTGludXggCj4+IGVtdWxhdGlvbi4gVW5jaGFuZ2VkLgo+PiBUaGVyZSBpcyBvbmUg cHJvYmxlbSBoZXJlIHRob3VnaCwgdGhlIGVtdWxhdGlvbiBpcyBzdGlsbCAzMiBiaXQuCj4gCj4g cGx1cyB0aGUgY3VycmVudCBlbXVsYXRpb24gbGF5ZXIgaXMgZmFyIGZyb20gY29tcGxldGUuIGEg bG90IG9mIHN0dWZmIGhhc24ndAo+IGJlZW4gaW1wbGVtZW50ZWQgeWV0IChtZWFuaW5nIGl0J3Mg bWlzc2luZyBvciBpbXBsZW1lbnRlZCBhcyBkdW1teSBjb2RlKS4KPiAKPiB0cnkgcnVubmluZyBy ZWNlbnQgZmlyZWZveCBsaW51eCBiaW5hcmllcyBvbiBmcmVlYnNkLiB0aGV5IHdpbGwgYWxsIGNy YXNoCj4gYWxtb3N0IGluc3RhbnRseS4KPiAKPiBjaGVlcnMuCj4gYWxleAo+IAoKWy4uLl0KClNv bWV0aW1lcyBJJ20gZ2xhZCB0byBoYXZlIHRoZSBMaW51eHVsYXRvciwgZm9yIGluc3RhbmNlIHVz aW5nCk1hdGhlbWF0aWNhIG9yIGFuIG9sZGVyIDMyYml0IElETCBvciBldmVuIE1BVExBQi4gQnV0 IGxhdGVseSwgSSBydW4gaW50bwpwcm9ibGVtcyBvbiBtb3JlIHJlY2VudCBwbGF0Zm9ybXMgbGlr ZSBGcmVlQlNEIDkgYW5kIDEwLgoKVGhlcmUgbWF5YmUgc2VyaW91cyByZWFzb25zIGhhdmluZyB0 aGUgTGludXh1bGF0b3IsIGkgZG8gbm90IGtub3cuIEJ1dAppZiBub3QsIHdoeSBzcGVuZGluZyBy YXJlIGRldmVsb3BlciByZXNvdXJjZXMgb24gdGhhdD8gQXMgZmFyIGFzIEknbQpjb25jZXJuZWQs IHRoZSBvbmx5IHJlYWwgcmVhc29uIGhhdmluZyB0aGUgTGludXh1bGF0b3IgaXMgc29tZSBzdHVm Zgpmcm9tIEFkb2JlIGZvciBkZXNrdG9wIHN5c3RlbXMsIEZsYXNoLiBUaGF0J3MgaXQuCkZvciB0 aGUgc2NpZW50aWZpYyBzdHVmZiwgSSB0cnkgdG8gbW92ZSBteSBwZW9wbGUgdG93YXJkcyBPcGVu U291cmNlLApzaW5jZSB3ZSBkbyAic3RhbmRhcmQiIHN0dWZmIGFuZCBJIGV4cGVjdCBzdHVkZW50 cyBhbmQgc2NpZW50aXN0cwpzb2x2aW5nIHByb2JsZW1zIHdpdGhvdXQgZmFuY3kgY29sb3VyZWQg Y2xpY2t5IGZ1bm55IHRoaW5ncy4gSW4KInByb2R1Y3Rpb24iLCB0aGlzIG1pZ2h0IGJlIGFub3Ro ZXIgcG9pbnQgb2Ygdmlldy4gU2NpTGFiIGZyb20gSU5SSUEgaXMKZ3JlYXQsIE11UEFELCBNQVhJ TUEgYWxzby4KCgpCdXQgaXMgdGhlcmUgYSByZWFsIG5lZWQgcnVubmluZyB0aGUgTGludXggYmlu YXJ5IG9mIEZvcmVmb3ggb24gRnJlZUJTRD8KClJlZ2FyZHMsCk9saXZlcgoK From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 14:30:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56724106564A; Wed, 28 Dec 2011 14:30:03 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 9002F8FC13; Wed, 28 Dec 2011 14:30:02 +0000 (UTC) Received: from alf.home (alf.kiev.zoral.com.ua [10.1.1.177]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id pBSETw2I001379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Dec 2011 16:29:58 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from alf.home (kostik@localhost [127.0.0.1]) by alf.home (8.14.5/8.14.5) with ESMTP id pBSETwj9008368; Wed, 28 Dec 2011 16:29:58 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by alf.home (8.14.5/8.14.5/Submit) id pBSETvPr008367; Wed, 28 Dec 2011 16:29:57 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: alf.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 28 Dec 2011 16:29:57 +0200 From: Kostik Belousov To: "O. Hartmann" Message-ID: <20111228142957.GX50300@deviant.kiev.zoral.com.ua> References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M6R/iNHleSlW4Gwu" Content-Disposition: inline In-Reply-To: <4EFB2344.3000302@zedat.fu-berlin.de> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Current FreeBSD , Ports FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 14:30:03 -0000 --M6R/iNHleSlW4Gwu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 28, 2011 at 03:10:12PM +0100, O. Hartmann wrote: > Am 12/28/11 14:58, schrieb Kostik Belousov: > > On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote: > >> Hello out here. > >> > >> I run into a problem since one of the last portupdates and I do not kn= ow > >> whether this has to do with binutils or gcc46 or even FreeBSD 9.0/10.0 > >> AMD64. > >> > >> Background: > >> We use a scientific graphical toolset for planetary research called > >> ISIS3, which is provided by the USGS. We patched ISIS3 to run on FreeB= SD > >> 8/9/10 so far and it ran well with FreeBSD 8.2-STABLE and 9.0-PRE a > >> couple of weeks ago. > >> On all of my boxes, I do frequently a portupgrade, so I saw binutils g= ot > >> bumped up and gcc 4.6 is also getting really frequently changed these = days. > >> After a some portupdates within the last weeks, I just decided to > >> compile ISIS3 again to keep it "fresh and on track", but it won't > >> compile anymore. > >> > >> On all FreeBSD 9.0-PRERELEASE and FreeBSD 10.0-CURRENT (all AMD64 and > >> CLANG built) I receive in some subfolders containing sources the > >> follwoing error: > >> > >> [...] > >> Adding API object [UniqueIOCachingAlgorithm] > >> Adding API object [UniversalGroundMap] > >> Adding API object [UserInterface] > >> Adding API object [VariableLineScanCameraDetectorMap] > >> Adding API object [VecFilter] > >> Adding API object [WorldMapper] > >> Adding API object [iException] > >> Adding API object [iString] > >> Adding API object [iTime] > >> Working on Package [mex] (11:30:15) > >> Adding API object [HrscCamera] > >> /usr/local/bin/ld: > >> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libs= tdc++.a(functexcept.o): > >> relocation R_X86_64_32 against `std::bad_exception::~bad_exception()' > >> can not be used when making a shared object; recompile with -fPIC > >> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libs= tdc++.a: > >> could not read symbols: Bad value > >> collect2: ld returned 1 exit status > >> gmake[5]: *** [plugin] Error 1 > >> cp: libHrscCamera.so: No such file or directory > >> gmake[4]: *** [install] Error 1 > > The error is completely clear as it is: the build tries to link static > > library libstdc++.so into shared object. This is not supported. >=20 > Thanks, Kostik, for the fast response. > The error isn't so clear to me, sorry. I thought libstdc++.a is the > static library and it is taken to be referenced/compiled into a shared Linked in. > object created by the application I try to compile. Right, and this is not supported. Code linked into shared object must be compiled PIC. An .a library usually does not contain objects compiled by PIC, ld just dutifully reported back. >=20 > I'm much more confused now, since I thought the last time I compiled > that piece of software, I never got any error like that. Well, clang > fails with some obscure errors on the code itself and I'm unwilling to > correct them, I'll try the legacy gcc 4.2.1 and will report what's > happening. It might have worked by accident (because libstdc++.a objects referenced=20 during the link did not carried unsupported relocations), or, much more likely, the build system has changed and started doing stupid things. It must not link static libraries into shared objects. You should examine why it does this, and fix it. Changing compilers is just wasting a time. --M6R/iNHleSlW4Gwu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk77J+UACgkQC3+MBN1Mb4jLqACgqmZ+kfdT2b/UZ3LSXK9oQOpA siQAoPZuCMqkkDqFz90xGH3vZpBXSXTA =dv5v -----END PGP SIGNATURE----- --M6R/iNHleSlW4Gwu-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 15:17:25 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC2AF1065673; Wed, 28 Dec 2011 15:17:25 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 6F80D8FC13; Wed, 28 Dec 2011 15:17:25 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1RfvFs-0005D0-F2>; Wed, 28 Dec 2011 16:17:24 +0100 Received: from e178027189.adsl.alicedsl.de ([85.178.27.189] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1RfvFs-0004hi-8X>; Wed, 28 Dec 2011 16:17:24 +0100 Message-ID: <4EFB3303.2000002@zedat.fu-berlin.de> Date: Wed, 28 Dec 2011 16:17:23 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Alexander Leidinger References: <9sn6eev7rlv8kylsdufdw3mh.1325082279096@email.android.com> In-Reply-To: <9sn6eev7rlv8kylsdufdw3mh.1325082279096@email.android.com> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig733EC6496B9A2087F8292378" X-Originating-IP: 85.178.27.189 Cc: arundel@freebsd.org, freebsd-performance@freebsd.org, freebsd-current@freebsd.org Subject: Re: Linuxulator (was: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 15:17:25 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig733EC6496B9A2087F8292378 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 12/28/11 15:24, schrieb Alexander Leidinger: >=20 > Hi, >=20 > you assume in your comment that development time "wasted" in the > linuxulator is time lost for other development. This assumption could b= e > valid for a commercially developed OS, but is wrong for FreeBSD. I tell= > this as a person who spend a lot of time with the linux ports, mentored= > a GSoC student who worked on the linuxulator and also put some time int= o > the kernel parts. That wasn't ment to be any offense! And shortly after I wrote this, i remembered myself that many stuff from JAVA is still completely not open due to Linux-shielded/protected stuff. Even commercial companies like DeLL seem to be incabale of offering JAVA apllets which are compatible to all platforms. I tried hard on geting their iDRAC6 stuff running on FreeBSD and recent firefox or even with diablo-jdk as a standalone JAVA application, but it lacks obviously some functionality only available in Linux firefox and/or JAVA. >=20 > The use case for it is: run linux programs which are not available with= > source or where "we" are not able to get it compiled on FreeBSD with a > reasonable effort. As a data point, "we" managed in the past to take th= e > closed source linux version of the Intel C/C++ compiler and manipulate > it in a way to run in the linuxulator but produce FreeBSD binaries. I > got reports that it was used in some HPC scenarios. Yes, you're right. We also used the Intel C and Fortran compiler to run a lot of scientifc programs on some boxes, but noadays, most software, especially scientific one, is 64bit since we deal with huge datasets which need a lot of memory and/or are happy having no memory limitations doing n-body simulations. But this is times ago. I'm sure there are still applications running 32bit, but the benefit of having 64bit and so a native 64bit compiler is quite huge. >=20 > Wasn't it you who asked if there's a way to run CUDA on FreeBSD? > Pessimistic but interested souls would not wait until there is maybe > some result from open sourcing the nvidia compiler and instead either > try to get something similar up and running, or to get a 64 bit version= > of the linuxulator. The later one may be more beneficial for more > people, and may even more easy as the parts are open source and there's= > even some code somewhere in a VCS (maybe in perforce). Yes, it was me who asked for a 32Bit CUDA solution, because I desperately needed OpenCL/CUDA. And I asked because I wouldn't like to leave my FreeBSD platform for achiving this, but I do not have any chance. I tried to get the CUDA stuff working on FreeBSD, but it would take me ages to fullfill and at the end I need a development environment. The BLOG mentioned and referred to achive this is quite old and outdated and also stated that one need either a full Linux installation (Gentoo) or an development box. Well, having a development box menas also having a full working Linux that could be 64bit and running my applications. It is now that way. We use Suse 11 and Ubuntu 10 boxes with TESLA boards from nVidia and I have to compile my stuff and run it on those boxes. I also administer one of such boxes and I must confress, that I'm not happy with that. For once, it might be a personal thing, on the other hand I feel lost on such cryptographic and shell-polluted administrative environments, which could only be administered by special scripted tools - and each Linux distribution seems to have its own, holy and mystical way to encrypt former clean administrative ways to do. Days ago nVidia and AMD claimed to have opened their OpenCL intermediate language/representation and and nVidia claims to have opensourced their compiler. But althought requested being "member" of the elite group of people having access to that piece of software, I did not get access to it. So, it seems not to be real opensourced. But I think this might be a topic of another thread, which would be very interesting to me to discuss, since I'm not that familiar with what is possible in FreeBSD and what not. I see that, from the theoretical perspective of how LLVM works, their could be a chance to get FreeBSD on par with Linux in GPGPU concerned applications, which becomes very, very important now. >=20 > Bye, > Alexander. Regards, Oliver >=20 > --=20 > Send via an Android device, please forgive brevity and typographic and > spelling errors. >=20 >=20 > "O. Hartmann" hat geschrieben: > On 12/23/11 12:44, Alexander Best wrote: > [...] >>> Many suggested that the Linux binaries be run via the FreeBSD Linux >>> emulation. Unchanged. >>> There is one problem here though, the emulation is still 32 bit. >> >> plus the current emulation layer is far from complete. a lot of stuff > hasn't >> been implemented yet (meaning it's missing or implemented as dummy cod= e). >> >> try running recent firefox linux binaries on freebsd. they will all cr= ash >> almost instantly. >> >> cheers. >> alex >> >=20 > [...] >=20 > Sometimes I'm glad to have the Linuxulator, for instance using > Mathematica or an older 32bit IDL or even MATLAB. But lately, I run int= o > problems on more recent platforms like FreeBSD 9 and 10. >=20 > There maybe serious reasons having the Linuxulator, i do not know. But > if not, why spending rare developer resources on that? As far as I'm > concerned, the only real reason having the Linuxulator is some stuff > from Adobe for desktop systems, Flash. That's it. > For the scientific stuff, I try to move my people towards OpenSource, > since we do "standard" stuff and I expect students and scientists > solving problems without fancy coloured clicky funny things. In > "production", this might be another point of view. SciLab from INRIA is= > great, MuPAD, MAXIMA also. >=20 >=20 > But is there a real need running the Linux binary of Forefox on FreeBSD= ? >=20 > Regards, > Oliver >=20 --=20 O. Hartmann Freie Universit=C3=A4t Berlin Institut fuer Geologische Wissenschaften Fachrichtung Planetologie und Fernerkundung Malteser-Str. 74--100/Haus D D-12249 Berlin Tel.: +49 (0) 30 838 70 508 FAX: +49 (0) 30 838 70 837 --------------enig733EC6496B9A2087F8292378 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO+zMDAAoJEOgBcD7A/5N8Zm4IAODc+TNbWJaBiGYKEsiciTe7 UhF+BPks6+4SHR/YVoBduz3ciFBAjNZMQ9Tc3zjgLVjfDSa9458tvssYaGUexT70 jSqM8o515oIE8YbMXN1CFuJ1/l3iERlWcO861Flh+Dem2p9weyDlTtXhWuMfrrMw 3y5RSI+aDlQGtQQJ21BaDl66jz/vsdL0lZIESTWaxzud20Sf9gfIrqeSU0FADNr+ 8fdqqYf9nsvo/7p4LZ2IHrhWbS0U750G24Vr+lYvD518JWuA9wvk+Vs/eK8Atr60 iuiY+hY3RrumdvGepJm1NQdO64NQ+47PQoRrEJefyd+fD/upwpg5dLf+pWyfts8= =P5tT -----END PGP SIGNATURE----- --------------enig733EC6496B9A2087F8292378-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 15:57:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 125CE106566B; Wed, 28 Dec 2011 15:57:03 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id C7FAD8FC14; Wed, 28 Dec 2011 15:57:02 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:110:9155:3851:5ce] (unknown [IPv6:2001:7b8:3a7:0:110:9155:3851:5ce]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id DD9035C37; Wed, 28 Dec 2011 16:57:01 +0100 (CET) Message-ID: <4EFB3C4F.2020108@FreeBSD.org> Date: Wed, 28 Dec 2011 16:57:03 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: "O. Hartmann" References: <4EFAF3FC.60002@zedat.fu-berlin.de> In-Reply-To: <4EFAF3FC.60002@zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Current FreeBSD , Ports FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 15:57:03 -0000 On 2011-12-28 11:48, O. Hartmann wrote: ... > /usr/local/bin/ld: > /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a(functexcept.o): > relocation R_X86_64_32 against `std::bad_exception::~bad_exception()' > can not be used when making a shared object; recompile with -fPIC > /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: > could not read symbols: Bad value > collect2: ld returned 1 exit status What happens if you compile and link the following simple program with g++46: #include int main(void) { std::cout << "Hello World!" << std::endl; return 0; } Does it fail with the same type of link error, e.g. linking to the libstdc++.a instead libstdc++.so? It would be nice if you can add -v to the command line, and paste the output here. I suspect your g++46 port is busted, for some reason. From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 16:15:47 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2FF21065675; Wed, 28 Dec 2011 16:15:47 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 531FF8FC15; Wed, 28 Dec 2011 16:15:46 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1RfwAL-0002Si-Ht>; Wed, 28 Dec 2011 17:15:45 +0100 Received: from e178027189.adsl.alicedsl.de ([85.178.27.189] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1RfwAL-0007K8-Bi>; Wed, 28 Dec 2011 17:15:45 +0100 Message-ID: <4EFB40B0.8020503@zedat.fu-berlin.de> Date: Wed, 28 Dec 2011 17:15:44 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Dimitry Andric References: <4EFAF3FC.60002@zedat.fu-berlin.de> <4EFB3C4F.2020108@FreeBSD.org> In-Reply-To: <4EFB3C4F.2020108@FreeBSD.org> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1FD12ABD761C91083378292F" X-Originating-IP: 85.178.27.189 Cc: Current FreeBSD , Ports FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 16:15:47 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1FD12ABD761C91083378292F Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Am 12/28/11 16:57, schrieb Dimitry Andric: > On 2011-12-28 11:48, O. Hartmann wrote: > ... >> /usr/local/bin/ld: >> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libs= tdc++.a(functexcept.o): >> >> relocation R_X86_64_32 against `std::bad_exception::~bad_exception()' >> can not be used when making a shared object; recompile with -fPIC >> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libs= tdc++.a: >> >> could not read symbols: Bad value >> collect2: ld returned 1 exit status >=20 > What happens if you compile and link the following simple program with > g++46: >=20 > #include >=20 > int main(void) > { > std::cout << "Hello World!" << std::endl; > return 0; > } >=20 > Does it fail with the same type of link error, e.g. linking to the > libstdc++.a instead libstdc++.so? It would be nice if you can add -v t= o > the command line, and paste the output here. >=20 > I suspect your g++46 port is busted, for some reason. It works fine: ohartmann@telesto: [~] g++46 -v -o muff muff.cpp Using built-in specs. COLLECT_GCC=3Dg++46 COLLECT_LTO_WRAPPER=3D/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd= 9.0/4.6.3/lto-wrapper Target: x86_64-portbld-freebsd9.0 Configured with: ./../gcc-4.6-20111209/configure --disable-nls --enable-languages=3Dc,c++,objc,fortran --libdir=3D/usr/local/lib/gcc46 --libexecdir=3D/usr/local/libexec/gcc46 --program-suffix=3D46 --with-as=3D/usr/local/bin/as --with-gmp=3D/usr/local --with-gxx-include-dir=3D/usr/local/lib/gcc46/include/c++/ --with-ld=3D/usr/local/bin/ld --with-libiconv-prefix=3D/usr/local --with-pkgversion=3D'FreeBSD Ports Collection' --with-system-zlib --enable-languages=3Dc,c++,objc,fortran,java --prefix=3D/usr/local --mandir=3D/usr/local/man --infodir=3D/usr/local/info/gcc46 --build=3Dx86_64-portbld-freebsd9.0 Thread model: posix gcc version 4.6.3 20111209 (prerelease) (FreeBSD Ports Collection) COLLECT_GCC_OPTIONS=3D'-v' '-o' 'muff' '-shared-libgcc' '-mtune=3Dgeneric= ' '-march=3Dx86-64' /usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/cc1plus -quiet -v muff.cpp -quiet -dumpbase muff.cpp -mtune=3Dgeneric -march=3Dx86-64 -auxbase muff -version -o /var/tmp//ccu1eDPY.s GNU C++ (FreeBSD Ports Collection) version 4.6.3 20111209 (prerelease) (x86_64-portbld-freebsd9.0) compiled by GNU C version 4.6.3 20111209 (prerelease), GMP version 5.0.2, MPFR version 3.1.0-p3, MPC version 0.9 GGC heuristics: --param ggc-min-expand=3D100 --param ggc-min-heapsize=3D1= 31072 ignoring nonexistent directory "/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../../../= x86_64-portbld-freebsd9.0/include" #include "..." search starts here: #include <...> search starts here: /usr/local/lib/gcc46/include/c++/ /usr/local/lib/gcc46/include/c++//x86_64-portbld-freebsd9.0 /usr/local/lib/gcc46/include/c++//backward /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/include /usr/local/include /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/include-fixed /usr/include End of search list. GNU C++ (FreeBSD Ports Collection) version 4.6.3 20111209 (prerelease) (x86_64-portbld-freebsd9.0) compiled by GNU C version 4.6.3 20111209 (prerelease), GMP version 5.0.2, MPFR version 3.1.0-p3, MPC version 0.9 GGC heuristics: --param ggc-min-expand=3D100 --param ggc-min-heapsize=3D1= 31072 Compiler executable checksum: 1f5bea4d4b089362b811317a91015e20 COLLECT_GCC_OPTIONS=3D'-v' '-o' 'muff' '-shared-libgcc' '-mtune=3Dgeneric= ' '-march=3Dx86-64' /usr/local/bin/as -v -o /var/tmp//ccblbg7V.o /var/tmp//ccu1eDPY.s GNU assembler version 2.22 (x86_64-portbld-freebsd9.0) using BFD version (GNU Binutils) 2.22 COMPILER_PATH=3D/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd9.0/4.= 6.3/:/usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/:/usr/l= ocal/libexec/gcc46/gcc/x86_64-portbld-freebsd9.0/:/usr/local/lib/gcc46/gc= c/x86_64-portbld-freebsd9.0/4.6.3/:/usr/local/lib/gcc46/gcc/x86_64-portbl= d-freebsd9.0/:/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/..= /../../../../x86_64-portbld-freebsd9.0/bin/ LIBRARY_PATH=3D/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/:= /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../../../x= 86_64-portbld-freebsd9.0/lib/:/usr/local/lib/gcc46/gcc/x86_64-portbld-fre= ebsd9.0/4.6.3/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS=3D'-v' '-o' 'muff' '-shared-libgcc' '-mtune=3Dgeneric= ' '-march=3Dx86-64' /usr/local/libexec/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/collect2 --eh-frame-hdr -V -dynamic-linker /libexec/ld-elf.so.1 -o muff /usr/lib/crt1.o /usr/lib/crti.o /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/crtbegin.o -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3 -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../../..= /x86_64-portbld-freebsd9.0/lib -L/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../.. /var/tmp//ccblbg7V.o -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/crtend.o /usr/lib/crtn.o GNU ld (GNU Binutils) 2.22 Supported emulations: elf_x86_64_fbsd elf_i386_fbsd elf_x86_64 elf_i386 elf_l1om elf_l1om_fbsd elf_k1om elf_k1om_fbsd ohartmann@telesto: [~] ./muff Hello World! ohartmann@telesto: [~] --------------enig1FD12ABD761C91083378292F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO+0CwAAoJEOgBcD7A/5N8L60IAIzkpLgZz4zMkHE8L99QA9U3 pcEwMYduL04uT6rXtDXI/8eW3pVvZWTcr4DwUgFRdm6QLjFJOc2wrE3tB5PVz7GU H0vR4VwCl75fNNjvKdREuuTyvfyovlBC4Z79HvMS47jS4UtsQfwLbXn7M5Z12YpM W8jZA/ADYZ0TnzIHSxfaHOP6uuRrzM/tzoUTrp2oHqdE12cCsdTgVZswU2VK9qGU 4AE5X5AKe3HHirFkD6e6Vsw6A6Hxy0f9RFNp9k5sqDteA4Jasi2XqTRya/9YHgxO KHrvBhXu0XUJJ3utJ8anpUc1qBCMjBbDSNgfcPMQ9eXIYocxEVE5xGghjZ9BOHU= =c6Hp -----END PGP SIGNATURE----- --------------enig1FD12ABD761C91083378292F-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 16:16:57 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E5361065678 for ; Wed, 28 Dec 2011 16:16:57 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id ED6168FC23 for ; Wed, 28 Dec 2011 16:16:56 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so22232249wgb.31 for ; Wed, 28 Dec 2011 08:16:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=bBZlrlSStBdDtB1vE+V0Aze3D4oOvNu36Xh/buzRN/k=; b=In6tCkIT1pvMZPJBjBGYxbrwkNNhfq0V9g7UqnkDxjlpIZ3ymxQ7G8Pv/7y4IOUtFZ XBxXMimoKDw1Aqzp4sTispdsJ8Y6rm4WAmlbpxA/9AQYJdlCzA7OnC3BbD2tZodsMTgU MBpJOv+b+92pw8Y7hZ0A4RZEEZKcYONMVnguk= Received: by 10.227.202.211 with SMTP id ff19mr32153149wbb.15.1325087118190; Wed, 28 Dec 2011 07:45:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.177.68 with HTTP; Wed, 28 Dec 2011 07:44:57 -0800 (PST) In-Reply-To: <201105040107.p4417NTR048534@pozo.com> References: <201105040107.p4417NTR048534@pozo.com> From: Renato Botelho Date: Wed, 28 Dec 2011 13:44:57 -0200 Message-ID: To: Manfred Antar Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org Subject: Re: Clang error make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 16:16:57 -0000 On Tue, May 3, 2011 at 10:07 PM, Manfred Antar wrote: > I get this error when trying to buildworld on current i386. > It's been this way for awhile Any Ideas ? > > =3D=3D=3D> boot/i386/boot0 (all) > clang -O2 -pipe =A0-DVOLUME_SERIAL -DPXE -DFLAGS=3D0x8f =A0-DTICKS=3D0xb6= =A0-DCOMSPEED=3D"7 << 5 + 3" -ffreestanding -mpreferred-stack-boundary=3D2= =A0-mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=3Dgn= u99 =A0 =A0-c /usr/src/sys/boot/i386/boot0/boot0.S > clang: warning: argument unused during compilation: '-mpreferred-stack-bo= undary=3D2' > /tmp/cc-4SXZt8.s:42:11: error: .code16 not supported yet > =A0.code16 # This runs in real mode > =A0 =A0 =A0 =A0 =A0^ > /tmp/cc-4SXZt8.s:313:3: error: unknown use of instruction mnemonic withou= t a size suffix > =A0jmp *%bx # Invoke bootstrap > =A0^ > /tmp/cc-4SXZt8.s:346:3: error: invalid operand for instruction > =A0retw # To caller > =A0^ > /tmp/cc-4SXZt8.s:372:3: error: invalid operand for instruction > =A0retw # To caller > =A0^ > *** Error code 1 > > Stop in /usr/src/sys/boot/i386/boot0. > *** Error code 1 > > Stop in /usr/src/sys/boot/i386. > *** Error code 1 > > Stop in /usr/src/sys/boot. > *** Error code 1 > > Stop in /usr/src/sys. Hello Manfred, I'm having this same issue on a i386 HEAD buildworld with clang. Did you find a fix for this? For now i built boot0 with gcc and it was built fine. Regards --=20 Renato Botelho From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 16:26:12 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 108F2106566B for ; Wed, 28 Dec 2011 16:26:12 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id C6BB98FC0C for ; Wed, 28 Dec 2011 16:26:11 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:110:9155:3851:5ce] (unknown [IPv6:2001:7b8:3a7:0:110:9155:3851:5ce]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 129505C37; Wed, 28 Dec 2011 17:26:11 +0100 (CET) Message-ID: <4EFB4324.1060002@FreeBSD.org> Date: Wed, 28 Dec 2011 17:26:12 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Renato Botelho References: <201105040107.p4417NTR048534@pozo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Clang error make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 16:26:12 -0000 On 2011-12-28 16:44, Renato Botelho wrote: > On Tue, May 3, 2011 at 10:07 PM, Manfred Antar wrote: >> I get this error when trying to buildworld on current i386. >> It's been this way for awhile Any Ideas ? >> >> ===> boot/i386/boot0 (all) >> clang -O2 -pipe -DVOLUME_SERIAL -DPXE -DFLAGS=0x8f -DTICKS=0xb6 -DCOMSPEED="7<< 5 + 3" -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -c /usr/src/sys/boot/i386/boot0/boot0.S >> clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' >> /tmp/cc-4SXZt8.s:42:11: error: .code16 not supported yet >> .code16 # This runs in real mode >> ^ This is expected, since the above command line is supposed to have '-no-integrated-as' added. For some reason, the test for clang in sys/boot/i386/boot0/Makefile is not working as it should. Most likely, it is due to the way you set CC, CXX and/or CPP in make.conf. Can you please post that file? From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 16:33:20 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F23F2106567F for ; Wed, 28 Dec 2011 16:33:20 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 83B758FC0A for ; Wed, 28 Dec 2011 16:33:19 +0000 (UTC) Received: by wibhr1 with SMTP id hr1so11131694wib.13 for ; Wed, 28 Dec 2011 08:33:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=njeWEVeA94G3mYsC9FqxKpXWqaxiMDVHR1o6EUb+I0c=; b=DtaKuA6H8eK5bP6pAS2vEZXssZa/KwCQhEa5rvutseiYvNE0bAIW/uPfBAZe1XxFO8 AFa1ojcLhXJPxYJE1lyber+wdI8xufnT8wOqyXAhbn10pEs06b3ayDKeK5POtZZepY9s KwS4ar/6xZb+PGlnqYxa6BKl50xMpQ7uzlnUk= Received: by 10.180.19.106 with SMTP id d10mr71802742wie.2.1325089999255; Wed, 28 Dec 2011 08:33:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.177.68 with HTTP; Wed, 28 Dec 2011 08:32:58 -0800 (PST) In-Reply-To: <4EFB4324.1060002@FreeBSD.org> References: <201105040107.p4417NTR048534@pozo.com> <4EFB4324.1060002@FreeBSD.org> From: Renato Botelho Date: Wed, 28 Dec 2011 14:32:58 -0200 Message-ID: To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org Subject: Re: Clang error make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 16:33:21 -0000 On Wed, Dec 28, 2011 at 2:26 PM, Dimitry Andric wrote: > On 2011-12-28 16:44, Renato Botelho wrote: >> >> On Tue, May 3, 2011 at 10:07 PM, Manfred Antar =A0wrote: >>> >>> I get this error when trying to buildworld on current i386. >>> It's been this way for awhile Any Ideas ? >>> >>> =3D=3D=3D> =A0boot/i386/boot0 (all) >>> clang -O2 -pipe =A0-DVOLUME_SERIAL -DPXE -DFLAGS=3D0x8f =A0-DTICKS=3D0x= b6 >>> =A0-DCOMSPEED=3D"7<< =A05 + 3" -ffreestanding -mpreferred-stack-boundar= y=3D2 >>> =A0-mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std= =3Dgnu99 >>> =A0-c /usr/src/sys/boot/i386/boot0/boot0.S >>> clang: warning: argument unused during compilation: >>> '-mpreferred-stack-boundary=3D2' >>> /tmp/cc-4SXZt8.s:42:11: error: .code16 not supported yet >>> =A0.code16 # This runs in real mode >>> =A0 =A0 =A0 =A0 =A0^ > > > This is expected, since the above command line is supposed to have > '-no-integrated-as' added. =A0For some reason, the test for clang in > sys/boot/i386/boot0/Makefile is not working as it should. > > Most likely, it is due to the way you set CC, CXX and/or CPP in > make.conf. =A0Can you please post that file? Sure, follow my src.conf: .if !defined(CC) || ${CC} =3D=3D "cc" CC=3Dclang .endif .if !defined(CXX) || ${CXX} =3D=3D "c++" CXX=3Dclang++ .endif .if !defined(CPP) || ${CPP} =3D=3D "cpp" CPP=3Dclang-cpp .endif # Don't die on warnings NO_WERROR=3D WERROR=3D # Don't forget this when using Jails! NO_FSCHG=3D and my make.conf KERNCONF=3DMURPHYS WITH_OPTIONS=3Dyes WITH_VIM_OPTIONS=3Dyes WITHOUT_X11=3Dyes # added by use.perl 2011-12-12 13:19:26 PERL_VERSION=3D5.12.4 More information about the system installed on this machine: garga@murphys:~> uname -a FreeBSD murphys.ramenzoni.com.br 9.0-RC3 FreeBSD 9.0-RC3 #0: Sun Dec 4 08:01:02 UTC 2011 root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 garga@murphys:~> clang -v FreeBSD clang version 3.0 (branches/release_30 142614) 20111021 Target: i386-unknown-freebsd9.0 Thread model: posix --=20 Renato Botelho From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 16:39:18 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D63C51065670 for ; Wed, 28 Dec 2011 16:39:18 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 595408FC0A for ; Wed, 28 Dec 2011 16:39:18 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:110:9155:3851:5ce] (unknown [IPv6:2001:7b8:3a7:0:110:9155:3851:5ce]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 9D2EC5C37; Wed, 28 Dec 2011 17:39:17 +0100 (CET) Message-ID: <4EFB4637.10604@FreeBSD.org> Date: Wed, 28 Dec 2011 17:39:19 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Renato Botelho References: <201105040107.p4417NTR048534@pozo.com> <4EFB4324.1060002@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Clang error make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 16:39:18 -0000 On 2011-12-28 17:32, Renato Botelho wrote: > On Wed, Dec 28, 2011 at 2:26 PM, Dimitry Andric wrote: ... >> Most likely, it is due to the way you set CC, CXX and/or CPP in >> make.conf. Can you please post that file? > > Sure, follow my src.conf: > > .if !defined(CC) || ${CC} == "cc" > CC=clang > .endif > .if !defined(CXX) || ${CXX} == "c++" > CXX=clang++ > .endif > .if !defined(CPP) || ${CPP} == "cpp" > CPP=clang-cpp > .endif This part should go into make.conf, *not* src.conf. If you want to use clang only for src, not for anything else, put: .if ${.CURDIR:M/usr/src*} || ${.CURDIR:M/usr/obj*} # [... set CC, etc here... ] .endif > # Don't die on warnings > NO_WERROR= > WERROR= > # Don't forget this when using Jails! > NO_FSCHG= This is fine to have in src.conf. From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 16:42:56 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA3A61065673 for ; Wed, 28 Dec 2011 16:42:56 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id 49F208FC17 for ; Wed, 28 Dec 2011 16:42:55 +0000 (UTC) Received: (qmail invoked by alias); 28 Dec 2011 16:42:54 -0000 Received: from f055156006.adsl.alicedsl.de (EHLO mandree.no-ip.org) [78.55.156.6] by mail.gmx.net (mp022) with SMTP; 28 Dec 2011 17:42:54 +0100 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX1+xGHI3xayxuDcMBy9jUb/XNquMepI9pG0kZNjsvg 6WU/Pw4yinBt3Y Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 621FE23CF51 for ; Wed, 28 Dec 2011 17:42:53 +0100 (CET) Message-ID: <4EFB470D.3070309@gmx.de> Date: Wed, 28 Dec 2011 17:42:53 +0100 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Mnenhy/0.8.3 Thunderbird/3.1.16 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20111227215330.GI45484@redundancy.redundancy.org> In-Reply-To: <20111227215330.GI45484@redundancy.redundancy.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: SU+J systems do not fsck themselves X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 16:42:56 -0000 Am 27.12.2011 22:53, schrieb David Thiel: > I've had multiple machines now (9.0-RC3, amd64, i386 and earlier > 9-CURRENT on ppc) running SU+J that have had unexplained panics and > crashes start happening relating to disk I/O. When I end up running a > full fsck, it keeps turning out that the disk is dirty and corrupted, > but no mechanism is in place with SU+J to detect and fix this. A bgfsck > never happens, but a manual fsck in single-user does indeed fix the > crashing and weird behavior. Others have tested their SU+J volumes and > found them to have errors as well. This makes me super nervous. The one thing I figured is that in the light of power outages, or crashing virtualization hosts, you really really really need to disable disk write caches, and this affects softupdates, journalling, asynch file systems, just about everything. The fact that makes matters worse is that journalling or softupdates allow you to mount a silently-corrupted file system, whereas the traditional UFS/UFS2 sync/asynch mounts will fsck themselves in the foreground, so they get fixed before the FS panics. So can you be sure that: - your driver, chip set and hard disk execute ordered writes in order, - your driver, chip set and hard disk actually write data to permanent storage BEFORE acknowledging a successful write? Whenever I fixed these issues, I had no more corruptions. For ata and sata, there are loader tunables you will want to set, hw.ata.wc=0 and kern.cam.ada.write_cache=0. If your drives are under ada, ad, or ahci related control, try these settings. For SCSI, use camcontrol to turn the write cache off. softupdates is supposed to rectify most of the performance penalties incurred. Note also that you needed to set ahci_load=YES and atapicam_load=YES in 8.X, I've never bothered to check 7.X or 9.X WRT these settings. From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 16:51:37 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38CAC106566C; Wed, 28 Dec 2011 16:51:37 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 98AFC8FC14; Wed, 28 Dec 2011 16:51:36 +0000 (UTC) Received: by werb13 with SMTP id b13so11180853wer.13 for ; Wed, 28 Dec 2011 08:51:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=BvLDmiqHbEw7kKzbE7LNrBk6MNj2BBOOXaa29mEvdDM=; b=KN9ApItUk2WBs2DPRH//TvzA9K+hbICABm6AiyHvqOjgdssS4qjcYtYjcqMGm+gn7Q uUaHMJYZaXHcyrntuIulV5YwOxlaAbMAYXQEEzAIc3ptOg9KKjvgNrJTKf4YbUUgg2P2 CUsEI0Cb36jsSLTE/27cHjDeD/XCKtXHwr0cg= Received: by 10.216.143.206 with SMTP id l56mr24097121wej.46.1325091095497; Wed, 28 Dec 2011 08:51:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.177.68 with HTTP; Wed, 28 Dec 2011 08:51:14 -0800 (PST) In-Reply-To: <4EFB4637.10604@FreeBSD.org> References: <201105040107.p4417NTR048534@pozo.com> <4EFB4324.1060002@FreeBSD.org> <4EFB4637.10604@FreeBSD.org> From: Renato Botelho Date: Wed, 28 Dec 2011 14:51:14 -0200 Message-ID: To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org Subject: Re: Clang error make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 16:51:37 -0000 On Wed, Dec 28, 2011 at 2:39 PM, Dimitry Andric wrote: > On 2011-12-28 17:32, Renato Botelho wrote: >> >> On Wed, Dec 28, 2011 at 2:26 PM, Dimitry Andric =A0wrot= e: > > ... > >>> Most likely, it is due to the way you set CC, CXX and/or CPP in >>> make.conf. =A0Can you please post that file? >> >> >> Sure, follow my src.conf: >> >> .if !defined(CC) || ${CC} =3D=3D "cc" >> CC=3Dclang >> .endif >> .if !defined(CXX) || ${CXX} =3D=3D "c++" >> CXX=3Dclang++ >> .endif >> .if !defined(CPP) || ${CPP} =3D=3D "cpp" >> CPP=3Dclang-cpp >> .endif > > > This part should go into make.conf, *not* src.conf. =A0If you want to use > clang only for src, not for anything else, put: > > .if ${.CURDIR:M/usr/src*} || ${.CURDIR:M/usr/obj*} > # [... set CC, etc here... ] > > .endif > > >> # Don't die on warnings >> NO_WERROR=3D >> WERROR=3D >> # Don't forget this when using Jails! >> NO_FSCHG=3D > > > This is fine to have in src.conf. Worked like a charm. Thanks!! --=20 Renato Botelho From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 16:54:36 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C736106566B for ; Wed, 28 Dec 2011 16:54:36 +0000 (UTC) (envelope-from max@mxcrypt.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 043678FC0C for ; Wed, 28 Dec 2011 16:54:35 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so17391311vbb.13 for ; Wed, 28 Dec 2011 08:54:35 -0800 (PST) Received: by 10.52.94.242 with SMTP id df18mr4795090vdb.122.1325091275235; Wed, 28 Dec 2011 08:54:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.150.132 with HTTP; Wed, 28 Dec 2011 08:54:04 -0800 (PST) In-Reply-To: <4EFB470D.3070309@gmx.de> References: <20111227215330.GI45484@redundancy.redundancy.org> <4EFB470D.3070309@gmx.de> From: Maxim Khitrov Date: Wed, 28 Dec 2011 11:54:04 -0500 Message-ID: To: Matthias Andree Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: SU+J systems do not fsck themselves X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 16:54:36 -0000 On Wed, Dec 28, 2011 at 11:42 AM, Matthias Andree wrote: > Am 27.12.2011 22:53, schrieb David Thiel: >> I've had multiple machines now (9.0-RC3, amd64, i386 and earlier >> 9-CURRENT on ppc) running SU+J that have had unexplained panics and >> crashes start happening relating to disk I/O. When I end up running a >> full fsck, it keeps turning out that the disk is dirty and corrupted, >> but no mechanism is in place with SU+J to detect and fix this. A bgfsck >> never happens, but a manual fsck in single-user does indeed fix the >> crashing and weird behavior. Others have tested their SU+J volumes and >> found them to have errors as well. This makes me super nervous. > > The one thing I figured is that in the light of power outages, or > crashing virtualization hosts, you really really really need to disable > disk write caches, and this affects softupdates, journalling, asynch > file systems, just about everything. > > The fact that makes matters worse is that journalling or softupdates > allow you to mount a silently-corrupted file system, whereas the > traditional UFS/UFS2 sync/asynch mounts will fsck themselves in the > foreground, so they get fixed before the FS panics. > > So can you be sure that: > > - your driver, chip set and hard disk execute ordered writes in order, > > - your driver, chip set and hard disk actually write data to permanent > storage BEFORE acknowledging a successful write? > > Whenever I fixed these issues, I had no more corruptions. > > For ata and sata, there are loader tunables you will want to set, > hw.ata.wc=3D0 and kern.cam.ada.write_cache=3D0. > > If your drives are under ada, ad, or ahci related control, try these > settings. =C2=A0For SCSI, use camcontrol to turn the write cache off. > softupdates is supposed to rectify most of the performance penalties > incurred. > > Note also that you needed to set ahci_load=3DYES and atapicam_load=3DYES = in > 8.X, I've never bothered to check 7.X or 9.X WRT these settings. This is a bit off-topic, but I'm curious what the effect of NCQ is on softupdates? Since that too has the ability to reorder writes to disk, should it be disabled in addition to cache? Also, I would say that if you are using a hardware raid controller with a BBU, then allowing the use of controller's cache and write-back policy should be safe for use with softupdates. Any caching mechanism, for that matter, that has a separate power supply source should be ok. For example, the Intel 320 SSDs have a few on-board capacitors that are used to flush the cache in the event of a power loss. - Max From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 16:55:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 586DA1065670 for ; Wed, 28 Dec 2011 16:55:29 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from fmailer.gwdg.de (fmailer.gwdg.de [134.76.11.16]) by mx1.freebsd.org (Postfix) with ESMTP id C8F5D8FC0A for ; Wed, 28 Dec 2011 16:55:28 +0000 (UTC) Received: from pd951cfac.dip.t-dialin.net ([217.81.207.172] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1RfwOS-0001oY-3g; Wed, 28 Dec 2011 17:30:20 +0100 Message-ID: <4EFB447D.3000808@gwdg.de> Date: Wed, 28 Dec 2011 17:31:57 +0100 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Kostik Belousov References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> In-Reply-To: <20111228142957.GX50300@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: Current FreeBSD , "O. Hartmann" , Ports FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 16:55:29 -0000 On 28.12.2011 15:29 (UTC+1), Kostik Belousov wrote: > On Wed, Dec 28, 2011 at 03:10:12PM +0100, O. Hartmann wrote: >> Am 12/28/11 14:58, schrieb Kostik Belousov: >>> On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote: >>>> Hello out here. >>>> >>>> I run into a problem since one of the last portupdates and I do not know >>>> whether this has to do with binutils or gcc46 or even FreeBSD 9.0/10.0 >>>> AMD64. >>>> >>>> Background: >>>> We use a scientific graphical toolset for planetary research called >>>> ISIS3, which is provided by the USGS. We patched ISIS3 to run on FreeBSD >>>> 8/9/10 so far and it ran well with FreeBSD 8.2-STABLE and 9.0-PRE a >>>> couple of weeks ago. >>>> On all of my boxes, I do frequently a portupgrade, so I saw binutils got >>>> bumped up and gcc 4.6 is also getting really frequently changed these days. >>>> After a some portupdates within the last weeks, I just decided to >>>> compile ISIS3 again to keep it "fresh and on track", but it won't >>>> compile anymore. >>>> >>>> On all FreeBSD 9.0-PRERELEASE and FreeBSD 10.0-CURRENT (all AMD64 and >>>> CLANG built) I receive in some subfolders containing sources the >>>> follwoing error: >>>> >>>> [...] >>>> Adding API object [UniqueIOCachingAlgorithm] >>>> Adding API object [UniversalGroundMap] >>>> Adding API object [UserInterface] >>>> Adding API object [VariableLineScanCameraDetectorMap] >>>> Adding API object [VecFilter] >>>> Adding API object [WorldMapper] >>>> Adding API object [iException] >>>> Adding API object [iString] >>>> Adding API object [iTime] >>>> Working on Package [mex] (11:30:15) >>>> Adding API object [HrscCamera] >>>> /usr/local/bin/ld: >>>> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a(functexcept.o): >>>> relocation R_X86_64_32 against `std::bad_exception::~bad_exception()' >>>> can not be used when making a shared object; recompile with -fPIC >>>> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: >>>> could not read symbols: Bad value >>>> collect2: ld returned 1 exit status >>>> gmake[5]: *** [plugin] Error 1 >>>> cp: libHrscCamera.so: No such file or directory >>>> gmake[4]: *** [install] Error 1 >>> The error is completely clear as it is: the build tries to link static >>> library libstdc++.so into shared object. This is not supported. >> >> Thanks, Kostik, for the fast response. >> The error isn't so clear to me, sorry. I thought libstdc++.a is the >> static library and it is taken to be referenced/compiled into a shared > Linked in. > >> object created by the application I try to compile. > Right, and this is not supported. Code linked into shared object must > be compiled PIC. An .a library usually does not contain objects compiled > by PIC, ld just dutifully reported back. > >> >> I'm much more confused now, since I thought the last time I compiled >> that piece of software, I never got any error like that. Well, clang >> fails with some obscure errors on the code itself and I'm unwilling to >> correct them, I'll try the legacy gcc 4.2.1 and will report what's >> happening. > > It might have worked by accident (because libstdc++.a objects referenced > during the link did not carried unsupported relocations), or, much more > likely, the build system has changed and started doing stupid things. > It must not link static libraries into shared objects. > > You should examine why it does this, and fix it. Changing compilers is > just wasting a time. Hmm, I get a similar error when trying to build lang/gcc46 on recent 10-CURRENT: ---------------------------------------------------------------- [..snip..] Making all in include gmake[4]: Entering directory `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include' mkdir -p ./x86_64-portbld-freebsd10.0/bits/stdc++.h.gch /usr/ports/lang/gcc46/work/build/./gcc/xgcc -shared-libgcc -B/usr/ports/lang/gcc46/work/build/./gcc -nostdinc++ -L/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/src -L/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/src/.libs -B/usr/local/x86_64-portbld-freebsd10.0/bin/ -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem /usr/local/x86_64-portbld-freebsd10.0/include -isystem /usr/local/x86_64-portbld-freebsd10.0/sys-include -x c++-header -nostdinc++ -g -O2 -pipe -I/usr/local/include -fno-strict-aliasing -I/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/x86_64-portbld-freebsd10.0 -I/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include -I/usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/libsupc++ -O2 -g -std=gnu++0x /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h \ -o x86_64-portbld-freebsd10.0/bits/stdc++.h.gch/O2ggnu++0x.gch In file included from /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/chrono:38:0, from /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:100: /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/ratio:133:31: error: macro "_Static_assert" passed 3 arguments, but takes just 2 In file included from /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:103:0: /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/future:376:39: error: macro "_Static_assert" passed 4 arguments, but takes just 2 In file included from /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/memory:85:0, from /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:81: /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h: In constructor 'constexpr std::unique_ptr<_Tp, _Dp>::unique_ptr()': /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h:117:59: error: constexpr constructor does not have empty body /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h: In constructor 'constexpr std::unique_ptr<_Tp, _Dp>::unique_ptr(std::nullptr_t)': /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h:139:59: error: constexpr constructor does not have empty body /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h: In constructor 'constexpr std::unique_ptr<_Tp [], _Dp>::unique_ptr()': /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h:279:59: error: constexpr constructor does not have empty body /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h: In constructor 'constexpr std::unique_ptr<_Tp [], _Dp>::unique_ptr(std::nullptr_t)': /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h:301:59: error: constexpr constructor does not have empty body In file included from /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/cassert:45:0, from /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:34: /usr/include/assert.h: At global scope: /usr/include/assert.h:62:23: error: '_Static_assert' does not name a type /usr/include/assert.h:62:23: error: '_Static_assert' does not name a type gmake[4]: *** [x86_64-portbld-freebsd10.0/bits/stdc++.h.gch/O2ggnu++0x.gch] Fehler 1 gmake[4]: Leaving directory `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include' gmake[3]: *** [all-recursive] Fehler 1 gmake[3]: Leaving directory `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3' gmake[2]: *** [all] Fehler 2 gmake[2]: Leaving directory `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3' gmake[1]: *** [all-target-libstdc++-v3] Fehler 2 gmake[1]: Leaving directory `/usr/ports/lang/gcc46/work/build' gmake: *** [bootstrap-lean] Fehler 2 *** Error code 1 Stop in /usr/ports/lang/gcc46. ---------------------------------------------------------------- I guess that this error could have something to do with r228902 from 2011-12-26: /head/include/assert.h: As per C11, add static_assert() to . lang/gcc46 builts fine for me before this revision. What do you think about it? Rainer From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 17:47:43 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F6541065673; Wed, 28 Dec 2011 17:47:43 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 318A58FC1B; Wed, 28 Dec 2011 17:47:42 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1RfxbJ-0002ve-TA>; Wed, 28 Dec 2011 18:47:41 +0100 Received: from e178027189.adsl.alicedsl.de ([85.178.27.189] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1RfxbJ-00031L-La>; Wed, 28 Dec 2011 18:47:41 +0100 Message-ID: <4EFB563D.2090705@zedat.fu-berlin.de> Date: Wed, 28 Dec 2011 18:47:41 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Rainer Hurling References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> In-Reply-To: <4EFB447D.3000808@gwdg.de> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA0A081B733AD5F8AE3CAC91D" X-Originating-IP: 85.178.27.189 Cc: Kostik Belousov , Current FreeBSD , Ports FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 17:47:43 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA0A081B733AD5F8AE3CAC91D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 12/28/11 17:31, schrieb Rainer Hurling: > On 28.12.2011 15:29 (UTC+1), Kostik Belousov wrote: >> On Wed, Dec 28, 2011 at 03:10:12PM +0100, O. Hartmann wrote: >>> Am 12/28/11 14:58, schrieb Kostik Belousov: >>>> On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote: >>>>> Hello out here. >>>>> >>>>> I run into a problem since one of the last portupdates and I do not= >>>>> know >>>>> whether this has to do with binutils or gcc46 or even FreeBSD 9.0/1= 0.0 >>>>> AMD64. >>>>> >>>>> Background: >>>>> We use a scientific graphical toolset for planetary research called= >>>>> ISIS3, which is provided by the USGS. We patched ISIS3 to run on >>>>> FreeBSD >>>>> 8/9/10 so far and it ran well with FreeBSD 8.2-STABLE and 9.0-PRE a= >>>>> couple of weeks ago. >>>>> On all of my boxes, I do frequently a portupgrade, so I saw >>>>> binutils got >>>>> bumped up and gcc 4.6 is also getting really frequently changed >>>>> these days. >>>>> After a some portupdates within the last weeks, I just decided to >>>>> compile ISIS3 again to keep it "fresh and on track", but it won't >>>>> compile anymore. >>>>> >>>>> On all FreeBSD 9.0-PRERELEASE and FreeBSD 10.0-CURRENT (all AMD64 a= nd >>>>> CLANG built) I receive in some subfolders containing sources the >>>>> follwoing error: >>>>> >>>>> [...] >>>>> Adding API object [UniqueIOCachingAlgorithm] >>>>> Adding API object [UniversalGroundMap] >>>>> Adding API object [UserInterface] >>>>> Adding API object [VariableLineScanCameraDetectorMap] >>>>> Adding API object [VecFilter] >>>>> Adding API object [WorldMapper] >>>>> Adding API object [iException] >>>>> Adding API object [iString] >>>>> Adding API object [iTime] >>>>> Working on Package [mex] (11:30:15) >>>>> Adding API object [HrscCamera] >>>>> /usr/local/bin/ld: >>>>> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../l= ibstdc++.a(functexcept.o): >>>>> >>>>> relocation R_X86_64_32 against `std::bad_exception::~bad_exception(= )' >>>>> can not be used when making a shared object; recompile with -fPIC >>>>> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../l= ibstdc++.a: >>>>> >>>>> could not read symbols: Bad value >>>>> collect2: ld returned 1 exit status >>>>> gmake[5]: *** [plugin] Error 1 >>>>> cp: libHrscCamera.so: No such file or directory >>>>> gmake[4]: *** [install] Error 1 >>>> The error is completely clear as it is: the build tries to link stat= ic >>>> library libstdc++.so into shared object. This is not supported. >>> >>> Thanks, Kostik, for the fast response. >>> The error isn't so clear to me, sorry. I thought libstdc++.a is the >>> static library and it is taken to be referenced/compiled into a share= d >> Linked in. >> >>> object created by the application I try to compile. >> Right, and this is not supported. Code linked into shared object must >> be compiled PIC. An .a library usually does not contain objects compil= ed >> by PIC, ld just dutifully reported back. >> >>> >>> I'm much more confused now, since I thought the last time I compiled >>> that piece of software, I never got any error like that. Well, clang >>> fails with some obscure errors on the code itself and I'm unwilling t= o >>> correct them, I'll try the legacy gcc 4.2.1 and will report what's >>> happening. >> >> It might have worked by accident (because libstdc++.a objects referenc= ed >> during the link did not carried unsupported relocations), or, much mor= e >> likely, the build system has changed and started doing stupid things. >> It must not link static libraries into shared objects. >> >> You should examine why it does this, and fix it. Changing compilers is= >> just wasting a time. >=20 >=20 > Hmm, I get a similar error when trying to build lang/gcc46 on recent > 10-CURRENT: >=20 > ---------------------------------------------------------------- > [..snip..] > Making all in include > gmake[4]: Entering directory > `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-= v3/include' >=20 > mkdir -p ./x86_64-portbld-freebsd10.0/bits/stdc++.h.gch > /usr/ports/lang/gcc46/work/build/./gcc/xgcc -shared-libgcc > -B/usr/ports/lang/gcc46/work/build/./gcc -nostdinc++ > -L/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++= -v3/src > -L/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++= -v3/src/.libs > -B/usr/local/x86_64-portbld-freebsd10.0/bin/ > -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem > /usr/local/x86_64-portbld-freebsd10.0/include -isystem > /usr/local/x86_64-portbld-freebsd10.0/sys-include -x c++-header > -nostdinc++ -g -O2 -pipe -I/usr/local/include -fno-strict-aliasing > -I/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++= -v3/include/x86_64-portbld-freebsd10.0 > -I/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++= -v3/include > -I/usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/libsupc++ -O= 2 > -g -std=3Dgnu++0x > /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precom= piled/stdc++.h > \ > -o x86_64-portbld-freebsd10.0/bits/stdc++.h.gch/O2ggnu++0x.gch > In file included from > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/chrono:38:0, >=20 > from > /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precom= piled/stdc++.h:100: >=20 > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/ratio:133:31: > error: macro "_Static_assert" passed 3 arguments, but takes just 2 > In file included from > /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precom= piled/stdc++.h:103:0: >=20 > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/future:376:39: > error: macro "_Static_assert" passed 4 arguments, but takes just 2 > In file included from > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/memory:85:0, >=20 > from > /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precom= piled/stdc++.h:81: >=20 > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/bits/unique_ptr.h: > In constructor 'constexpr std::unique_ptr<_Tp, _Dp>::unique_ptr()': > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/bits/unique_ptr.h:117:59: > error: constexpr constructor does not have empty body > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/bits/unique_ptr.h: > In constructor 'constexpr std::unique_ptr<_Tp, > _Dp>::unique_ptr(std::nullptr_t)': > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/bits/unique_ptr.h:139:59: > error: constexpr constructor does not have empty body > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/bits/unique_ptr.h: > In constructor 'constexpr std::unique_ptr<_Tp [], _Dp>::unique_ptr()': > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/bits/unique_ptr.h:279:59: > error: constexpr constructor does not have empty body > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/bits/unique_ptr.h: > In constructor 'constexpr std::unique_ptr<_Tp [], > _Dp>::unique_ptr(std::nullptr_t)': > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/bits/unique_ptr.h:301:59: > error: constexpr constructor does not have empty body > In file included from > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v= 3/include/cassert:45:0, >=20 > from > /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precom= piled/stdc++.h:34: >=20 > /usr/include/assert.h: At global scope: > /usr/include/assert.h:62:23: error: '_Static_assert' does not name a ty= pe > /usr/include/assert.h:62:23: error: '_Static_assert' does not name a ty= pe > gmake[4]: *** > [x86_64-portbld-freebsd10.0/bits/stdc++.h.gch/O2ggnu++0x.gch] Fehler 1 > gmake[4]: Leaving directory > `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-= v3/include' >=20 > gmake[3]: *** [all-recursive] Fehler 1 > gmake[3]: Leaving directory > `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-= v3' > gmake[2]: *** [all] Fehler 2 > gmake[2]: Leaving directory > `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-= v3' > gmake[1]: *** [all-target-libstdc++-v3] Fehler 2 > gmake[1]: Leaving directory `/usr/ports/lang/gcc46/work/build' > gmake: *** [bootstrap-lean] Fehler 2 > *** Error code 1 > Stop in /usr/ports/lang/gcc46. > ---------------------------------------------------------------- >=20 >=20 > I guess that this error could have something to do with r228902 from > 2011-12-26: >=20 > /head/include/assert.h: As per C11, add static_assert() to . >=20 > lang/gcc46 builts fine for me before this revision. What do you think > about it? > Rainer I already posted a PR. The first time I saw a similar error was, when I made builtworld on FBSD 10.0 with WITH_ICONV=3DYES set in /etc/src.conf. I wasn't even able to build the lang/gcc46 with the legacy gcc42 compiler. But the problem I reported while compiling a non-poted piece of software also occurs with the legacy gcc 4.2, but there the error is looking something different, reporting some missing vtable: or similar. Oliver --------------enigA0A081B733AD5F8AE3CAC91D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO+1Y9AAoJEOgBcD7A/5N8hgcH/jYACEsfghRKhD/ZbDeQ3v6O YCM9pBa8uZcFvV1wCDL4e1fg2FYtosECpUinIWS4LRISm3cbLLCxCPfrsLM6ipE2 vaaVec9N+udmXqZu5X4xwJSs8dzrClxxiV3F89cYvidbzkMjJznDZ8LP4Bi86m19 cAalr4HbbiPEl2aHJSpQYc93aQRX9ozXEC5enCuji2kT1CCSqEAVWSILuvifIzhc bOd64HX3goAMnx/CiiNMgABdx8XM0stYHL0gVrtEoaLird6g2vr9Tp9ouEpdlnYy TKvTowcHyOTYCm55zCcmTj7jQR2emt+5ME8Ntq02am8CHKzvv2wqaVuL0VpG58Y= =zASZ -----END PGP SIGNATURE----- --------------enigA0A081B733AD5F8AE3CAC91D-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 17:57:45 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D219A106564A for ; Wed, 28 Dec 2011 17:57:45 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id 4444C8FC15 for ; Wed, 28 Dec 2011 17:57:44 +0000 (UTC) Received: from deuterium.andreas.nets (dhclient-91-190-14-19.flashcable.ch [91.190.14.19]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id pBSHsBKA007458; Wed, 28 Dec 2011 18:54:12 +0100 (CET) (envelope-from andreast-list@fgznet.ch) Message-ID: <4EFB5894.7030306@fgznet.ch> Date: Wed, 28 Dec 2011 18:57:40 +0100 From: Andreas Tobler User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Rainer Hurling , Ed Schouten References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> In-Reply-To: <4EFB447D.3000808@gwdg.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: Kostik Belousov , Current FreeBSD , "O. Hartmann" Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 17:57:45 -0000 On 28.12.11 17:31, Rainer Hurling wrote: > On 28.12.2011 15:29 (UTC+1), Kostik Belousov wrote: >> On Wed, Dec 28, 2011 at 03:10:12PM +0100, O. Hartmann wrote: >>> Am 12/28/11 14:58, schrieb Kostik Belousov: >>>> On Wed, Dec 28, 2011 at 11:48:28AM +0100, O. Hartmann wrote: >>>>> Hello out here. >>>>> >>>>> I run into a problem since one of the last portupdates and I do not know >>>>> whether this has to do with binutils or gcc46 or even FreeBSD 9.0/10.0 >>>>> AMD64. >>>>> >>>>> Background: >>>>> We use a scientific graphical toolset for planetary research called >>>>> ISIS3, which is provided by the USGS. We patched ISIS3 to run on FreeBSD >>>>> 8/9/10 so far and it ran well with FreeBSD 8.2-STABLE and 9.0-PRE a >>>>> couple of weeks ago. >>>>> On all of my boxes, I do frequently a portupgrade, so I saw binutils got >>>>> bumped up and gcc 4.6 is also getting really frequently changed these days. >>>>> After a some portupdates within the last weeks, I just decided to >>>>> compile ISIS3 again to keep it "fresh and on track", but it won't >>>>> compile anymore. >>>>> >>>>> On all FreeBSD 9.0-PRERELEASE and FreeBSD 10.0-CURRENT (all AMD64 and >>>>> CLANG built) I receive in some subfolders containing sources the >>>>> follwoing error: >>>>> >>>>> [...] >>>>> Adding API object [UniqueIOCachingAlgorithm] >>>>> Adding API object [UniversalGroundMap] >>>>> Adding API object [UserInterface] >>>>> Adding API object [VariableLineScanCameraDetectorMap] >>>>> Adding API object [VecFilter] >>>>> Adding API object [WorldMapper] >>>>> Adding API object [iException] >>>>> Adding API object [iString] >>>>> Adding API object [iTime] >>>>> Working on Package [mex] (11:30:15) >>>>> Adding API object [HrscCamera] >>>>> /usr/local/bin/ld: >>>>> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a(functexcept.o): >>>>> relocation R_X86_64_32 against `std::bad_exception::~bad_exception()' >>>>> can not be used when making a shared object; recompile with -fPIC >>>>> /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: >>>>> could not read symbols: Bad value >>>>> collect2: ld returned 1 exit status >>>>> gmake[5]: *** [plugin] Error 1 >>>>> cp: libHrscCamera.so: No such file or directory >>>>> gmake[4]: *** [install] Error 1 >>>> The error is completely clear as it is: the build tries to link static >>>> library libstdc++.so into shared object. This is not supported. >>> >>> Thanks, Kostik, for the fast response. >>> The error isn't so clear to me, sorry. I thought libstdc++.a is the >>> static library and it is taken to be referenced/compiled into a shared >> Linked in. >> >>> object created by the application I try to compile. >> Right, and this is not supported. Code linked into shared object must >> be compiled PIC. An .a library usually does not contain objects compiled >> by PIC, ld just dutifully reported back. >> >>> >>> I'm much more confused now, since I thought the last time I compiled >>> that piece of software, I never got any error like that. Well, clang >>> fails with some obscure errors on the code itself and I'm unwilling to >>> correct them, I'll try the legacy gcc 4.2.1 and will report what's >>> happening. >> >> It might have worked by accident (because libstdc++.a objects referenced >> during the link did not carried unsupported relocations), or, much more >> likely, the build system has changed and started doing stupid things. >> It must not link static libraries into shared objects. >> >> You should examine why it does this, and fix it. Changing compilers is >> just wasting a time. > > > Hmm, I get a similar error when trying to build lang/gcc46 on recent > 10-CURRENT: > > ---------------------------------------------------------------- > [..snip..] > Making all in include > gmake[4]: Entering directory > `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include' > mkdir -p ./x86_64-portbld-freebsd10.0/bits/stdc++.h.gch > /usr/ports/lang/gcc46/work/build/./gcc/xgcc -shared-libgcc > -B/usr/ports/lang/gcc46/work/build/./gcc -nostdinc++ > -L/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/src > -L/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/src/.libs > -B/usr/local/x86_64-portbld-freebsd10.0/bin/ > -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem > /usr/local/x86_64-portbld-freebsd10.0/include -isystem > /usr/local/x86_64-portbld-freebsd10.0/sys-include -x c++-header > -nostdinc++ -g -O2 -pipe -I/usr/local/include -fno-strict-aliasing > -I/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/x86_64-portbld-freebsd10.0 > -I/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include > -I/usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/libsupc++ -O2 > -g -std=gnu++0x > /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h > \ > -o x86_64-portbld-freebsd10.0/bits/stdc++.h.gch/O2ggnu++0x.gch > In file included from > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/chrono:38:0, > from > /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:100: > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/ratio:133:31: > error: macro "_Static_assert" passed 3 arguments, but takes just 2 > In file included from > /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:103:0: > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/future:376:39: > error: macro "_Static_assert" passed 4 arguments, but takes just 2 > In file included from > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/memory:85:0, > from > /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:81: > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h: > In constructor 'constexpr std::unique_ptr<_Tp, _Dp>::unique_ptr()': > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h:117:59: > error: constexpr constructor does not have empty body > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h: > In constructor 'constexpr std::unique_ptr<_Tp, > _Dp>::unique_ptr(std::nullptr_t)': > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h:139:59: > error: constexpr constructor does not have empty body > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h: > In constructor 'constexpr std::unique_ptr<_Tp [], _Dp>::unique_ptr()': > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h:279:59: > error: constexpr constructor does not have empty body > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h: > In constructor 'constexpr std::unique_ptr<_Tp [], > _Dp>::unique_ptr(std::nullptr_t)': > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/bits/unique_ptr.h:301:59: > error: constexpr constructor does not have empty body > In file included from > /usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include/cassert:45:0, > from > /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:34: > /usr/include/assert.h: At global scope: > /usr/include/assert.h:62:23: error: '_Static_assert' does not name a type > /usr/include/assert.h:62:23: error: '_Static_assert' does not name a type > gmake[4]: *** > [x86_64-portbld-freebsd10.0/bits/stdc++.h.gch/O2ggnu++0x.gch] Fehler 1 > gmake[4]: Leaving directory > `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3/include' > gmake[3]: *** [all-recursive] Fehler 1 > gmake[3]: Leaving directory > `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3' > gmake[2]: *** [all] Fehler 2 > gmake[2]: Leaving directory > `/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libstdc++-v3' > gmake[1]: *** [all-target-libstdc++-v3] Fehler 2 > gmake[1]: Leaving directory `/usr/ports/lang/gcc46/work/build' > gmake: *** [bootstrap-lean] Fehler 2 > *** Error code 1 > Stop in /usr/ports/lang/gcc46. > ---------------------------------------------------------------- > > > I guess that this error could have something to do with r228902 from > 2011-12-26: > > /head/include/assert.h: As per C11, add static_assert() to. > > lang/gcc46 builts fine for me before this revision. What do you think > about it? This commit _is_ responsible for this failure. I see the same. (Added Ed@) Andreas From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 18:10:55 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7AF6106567D; Wed, 28 Dec 2011 18:10:55 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from mx0.hoeg.nl (mx0.hoeg.nl [IPv6:2a01:4f8:101:5343::aa]) by mx1.freebsd.org (Postfix) with ESMTP id 8369F8FC0A; Wed, 28 Dec 2011 18:10:55 +0000 (UTC) Received: by mx0.hoeg.nl (Postfix, from userid 1000) id BDD962A28CC9; Wed, 28 Dec 2011 19:10:54 +0100 (CET) Date: Wed, 28 Dec 2011 19:10:54 +0100 From: Ed Schouten To: Rainer Hurling Message-ID: <20111228181054.GF1895@hoeg.nl> References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vjQsMS/9MbKYGLq" Content-Disposition: inline In-Reply-To: <4EFB447D.3000808@gwdg.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Kostik Belousov , Current FreeBSD , "O. Hartmann" , Ports FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 18:10:56 -0000 --5vjQsMS/9MbKYGLq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Rainer Hurling , 20111228 17:31: > error: macro "_Static_assert" passed 3 arguments, but takes just 2 > In file included from /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc= ++-v3/include/precompiled/stdc++.h:103:0: Hmmm... This seems to apply to my changes. I will look into this tomorrow. Thanks for the report! --=20 Ed Schouten WWW: http://80386.nl/ --5vjQsMS/9MbKYGLq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQIcBAEBAgAGBQJO+1uuAAoJEG5e2P40kaK7+IgP/RYUpwNYocXjlLK/YRPYL+c4 ZTJ64JClGnDe2ovwZh2ZJRBHUNim9yWToLz0TtwSYhPHsz6r7rE/yK2WLlQHecuD DKT4vCx1xlAWxn3k9vV80mtH2AV2bXv7WrX5c/19nxhHX4Bm3gKhwDzBtUOrTi5V C06jusLynzQ0efh2ts5BtDHl8LwLtJskdJ9vqeMfwSDghpgKUkMzuvLMcG49PGUb XHHekHMlOIMsCGf6zpn7ShcCqAs0FEskXtXvYOCJ6Qm2GPJT6h9RHzEjg5RrwH7A hzr42OhKjWlV37ILlop7GvyrK9tE/v+zSBCi6HdzgBTlar6vI3yAPvechgg4AljW 09qR6VwBU6FV9csJqngN11pTpRXILVmrZ7bEwucHMuYhgtqFy8Dp/BOButKQkkM8 VoqeYDZZvw/gyLyclf+o7kNsMAev/QRnGZqPRDyiS6aRta3IaHL0b87RvxX9E7Ws 2i12WiLLW9+SkYT0U1gQ/wKsadB8K5sj/Q+uTZNgZVsS3vUN4Co+F/rkZmXSsD8a nuHVjbPnGmgKNS4Dx5g+QT1af13cL55DO76tJiiWNiHgMp2SIQyYzMgDl6aixe7z yMEfAYN3/V1sz9lFIybmCFatAZ/BEJtCo7UEPdE6a0JXn48SyTkGhKLk50M9Xq9e u/D4hqzz7WQ+ztjui/cX =BVid -----END PGP SIGNATURE----- --5vjQsMS/9MbKYGLq-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 18:21:09 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 494F2106566B; Wed, 28 Dec 2011 18:21:09 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id EFD2E8FC08; Wed, 28 Dec 2011 18:21:08 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1Rfy7f-00063u-H7>; Wed, 28 Dec 2011 19:21:07 +0100 Received: from e178027189.adsl.alicedsl.de ([85.178.27.189] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1Rfy7f-0004ZR-CG>; Wed, 28 Dec 2011 19:21:07 +0100 Message-ID: <4EFB5E0C.90302@zedat.fu-berlin.de> Date: Wed, 28 Dec 2011 19:21:00 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Ed Schouten References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> <20111228181054.GF1895@hoeg.nl> In-Reply-To: <20111228181054.GF1895@hoeg.nl> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF608E066953F0508D8FA1DE6" X-Originating-IP: 85.178.27.189 Cc: Kostik Belousov , Ports FreeBSD , Current FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 18:21:09 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF608E066953F0508D8FA1DE6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 12/28/11 19:10, schrieb Ed Schouten: > * Rainer Hurling , 20111228 17:31: >> error: macro "_Static_assert" passed 3 arguments, but takes just 2 >> In file included from /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libs= tdc++-v3/include/precompiled/stdc++.h:103:0: >=20 > Hmmm... This seems to apply to my changes. I will look into this > tomorrow. Thanks for the report! >=20 Be aware that the error produced by the linker I mentioned in the initial post occurs on FreeBSD 10 as well as FreeBSD 9.0. I already filed a PR about the problem of a non compiling lang/gcc46 today (ports/163672: lang/gcc46: make failed for lang/gcc46). For test puproses, I rebuild gcc46 on our FreeBSD 9.0 boxes - without any problem.= I guess, the commit r228902 has been done to FreeBSD 10.0 and not 9.0. Oliver --------------enigF608E066953F0508D8FA1DE6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO+14SAAoJEOgBcD7A/5N8xFwIAImN0nJNT5r8ZgXd+mML49Q6 Dn8f5NOAhLzvCJQGSwYOcpXJAQ1u4YDSKMU18vFxhqf5aXVgBGI0ZpxQY92n5f9a IEPVkgHdqaATAECAhoFvTe1BcyNpqMjWy+rZA8PFm9RNI7d5O4MnZmJoyBBEZgjZ pF4+rdj/b9yWDV7cEtEH+vPeyz4mZrIJLd+FZQHOd9t7UBk1o3WLyOs4xKbt+LdD PUADdMPU4/v0oARKvClDmOUakA7+E3b+c7iIq+05zbJT3xSfHGEr8+PKPaNDkhq7 gYpi0koabyJL2Z/u1l8liK+emYZxNF8NLbdnD1QAtXZGjk3B710hA4Bu4yODLWc= =9bln -----END PGP SIGNATURE----- --------------enigF608E066953F0508D8FA1DE6-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 18:31:39 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F219D106564A; Wed, 28 Dec 2011 18:31:39 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 5F9878FC08; Wed, 28 Dec 2011 18:31:38 +0000 (UTC) Received: from alf.home (alf.kiev.zoral.com.ua [10.1.1.177]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id pBSIVWA1023389 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Dec 2011 20:31:33 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from alf.home (kostik@localhost [127.0.0.1]) by alf.home (8.14.5/8.14.5) with ESMTP id pBSIVWbG009134; Wed, 28 Dec 2011 20:31:32 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by alf.home (8.14.5/8.14.5/Submit) id pBSIVWqI009133; Wed, 28 Dec 2011 20:31:32 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: alf.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 28 Dec 2011 20:31:32 +0200 From: Kostik Belousov To: "O. Hartmann" Message-ID: <20111228183132.GB50300@deviant.kiev.zoral.com.ua> References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> <20111228181054.GF1895@hoeg.nl> <4EFB5E0C.90302@zedat.fu-berlin.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="iusaYbnlLJ7wNIY3" Content-Disposition: inline In-Reply-To: <4EFB5E0C.90302@zedat.fu-berlin.de> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Ed Schouten , Ports FreeBSD , Current FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 18:31:40 -0000 --iusaYbnlLJ7wNIY3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 28, 2011 at 07:21:00PM +0100, O. Hartmann wrote: > Am 12/28/11 19:10, schrieb Ed Schouten: > > * Rainer Hurling , 20111228 17:31: > >> error: macro "_Static_assert" passed 3 arguments, but takes just 2 > >> In file included from /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libs= tdc++-v3/include/precompiled/stdc++.h:103:0: > >=20 > > Hmmm... This seems to apply to my changes. I will look into this > > tomorrow. Thanks for the report! > >=20 >=20 >=20 > Be aware that the error produced by the linker I mentioned in the > initial post occurs on FreeBSD 10 as well as FreeBSD 9.0. >=20 > I already filed a PR about the problem of a non compiling lang/gcc46 > today (ports/163672: lang/gcc46: make failed for lang/gcc46). For test > puproses, I rebuild gcc46 on our FreeBSD 9.0 boxes - without any problem. >=20 > I guess, the commit r228902 has been done to FreeBSD 10.0 and not 9.0. Obviously, linker error during the compilation of third-party software has nothing to do with compiler error occuring when building gcc. Do people ever read the texts of the messages ? --iusaYbnlLJ7wNIY3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk77YIQACgkQC3+MBN1Mb4jHvwCfYh5lVIlOwre8gb81j3cW7+/f qg0An0jYh76DfO+w0kaYO6y7agVJ12Hk =nOOL -----END PGP SIGNATURE----- --iusaYbnlLJ7wNIY3-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 19:14:20 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48FE2106566B for ; Wed, 28 Dec 2011 19:14:20 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1ECAF8FC0C for ; Wed, 28 Dec 2011 19:14:19 +0000 (UTC) Received: by pbcc3 with SMTP id c3so10720368pbc.13 for ; Wed, 28 Dec 2011 11:14:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=BoG+w7yM6Vm5MLyp2tV9jIOBUoxen4jp/RqrESwKGGE=; b=Cq7daCLSXhxD3tdEGlgKDfNE6IYywbyE89/+CgssLqZPCM9lqVzqmTLQATljpHjrop vy81XrQBBNYSxfbXZxZY4g1nMGC9ixQbkjTRBcvU/h/kQihtffRZeISM6j1WDnn5tR/W y+FeoS5f9t32Nkq5DDeYkv9+TvZJNys+bPnYk= MIME-Version: 1.0 Received: by 10.68.209.68 with SMTP id mk4mr48947620pbc.88.1325099659358; Wed, 28 Dec 2011 11:14:19 -0800 (PST) Sender: mdf356@gmail.com Received: by 10.68.208.167 with HTTP; Wed, 28 Dec 2011 11:14:19 -0800 (PST) In-Reply-To: References: <20111227215330.GI45484@redundancy.redundancy.org> <4EFB470D.3070309@gmx.de> Date: Wed, 28 Dec 2011 11:14:19 -0800 X-Google-Sender-Auth: 13iD09_1mvTC8vIEKrs8MI_Gaxo Message-ID: From: mdf@FreeBSD.org To: Maxim Khitrov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Matthias Andree , freebsd-current@freebsd.org Subject: Re: SU+J systems do not fsck themselves X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 19:14:20 -0000 On Wed, Dec 28, 2011 at 8:54 AM, Maxim Khitrov wrote: > On Wed, Dec 28, 2011 at 11:42 AM, Matthias Andree > wrote: >> Am 27.12.2011 22:53, schrieb David Thiel: >>> I've had multiple machines now (9.0-RC3, amd64, i386 and earlier >>> 9-CURRENT on ppc) running SU+J that have had unexplained panics and >>> crashes start happening relating to disk I/O. When I end up running a >>> full fsck, it keeps turning out that the disk is dirty and corrupted, >>> but no mechanism is in place with SU+J to detect and fix this. A bgfsck >>> never happens, but a manual fsck in single-user does indeed fix the >>> crashing and weird behavior. Others have tested their SU+J volumes and >>> found them to have errors as well. This makes me super nervous. >> >> The one thing I figured is that in the light of power outages, or >> crashing virtualization hosts, you really really really need to disable >> disk write caches, and this affects softupdates, journalling, asynch >> file systems, just about everything. >> >> The fact that makes matters worse is that journalling or softupdates >> allow you to mount a silently-corrupted file system, whereas the >> traditional UFS/UFS2 sync/asynch mounts will fsck themselves in the >> foreground, so they get fixed before the FS panics. >> >> So can you be sure that: >> >> - your driver, chip set and hard disk execute ordered writes in order, If they don't, it's a bug. Not that there isn't buggy firmware out there, but each layer of software does need to rely on the one below actually doing what it's promised. >> - your driver, chip set and hard disk actually write data to permanent >> storage BEFORE acknowledging a successful write? Not required by SU as they use an explicit BIO_FLUSH which should be handled by the driver. >> Whenever I fixed these issues, I had no more corruptions. >> >> For ata and sata, there are loader tunables you will want to set, >> hw.ata.wc=3D0 and kern.cam.ada.write_cache=3D0. This should not be necessary if the driver and firmware are not buggy. >> If your drives are under ada, ad, or ahci related control, try these >> settings. =A0For SCSI, use camcontrol to turn the write cache off. >> softupdates is supposed to rectify most of the performance penalties >> incurred. >> >> Note also that you needed to set ahci_load=3DYES and atapicam_load=3DYES= in >> 8.X, I've never bothered to check 7.X or 9.X WRT these settings. > > This is a bit off-topic, but I'm curious what the effect of NCQ is on > softupdates? Since that too has the ability to reorder writes to disk, > should it be disabled in addition to cache? SU doesn't care about write ordering, as long as everything before a BIO_FLUSH is really flushed by the time the BIO_FLUSH is acknowledged. Cheers, matthew > Also, I would say that if you are using a hardware raid controller > with a BBU, then allowing the use of controller's cache and write-back > policy should be safe for use with softupdates. Any caching mechanism, > for that matter, that has a separate power supply source should be ok. > For example, the Intel 320 SSDs have a few on-board capacitors that > are used to flush the cache in the event of a power loss. > > - Max > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 19:17:44 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 491C71065672; Wed, 28 Dec 2011 19:17:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id B2F7B8FC17; Wed, 28 Dec 2011 19:17:43 +0000 (UTC) Received: from alf.home (alf.kiev.zoral.com.ua [10.1.1.177]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id pBSJHe5u026413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Dec 2011 21:17:40 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from alf.home (kostik@localhost [127.0.0.1]) by alf.home (8.14.5/8.14.5) with ESMTP id pBSJHdnP009588; Wed, 28 Dec 2011 21:17:39 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by alf.home (8.14.5/8.14.5/Submit) id pBSJHd8n009587; Wed, 28 Dec 2011 21:17:39 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: alf.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 28 Dec 2011 21:17:39 +0200 From: Kostik Belousov To: mdf@freebsd.org Message-ID: <20111228191739.GC50300@deviant.kiev.zoral.com.ua> References: <20111227215330.GI45484@redundancy.redundancy.org> <4EFB470D.3070309@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EURhva3SXbTcVq/V" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Maxim Khitrov , Matthias Andree , freebsd-current@freebsd.org Subject: Re: SU+J systems do not fsck themselves X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 19:17:44 -0000 --EURhva3SXbTcVq/V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Dec 28, 2011 at 11:14:19AM -0800, mdf@freebsd.org wrote: > SU doesn't care about write ordering, as long as everything before a > BIO_FLUSH is really flushed by the time the BIO_FLUSH is acknowledged. No. SU and SU+J only require that write completed notification is issued when geom/driver layer guarantees that the block content is written to the stable storage. SU does not depend on non-reordering of writes in any way, as well as it does not issue BIO_FLUSH. --EURhva3SXbTcVq/V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk77a1MACgkQC3+MBN1Mb4hK+QCgjOV68X27ufdcR9iEQ3HTW3Sd HnAAn3PhjvVYKJpoGGulkvS/zYgzxz0H =RBAI -----END PGP SIGNATURE----- --EURhva3SXbTcVq/V-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 19:22:24 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D70B41065670; Wed, 28 Dec 2011 19:22:24 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id E724B8FC12; Wed, 28 Dec 2011 19:22:23 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so22417569wgb.31 for ; Wed, 28 Dec 2011 11:22:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5sdy1xrq57IZ0Up4cezmvqXN0kuJhLyCyDqz6ktRBsY=; b=bP3erh6ifEk3e+azNxf70bMhZihbkg9npO+6q8wUB3qM5KseDbyirbjTKcxfvTcjcb mNBWO0/RuYFxb8m66n0eTsUPRdtnW3Al6Yn3C5NXQv/VIQ1bPERxp1/B9iemnuWb16FV Kt1Qd+3HyYSyXF9V7crfgwlWRmOeCIzJ+1ZX8= MIME-Version: 1.0 Received: by 10.227.60.78 with SMTP id o14mr32540545wbh.9.1325100141377; Wed, 28 Dec 2011 11:22:21 -0800 (PST) Received: by 10.223.158.129 with HTTP; Wed, 28 Dec 2011 11:22:21 -0800 (PST) In-Reply-To: <4EFB18B7.8050207@unsane.co.uk> References: <4EF904F2.4020109@FreeBSD.org> <4EF953ED.9060905@fuzzwad.org> <4EF9B09A.4070103@freebsd.org> <4EFA1C9C.60601@FreeBSD.org> <4EFA7FD4.10600@freebsd.org> <4EFA8E01.6050101@FreeBSD.org> <4EFAB788.2040508@FreeBSD.org> <4EFB18B7.8050207@unsane.co.uk> Date: Wed, 28 Dec 2011 11:22:21 -0800 Message-ID: From: Kevin Oberman To: Vincent Hoffman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Lawrence Stewart , Adrian Chadd , Doug Barton , Ron McDowell , freebsd-current Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 19:22:24 -0000 On Wed, Dec 28, 2011 at 5:25 AM, Vincent Hoffman wrote: > On 28/12/2011 06:30, Doug Barton wrote: > > On 12/27/2011 22:08, Adrian Chadd wrote: > >> Hi, > >> > >> Why not just list the things that sysinstall did that people like, and > >> extract out / reimplement those bits? > > That's sounds great. As soon as that's done, we can remove sysinstall > > from the base. Until those things exist, removing it is premature. > > > In that case can I suggest a wiki page or other viewable/editable list > of desirable features from sysinstall? > I only used it for the basic disklayout and component install so I'm not > in a position to start it off or I would. > > Vince > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Why not just get the list from sysinstall? Distributions Install additional distribution sets Documentation installation Install FreeBSD Documentation set Packages Install pre-packaged software for FreeBSD Root Password Set the system manager's password Fdisk The disk Slice (PC-style partition) Editor Label The disk Label editor User Management Add user and group information Console Customize system console behavior Time Zone Set which time zone you're in Media Change the installation media type Mouse Configure your mouse Networking Configure additional network services Security Configure system security options Startup Configure system startup options TTYs Configure system ttys. Options View/Set various installation options HTML Docs Go to the HTML documentation menu (post-install) Load KLD Load a KLD from a floppy Several of these simply call other tools that will remain present, but several are internal to sysinstall. Fdisk and Label should be replaced by the gpart tools already in bsdinstall. A couple might be simply removed, but most are either useful or near essential, especially for new user. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 20:49:50 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFAAA106566B for ; Wed, 28 Dec 2011 20:49:50 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from sarah.protected-networks.net (sarah.protected-networks.net [IPv6:2001:470:1f07:4e1::1]) by mx1.freebsd.org (Postfix) with ESMTP id BC8678FC14 for ; Wed, 28 Dec 2011 20:49:50 +0000 (UTC) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [202.12.127.84]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "Iain Butler", Issuer "RSA Class 2 Personal CA" (verified OK)) (Authenticated sender: imb@protected-networks.net) by sarah.protected-networks.net (Postfix) with ESMTPSA id 77CEE61C9 for ; Wed, 28 Dec 2011 15:49:49 -0500 (EST) DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=ouc3lB0ztFG14FUZZqByPKxn6Qq/Ezz0R93ydScxMEobnxM5QnRAytVL2WQZbzJbN D7rM20iEl6MnyJ7t7CX9kk5ob5hpYmMdPbxM8mc7R2XVQ224LWx4XTeyD0l0P/W Message-ID: <4EFB80EC.9020000@protected-networks.net> Date: Wed, 28 Dec 2011 15:49:48 -0500 From: Michael Butler User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:9.0) Gecko/20111223 Thunderbird/9.0 MIME-Version: 1.0 To: FreeBSD Current X-Enigmail-Version: undefined OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: SVN -> CVS gateway stalled? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 20:49:51 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I noticed updates come from SVN today but haven't yet seen them in CVS. Is it busted again? imb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk77gOsACgkQQv9rrgRC1JJRowCgqnaVL7F6+LrS9QSayq2dQUM/ Ei8AoJqoZDG82ZabnpP6zlMZjTJj1L9x =7g4y -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 21:16:52 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D79FB106566B; Wed, 28 Dec 2011 21:16:52 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 748C18FC17; Wed, 28 Dec 2011 21:16:52 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:3df3:fd3e:2c60:3d1d]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id F26744AC1C; Thu, 29 Dec 2011 01:16:50 +0400 (MSK) Date: Thu, 29 Dec 2011 01:16:47 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <782213068.20111229011647@serebryakov.spb.ru> To: mdf@FreeBSD.org In-Reply-To: References: <20111227215330.GI45484@redundancy.redundancy.org> <4EFB470D.3070309@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Maxim Khitrov , Matthias Andree , freebsd-current@freebsd.org Subject: Re: SU+J systems do not fsck themselves X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 21:16:52 -0000 Hello, Mdf. You wrote 28 =E4=E5=EA=E0=E1=F0=FF 2011 =E3., 23:14:19: > Not required by SU as they use an explicit BIO_FLUSH which should be > handled by the driver. No, they don't. It was discussed here about month ago. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 22:35:58 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD8BC1065670 for ; Wed, 28 Dec 2011 22:35:58 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id C988B8FC13 for ; Wed, 28 Dec 2011 22:35:58 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Rg26I-000GIo-BV for freebsd-current@freebsd.org; Wed, 28 Dec 2011 22:35:58 +0000 Date: Thu, 29 Dec 2011 07:35:57 +0900 Message-ID: From: Randy Bush To: FreeBSD Current User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: grep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 22:35:58 -0000 FreeBSD ran.psg.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4: Sat Dec 24 12:33:51 UTC 2011 root@ran.psg.com:/usr/obj/usr/src/sys/RAN amd64 % echo foo | grep foo % so i am csupping hoping to pick up the fix. but what do i need to do so that the sucker can build a new kernel and world? randy From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 22:43:27 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70171106566C; Wed, 28 Dec 2011 22:43:27 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.freebsd.org (Postfix) with ESMTP id 53D408FC24; Wed, 28 Dec 2011 22:43:27 +0000 (UTC) Received: from [127.0.0.1] (proxy6.corp.yahoo.com [216.145.48.19]) by mrout1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id pBSMhFNs078860; Wed, 28 Dec 2011 14:43:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1325112196; bh=eUtiEJVYwuWI0ebh7qb0w4f5c2N8wpQqkxAi6j2rYEc=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version; b=Ye1tVtYvMB7bSM9VBCg0GcLCckKxlIiYLSeKqnGzuGWbaY0vs4mEHIKYX7A+kzoWB JGY8w8VI8CpIwptSL8kxs/4SsE0lnW3DIV2K+05DxFTfisv9CockxpTln8bTRL3Bz/ s32WDbPRlJd0BlgzLy9hgb+9+vCGsD4rZTYt7g28= From: Sean Bruno To: Michael Butler In-Reply-To: <4EFB80EC.9020000@protected-networks.net> References: <4EFB80EC.9020000@protected-networks.net> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-C/1raB5Bb21LhGlk++uM" Date: Wed, 28 Dec 2011 14:43:15 -0800 Message-ID: <1325112195.17645.13.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) X-Mailman-Approved-At: Wed, 28 Dec 2011 22:50:42 +0000 Cc: clusteradm Subject: Re: SVN -> CVS gateway stalled? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 22:43:27 -0000 --=-C/1raB5Bb21LhGlk++uM Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2011-12-28 at 12:49 -0800, Michael Butler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > I noticed updates come from SVN today but haven't yet seen them in CVS. > Is it busted again? >=20 Clusteradm@ can take a look at this ... I think. Sean --=-C/1raB5Bb21LhGlk++uM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAABAgAGBQJO+5t/AAoJEL2UHwafTLtOR08H/jLmNVh3m8YsIG05ViahuPyN CnflTCkYQpkZgDfDDRsLiCj/OWfDA86kn/L2BZysNHpllAzzGBsY0B78A2Y8LbiA Lddzc3ApE+zZjg6kOIJzrM62plOx/zsvZ7CjjBYBUrPIBdBHjjkkfY1RYfkAF0er AM3rvkgd7ardJyzDh9f2Ig3LrGZuauodYEoD/Nmnjogkr7KSJNbwgOxYMDc8V0TL /yJEqrEFSQ+teU1/HXnv9zqmiks1c5H0QqzmtQLdaI3om3se38iAlss8J6ix4Oaw 9vOSmdRhPTQpHf9K8xBt13oE2ppW+TQSNSt/YA/IVg9Rctr+cMlhS33YkIDL/fg= =d/oJ -----END PGP SIGNATURE----- --=-C/1raB5Bb21LhGlk++uM-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 22:52:41 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id A635D106564A for ; Wed, 28 Dec 2011 22:52:41 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 741B815464C; Wed, 28 Dec 2011 22:51:28 +0000 (UTC) Message-ID: <4EFB9D70.8040002@FreeBSD.org> Date: Wed, 28 Dec 2011 14:51:28 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Randy Bush References: In-Reply-To: X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: grep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 22:52:41 -0000 On 12/28/2011 14:35, Randy Bush wrote: > FreeBSD ran.psg.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4: Sat Dec 24 12:33:51 UTC 2011 root@ran.psg.com:/usr/obj/usr/src/sys/RAN amd64 > > % echo foo | grep foo > % > > so i am csupping hoping to pick up the fix. I'm using pretty recent -current, and it works for me. Are you by any chance using bsdgrep? (it's not the default) > but what do i need to do so > that the sucker can build a new kernel and world? It will probably be necessary to replace the grep binary after you update your source. If you're using bsdgrep try this in /usr/src/usr.bin/grep: make cleandir && make obj && make depend && make all && make install If you haven't enabled the option for bsdgrep in src.conf then do the same thing in /usr/src/gnu/usr.bin/grep. If neither of those produce a working grep, you've got bigger issues. hth, Doug -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 23:00:54 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6CEB106566B; Wed, 28 Dec 2011 23:00:54 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id A0A2A8FC0C; Wed, 28 Dec 2011 23:00:54 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Rg2UQ-000GOJ-CS; Wed, 28 Dec 2011 23:00:54 +0000 Date: Thu, 29 Dec 2011 08:00:53 +0900 Message-ID: From: Randy Bush To: Doug Barton In-Reply-To: <4EFB9D70.8040002@FreeBSD.org> References: <4EFB9D70.8040002@FreeBSD.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: FreeBSD Current Subject: Re: grep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 23:00:54 -0000 >> % echo foo | grep foo >> % > > I'm using pretty recent -current, and it works for me. Are you by any > chance using bsdgrep? (it's not the default) not to my knowledge > If you haven't enabled the option for bsdgrep in src.conf then do the > same thing in /usr/src/gnu/usr.bin/grep. > > make cleandir && make obj && make depend && make all && make install i guess that have bigger issues :( randy From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 23:03:24 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB4A01065672; Wed, 28 Dec 2011 23:03:24 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 954488FC17; Wed, 28 Dec 2011 23:03:24 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Rg2Wq-000GQR-2j; Wed, 28 Dec 2011 23:03:24 +0000 Date: Thu, 29 Dec 2011 08:03:23 +0900 Message-ID: From: Randy Bush To: Doug Barton In-Reply-To: <4EFB9D70.8040002@FreeBSD.org> References: <4EFB9D70.8040002@FreeBSD.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: FreeBSD Current Subject: Re: grep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 23:03:24 -0000 bsdgrep works, grep does not % echo foo | bsdgrep foo foo % echo foo | grep foo % From owner-freebsd-current@FreeBSD.ORG Wed Dec 28 23:37:33 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D39E6106564A for ; Wed, 28 Dec 2011 23:37:33 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (mail.farley.org [IPv6:2001:470:1f07:14d3:2::11]) by mx1.freebsd.org (Postfix) with ESMTP id 893128FC12 for ; Wed, 28 Dec 2011 23:37:33 +0000 (UTC) Received: from thor.farley.org (HPooka@thor.farley.org [IPv6:2001:470:1f07:14d3:1::5]) by mail.farley.org (8.14.5/8.14.5) with ESMTP id pBSNbWqJ004592; Wed, 28 Dec 2011 18:37:32 -0500 (EST) (envelope-from scf@FreeBSD.org) Date: Wed, 28 Dec 2011 18:37:32 -0500 (EST) From: "Sean C. Farley" To: Randy Bush In-Reply-To: Message-ID: References: <4EFB9D70.8040002@FreeBSD.org> User-Agent: Alpine 2.02 (BSF 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-1.5 required=4.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.farley.org Cc: FreeBSD Current Subject: Re: grep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 23:37:33 -0000 On Thu, 29 Dec 2011, Randy Bush wrote: > bsdgrep works, grep does not > > % echo foo | bsdgrep foo > foo > % echo foo | grep foo > % Make sure you do not have an alias or function for grep. I have once or twice in the past inadvertently created aliases or functions for grep that did nothing. That was a fun experience trying to find out why grep was ignoring me. ;) Sean -- scf@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 00:04:52 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83BB4106566C; Thu, 29 Dec 2011 00:04:52 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (unknown [IPv6:2001:5a8:4:7e72:4a5b:39ff:fe12:452]) by mx1.freebsd.org (Postfix) with ESMTP id 443138FC08; Thu, 29 Dec 2011 00:04:52 +0000 (UTC) Received: from chez.mckusick.com (localhost [127.0.0.1]) by chez.mckusick.com (8.14.3/8.14.3) with ESMTP id pBT04iQH012044; Wed, 28 Dec 2011 16:04:44 -0800 (PST) (envelope-from mckusick@chez.mckusick.com) Message-Id: <201112290004.pBT04iQH012044@chez.mckusick.com> To: Don Lewis In-reply-to: <201112152330.pBFNUqDe063464@gw.catspoiler.org> Date: Wed, 28 Dec 2011 16:04:44 -0800 From: Kirk McKusick X-Spam-Status: No, score=0.0 required=5.0 tests=MISSING_MID, UNPARSEABLE_RELAY autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on chez.mckusick.com X-Mailman-Approved-At: Thu, 29 Dec 2011 02:06:45 +0000 Cc: phk@phk.freebsd.dk, seanbru@yahoo-inc.com, current@freebsd.org Subject: Re: dogfooding over in clusteradm land X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 00:04:52 -0000 Rather than changing BKVASIZE, I would try running the cvs2svn conversion on a 16K/2K filesystem and see if that sorts out the problem. If it does, it tells us that doubling the main block size and reducing the number of buffers by half is the problem. If that is the problem, then we will have to increase the KVM allocated to the buffer cache. Kirk McKusick From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 06:21:40 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED1E3106564A for ; Thu, 29 Dec 2011 06:21:40 +0000 (UTC) (envelope-from jsa.bsd@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id A17508FC0A for ; Thu, 29 Dec 2011 06:21:40 +0000 (UTC) Received: by qcse13 with SMTP id e13so11742134qcs.13 for ; Wed, 28 Dec 2011 22:21:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=pDHMwSxbomuHS/vI4Pi8s275upPtn1Vzr3ROMIYkagQ=; b=wMOnhmCsxvFiB39Ou1LtaV6x3AbjlhxzaPlDUen0mdTGNM5N0HPfminCM2oo8VQtWB fXir7fqgWysnO0AvuC9PLum//e1NHegb+g4Iuiq8mzudZeYnmgNnqINSP9Na4ZDREmvy jhZO0KTWhM3mpgmkCqdPwFEUSUF7V1iZbyuss= Received: by 10.224.182.10 with SMTP id ca10mr35683887qab.1.1325138217081; Wed, 28 Dec 2011 21:56:57 -0800 (PST) Received: from pazuzu.wickedmachine.net ([76.5.150.155]) by mx.google.com with ESMTPS id ev2sm14893028qab.15.2011.12.28.21.56.56 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Dec 2011 21:56:56 -0800 (PST) Sender: "Joseph S. Atkinson" Message-ID: <4EFC0127.6030301@FreeBSD.org> Date: Thu, 29 Dec 2011 00:56:55 -0500 From: "Joseph S. Atkinson" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111224 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 06:21:41 -0000 I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the issue of cdda:// access. I can confirm this issues, but don't know enough about driver access to fix this myself. Doug Barton reports that cdcontrol(1) doesn't work for him, and mplayer and audactiy also display issues running as non-root. Under 9.0-RC3 r228843, I get these errors on boot with no disc present in /dev/cd0 at all. (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 00 (pass1:ahcich2:0:0:0): CAM status: ATA Status Error (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 These ports are fairly popular, but the problems may not lie exclusively with their assumptions about FreeBSD. I am running 10.0 on another machine specifically to test changes under src/sys/cam. I am worried that with the actual 9.0-RELEASE on the horizon, users will find show stopping problems using their disc drives. -- Joseph S. Atkinson Paellax Technology Group http://www.paellax.com/ -- Sent from my FreeBSD/GNOME laptop 'pazuzu'. From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 06:41:51 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AD55106564A for ; Thu, 29 Dec 2011 06:41:51 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 05A478FC08 for ; Thu, 29 Dec 2011 06:41:50 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so13696899obb.13 for ; Wed, 28 Dec 2011 22:41:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6gJpZ5e2cbd9/1+iv/B3uA9sVHBb5IMUUEgjKTwtfvE=; b=rwS/o0C6SKIL7MHGqCGHipN2hM869fj800DmqTs7xklLZD7qoKKJeq3R6mqRL0+lYh 9lMb7cYwnIWhkjLWAK+awQhkO9sImvyxXGyfFI7p3Gj2tKoguVSOXMnDPqbXe7RmGk/k GQjdHi9dgwUuY5yE5g9xAp8bxU51tGXX1b4jY= MIME-Version: 1.0 Received: by 10.182.1.67 with SMTP id 3mr30785799obk.31.1325140910562; Wed, 28 Dec 2011 22:41:50 -0800 (PST) Received: by 10.182.152.6 with HTTP; Wed, 28 Dec 2011 22:41:50 -0800 (PST) In-Reply-To: <4EFC0127.6030301@FreeBSD.org> References: <4EFC0127.6030301@FreeBSD.org> Date: Wed, 28 Dec 2011 22:41:50 -0800 Message-ID: From: Garrett Cooper To: "Joseph S. Atkinson" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 06:41:51 -0000 On Wed, Dec 28, 2011 at 9:56 PM, Joseph S. Atkinson wrote: > I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the > issue of cdda:// access. > > I can confirm this issues, but don't know enough about driver access to fix > this myself. Doug Barton reports that cdcontrol(1) doesn't work for him, and > mplayer and audactiy also display issues running as non-root. > > Under 9.0-RC3 r228843, I get these errors on boot with no disc present in > /dev/cd0 at all. > > (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 > 00 > (pass1:ahcich2:0:0:0): CAM status: ATA Status Error > (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) > (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 > > These ports are fairly popular, but the problems may not lie exclusively > with their assumptions about FreeBSD. I am running 10.0 on another machine > specifically to test changes under src/sys/cam. > > I am worried that with the actual 9.0-RELEASE on the horizon, users will > find show stopping problems using their disc drives. Try having users merge r228808 and r228847. If that works, then I would press re@ produce another RC that fixes this. Thanks, -Garrett PS This is coming from a user that was annoyed by this gap with the ATA_CAM code. From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 10:31:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1869F106566B for ; Thu, 29 Dec 2011 10:31:32 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp07.smtpout.orange.fr [80.12.242.129]) by mx1.freebsd.org (Postfix) with ESMTP id AE5618FC0C for ; Thu, 29 Dec 2011 10:31:31 +0000 (UTC) Received: from localhost ([92.162.2.141]) by mwinf5d13 with ME id EyXU1i00U32Ybas03yXVgx; Thu, 29 Dec 2011 11:31:30 +0100 Message-ID: <4EFC4180.2090305@orange.fr> Date: Thu, 29 Dec 2011 11:31:28 +0100 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.25) Gecko/20111228 Thunderbird/3.1.17 MIME-Version: 1.0 To: FreeBSD Current , clusteradm Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: svn2cvs gateway down (one more time..) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 10:31:32 -0000 On 12/28/2011 23:43, Sean Bruno wrote: > On Wed, 2011-12-28 at 12:49 -0800, Michael Butler wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I noticed updates come from SVN today but haven't yet seen them in CVS. >> Is it busted again? >> > > > Clusteradm@ can take a look at this ... I think. > > Sean Is someone in charge ? Seems to be down since 2011.12.27.10.34.00 UTC (r228910) TIA CBu From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 10:48:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E4FD106566C; Thu, 29 Dec 2011 10:48:32 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from fmailer.gwdg.de (fmailer.gwdg.de [134.76.11.16]) by mx1.freebsd.org (Postfix) with ESMTP id 275238FC13; Thu, 29 Dec 2011 10:48:31 +0000 (UTC) Received: from pd951ce14.dip.t-dialin.net ([217.81.206.20] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1RgDVL-0003Js-Rq; Thu, 29 Dec 2011 11:46:36 +0100 Message-ID: <4EFC4579.6060608@gwdg.de> Date: Thu, 29 Dec 2011 11:48:25 +0100 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Kostik Belousov References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> <20111228181054.GF1895@hoeg.nl> <4EFB5E0C.90302@zedat.fu-berlin.de> <20111228183132.GB50300@deviant.kiev.zoral.com.ua> In-Reply-To: <20111228183132.GB50300@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: Ed Schouten , Current FreeBSD , "O. Hartmann" , Ports FreeBSD Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 10:48:32 -0000 On 28.12.2011 19:31 (UTC+1), Kostik Belousov wrote: > On Wed, Dec 28, 2011 at 07:21:00PM +0100, O. Hartmann wrote: >> Am 12/28/11 19:10, schrieb Ed Schouten: >>> * Rainer Hurling, 20111228 17:31: >>>> error: macro "_Static_assert" passed 3 arguments, but takes just 2 >>>> In file included from /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/precompiled/stdc++.h:103:0: >>> >>> Hmmm... This seems to apply to my changes. I will look into this >>> tomorrow. Thanks for the report! >>> >> >> >> Be aware that the error produced by the linker I mentioned in the >> initial post occurs on FreeBSD 10 as well as FreeBSD 9.0. >> >> I already filed a PR about the problem of a non compiling lang/gcc46 >> today (ports/163672: lang/gcc46: make failed for lang/gcc46). For test >> puproses, I rebuild gcc46 on our FreeBSD 9.0 boxes - without any problem. >> >> I guess, the commit r228902 has been done to FreeBSD 10.0 and not 9.0. > > Obviously, linker error during the compilation of third-party software > has nothing to do with compiler error occuring when building gcc. > > Do people ever read the texts of the messages ? Kostik, probably you are right. I had read the messages, but there are some strange errors with gcc46 on head for two days now, which leaded me in the wrong direction. So sorry for erroneously 'hijacking' this thread with another problem most certain only existing in head. I found another trail, which hopefully is more usefull for solving the problem Oliver described. Whe I try to build lang/lua I get this error: [..snip..] cc -o liblua.so -O2 -fno-strict-aliasing -pipe -msse3 -Wall -DLUA_USE_LINUX -shared -Wl,-soname=liblua-5.1.so.1 lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o ranlib liblua.a cc -o lua lua.o liblua.a -lm -Wl,-E -lreadline cc -o luac luac.o print.o liblua.a -lm -Wl,-E -lreadline /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' can not be used when making a shared object; recompile with -fPIC lapi.o: could not read symbols: Bad value *** Error code 1 It also gives a linker error, almost the same relocation is named. This does only happen with option '-msse3' enabled in /etc/make.conf: CFLAGS= -O2 -fno-strict-aliasing -pipe -msse3 Using CLFAGS without -msse3 (default) works well: CFLAGS= -O2 -fno-strict-aliasing -pipe The systems processor, were this happens, is a CPU: AMD Phenom(tm) II X6 1090T Processor (3214.32-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100fa0 Family = 10 Model = a Stepping = 0 Features=0x178bfbff Features2=0x802009 AMD Features=0xee500800 AMD Features2=0x37ff TSC: P-state invariant, performance statistics FreeBSD 10-CURRENT (amd64) r228920 In hope of a more belonging posting, Rainer From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 10:54:33 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AF58106564A; Thu, 29 Dec 2011 10:54:33 +0000 (UTC) (envelope-from simon@FreeBSD.org) Received: from emx.nitro.dk (emx.nitro.dk [IPv6:2a01:4f8:120:7384::102]) by mx1.freebsd.org (Postfix) with ESMTP id 04B3C8FC0A; Thu, 29 Dec 2011 10:54:33 +0000 (UTC) Received: from mailscan.leto.nitro.dk (mailscan.leto.nitro.dk [127.0.1.4]) by emx.nitro.dk (Postfix) with ESMTP id 3EDEF19206A; Thu, 29 Dec 2011 10:54:32 +0000 (UTC) Received: from emx.nitro.dk ([127.0.1.2]) by mailscan.leto.nitro.dk (mailscan.leto.nitro.dk [127.0.1.4]) (amavisd-new, port 10024) with LMTP id VINd_5TqewOr; Thu, 29 Dec 2011 10:54:30 +0000 (UTC) Received: from [192.168.4.21] (unknown [89.100.56.44]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by emx.nitro.dk (Postfix) with ESMTPSA id 33DCE192069; Thu, 29 Dec 2011 10:54:30 +0000 (UTC) From: "Simon L. B. Nielsen" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 29 Dec 2011 10:54:29 +0000 Message-Id: To: stable@freebsd.org, current@freebsd.org Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) Cc: Subject: svn2cvs fixed again X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 10:54:33 -0000 Hey, svn2cvs has been fixed and is catching up now. Mirrors should be fully = up to date within a couple of hours (depending on their sync schedule). --=20 Simon L. B. Nielsen From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 11:19:44 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68CCA1065692; Thu, 29 Dec 2011 11:19:44 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 0C0E78FC1E; Thu, 29 Dec 2011 11:19:42 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1RgE1N-0000gI-0q>; Thu, 29 Dec 2011 12:19:41 +0100 Received: from e178008034.adsl.alicedsl.de ([85.178.8.34] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1RgE1M-0004ul-Q9>; Thu, 29 Dec 2011 12:19:41 +0100 Message-ID: <4EFC4CCC.3050507@zedat.fu-berlin.de> Date: Thu, 29 Dec 2011 12:19:40 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Rainer Hurling References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> <20111228181054.GF1895@hoeg.nl> <4EFB5E0C.90302@zedat.fu-berlin.de> <20111228183132.GB50300@deviant.kiev.zoral.com.ua> <4EFC4579.6060608@gwdg.de> In-Reply-To: <4EFC4579.6060608@gwdg.de> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD84A0952DF1FB12075D23DE5" X-Originating-IP: 85.178.8.34 Cc: Kostik Belousov , Ed Schouten , Current FreeBSD , Ports FreeBSD Subject: lang/lua: /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' can not be used when making a shared object; recompile with -fPIC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 11:19:44 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD84A0952DF1FB12075D23DE5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 12/29/11 11:48, schrieb Rainer Hurling: > On 28.12.2011 19:31 (UTC+1), Kostik Belousov wrote: >> On Wed, Dec 28, 2011 at 07:21:00PM +0100, O. Hartmann wrote: >>> Am 12/28/11 19:10, schrieb Ed Schouten: >>>> * Rainer Hurling, 20111228 17:31: >>>>> error: macro "_Static_assert" passed 3 arguments, but takes just 2 >>>>> In file included from >>>>> /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/pr= ecompiled/stdc++.h:103:0: >>>>> >>>> >>>> Hmmm... This seems to apply to my changes. I will look into this >>>> tomorrow. Thanks for the report! >>>> >>> >>> >>> Be aware that the error produced by the linker I mentioned in the >>> initial post occurs on FreeBSD 10 as well as FreeBSD 9.0. >>> >>> I already filed a PR about the problem of a non compiling lang/gcc46 >>> today (ports/163672: lang/gcc46: make failed for lang/gcc46). For tes= t >>> puproses, I rebuild gcc46 on our FreeBSD 9.0 boxes - without any >>> problem. >>> >>> I guess, the commit r228902 has been done to FreeBSD 10.0 and not 9.0= =2E >> >> Obviously, linker error during the compilation of third-party software= >> has nothing to do with compiler error occuring when building gcc. >> >> Do people ever read the texts of the messages ? >=20 > Kostik, probably you are right. I had read the messages, but there are > some strange errors with gcc46 on head for two days now, which leaded m= e > in the wrong direction. So sorry for erroneously 'hijacking' this threa= d > with another problem most certain only existing in head. >=20 >=20 > I found another trail, which hopefully is more usefull for solving the > problem Oliver described. >=20 > Whe I try to build lang/lua I get this error: >=20 > [..snip..] > cc -o liblua.so -O2 -fno-strict-aliasing -pipe -msse3 -Wall > -DLUA_USE_LINUX -shared -Wl,-soname=3Dliblua-5.1.so.1 lapi.o lcode.o > ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o= > lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o > lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o > lstrlib.o loadlib.o linit.o > ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o > llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.= o > ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o > lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o > ranlib liblua.a > cc -o lua lua.o liblua.a -lm -Wl,-E -lreadline > cc -o luac luac.o print.o liblua.a -lm -Wl,-E -lreadline > /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' > can not be used when making a shared object; recompile with -fPIC > lapi.o: could not read symbols: Bad value > *** Error code 1 >=20 >=20 > It also gives a linker error, almost the same relocation is named. This= > does only happen with option '-msse3' enabled in /etc/make.conf: >=20 > CFLAGS=3D -O2 -fno-strict-aliasing -pipe -msse3 >=20 > Using CLFAGS without -msse3 (default) works well: >=20 > CFLAGS=3D -O2 -fno-strict-aliasing -pipe >=20 >=20 > The systems processor, were this happens, is a >=20 > CPU: AMD Phenom(tm) II X6 1090T Processor (3214.32-MHz K8-class CPU) > Origin =3D "AuthenticAMD" Id =3D 0x100fa0 Family =3D 10 Model =3D = a > Stepping =3D 0 > Features=3D0x178bfbff >=20 > Features2=3D0x802009 > AMD > Features=3D0xee500800 > AMD > Features2=3D0x37ff >=20 > TSC: P-state invariant, performance statistics >=20 > FreeBSD 10-CURRENT (amd64) r228920 >=20 > In hope of a more belonging posting, > Rainer > _______________________________________________ WOW! I tried lang/lua on FreeBSD 9.0-PRE and see exactly this error: clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINU= X -c print.c clang -o liblua.so -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX -shared -Wl,-soname=3Dliblua-5.1.so.1 lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' can not be used when making a shared object; recompile with -fPIC lapi.o: could not read symbols: Bad value clang: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o ranlib liblua.a 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 1 Stop in /usr/ports/lang/lua. =3D=3D=3D>>> make failed for lang/lua =3D=3D=3D>>> Aborting update On FreeBSD 10.0-CURRENT I see this: clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX= -c linit.c ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o ranlib liblua.a clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX= -c lua.c clang -o lua lua.o liblua.a -lm -Wl,-E -lreadline clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX= -c luac.c clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX= -c print.c clang -o luac luac.o print.o liblua.a -lm -Wl,-E -lreadline clang -o liblua.so -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX -shared -Wl,-soname=3Dliblua-5.1.so.1 lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' can not be used when making a shared object; recompile with -fPIC lapi.o: could not read symbols: Bad value clang: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. *** Error code 1 Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. *** Error code 1 Stop in /usr/ports/lang/lua/work/lua-5.1.4. *** Error code 1 Stop in /usr/ports/lang/lua. =3D=3D=3D>>> make failed for lang/lua =3D=3D=3D>>> Aborting update Terminated Terminated This is very strange! Regards, Oliver --------------enigD84A0952DF1FB12075D23DE5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO/EzMAAoJEOgBcD7A/5N8aroIAKBHS+QwuohlXIi25B6zFU6I SWw0GV3NEWOa8IAarrPYSjG8qUAW07XNsmv+TAEuXwetalD0AMp0yn8p39SZ/2MA i9a0e8XkRWl5XW4VRgjSDSsN9q3vkiCwZRa+iAvYyFj1N53uo2haGSqfUf8P4Tan g9PGSD3pILoDw0NoG3gtVN3kEuWegl4IQa9c/szplxFZ8AKS7yDuc9QKgNWnPySZ CFkguebT2u8GCBUqSq04sl7MNJePP2/EzCnvNPF2pKpmy8p9DvW2bZnZFhjbmXCO DqswMP9IuXqzL/2Sd2atLQKZbShpReY5lIZCu2JF0QGUQ9p0wnD8gwnJWFJFe0I= =r/UC -----END PGP SIGNATURE----- --------------enigD84A0952DF1FB12075D23DE5-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 11:52:47 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF21C106564A for ; Thu, 29 Dec 2011 11:52:47 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp08.smtpout.orange.fr [80.12.242.130]) by mx1.freebsd.org (Postfix) with ESMTP id 7F2A28FC0C for ; Thu, 29 Dec 2011 11:52:41 +0000 (UTC) Received: from localhost ([92.162.2.141]) by mwinf5d16 with ME id Ezsf1i00s32Ybas03zsfCm; Thu, 29 Dec 2011 12:52:40 +0100 Message-ID: <4EFC5487.3080709@orange.fr> Date: Thu, 29 Dec 2011 12:52:39 +0100 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.25) Gecko/20111228 Thunderbird/3.1.17 MIME-Version: 1.0 To: Garrett Cooper References: <4EFC0127.6030301@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Joseph S. Atkinson" , freebsd-current@freebsd.org Subject: Re: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 11:52:48 -0000 On 12/29/2011 07:41, Garrett Cooper wrote: > On Wed, Dec 28, 2011 at 9:56 PM, Joseph S. Atkinson wrote: >> I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the >> issue of cdda:// access. >> >> I can confirm this issues, but don't know enough about driver access to fix >> this myself. Doug Barton reports that cdcontrol(1) doesn't work for him, and >> mplayer and audactiy also display issues running as non-root. >> >> Under 9.0-RC3 r228843, I get these errors on boot with no disc present in >> /dev/cd0 at all. >> >> (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 >> 00 >> (pass1:ahcich2:0:0:0): CAM status: ATA Status Error >> (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) >> (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 >> >> These ports are fairly popular, but the problems may not lie exclusively >> with their assumptions about FreeBSD. I am running 10.0 on another machine >> specifically to test changes under src/sys/cam. >> >> I am worried that with the actual 9.0-RELEASE on the horizon, users will >> find show stopping problems using their disc drives. > > Try having users merge r228808 and r228847. If that works, then I > would press re@ produce another RC that fixes this. > Thanks, > -Garrett > > PS This is coming from a user that was annoyed by this gap with the > ATA_CAM code. As the submitter of ports/162190, I would firstly ask: Is the problem corrected by r228808 and r228847 in 10.0-CURRENT ? If not merging to 9.0 is useless. If yes I could test. CBu From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 11:59:11 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C59C0106564A; Thu, 29 Dec 2011 11:59:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 275C48FC08; Thu, 29 Dec 2011 11:59:10 +0000 (UTC) Received: from alf.home (alf.kiev.zoral.com.ua [10.1.1.177]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id pBTBx4IA053135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Dec 2011 13:59:04 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from alf.home (kostik@localhost [127.0.0.1]) by alf.home (8.14.5/8.14.5) with ESMTP id pBTBx4oN017116; Thu, 29 Dec 2011 13:59:04 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by alf.home (8.14.5/8.14.5/Submit) id pBTBx4Oo017115; Thu, 29 Dec 2011 13:59:04 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: alf.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 29 Dec 2011 13:59:04 +0200 From: Kostik Belousov To: "O. Hartmann" Message-ID: <20111229115904.GH50300@deviant.kiev.zoral.com.ua> References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> <20111228181054.GF1895@hoeg.nl> <4EFB5E0C.90302@zedat.fu-berlin.de> <20111228183132.GB50300@deviant.kiev.zoral.com.ua> <4EFC4579.6060608@gwdg.de> <4EFC4CCC.3050507@zedat.fu-berlin.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EUBiG/BDWfQOM97z" Content-Disposition: inline In-Reply-To: <4EFC4CCC.3050507@zedat.fu-berlin.de> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Ed Schouten , Ports FreeBSD , Current FreeBSD Subject: Re: lang/lua: /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' can not be used when making a shared object; recompile with -fPIC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 11:59:11 -0000 --EUBiG/BDWfQOM97z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 29, 2011 at 12:19:40PM +0100, O. Hartmann wrote: > Am 12/29/11 11:48, schrieb Rainer Hurling: > > On 28.12.2011 19:31 (UTC+1), Kostik Belousov wrote: > >> On Wed, Dec 28, 2011 at 07:21:00PM +0100, O. Hartmann wrote: > >>> Am 12/28/11 19:10, schrieb Ed Schouten: > >>>> * Rainer Hurling, 20111228 17:31: > >>>>> error: macro "_Static_assert" passed 3 arguments, but takes just 2 > >>>>> In file included from > >>>>> /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/pr= ecompiled/stdc++.h:103:0: > >>>>> > >>>> > >>>> Hmmm... This seems to apply to my changes. I will look into this > >>>> tomorrow. Thanks for the report! > >>>> > >>> > >>> > >>> Be aware that the error produced by the linker I mentioned in the > >>> initial post occurs on FreeBSD 10 as well as FreeBSD 9.0. > >>> > >>> I already filed a PR about the problem of a non compiling lang/gcc46 > >>> today (ports/163672: lang/gcc46: make failed for lang/gcc46). For test > >>> puproses, I rebuild gcc46 on our FreeBSD 9.0 boxes - without any > >>> problem. > >>> > >>> I guess, the commit r228902 has been done to FreeBSD 10.0 and not 9.0. > >> > >> Obviously, linker error during the compilation of third-party software > >> has nothing to do with compiler error occuring when building gcc. > >> > >> Do people ever read the texts of the messages ? > >=20 > > Kostik, probably you are right. I had read the messages, but there are > > some strange errors with gcc46 on head for two days now, which leaded me > > in the wrong direction. So sorry for erroneously 'hijacking' this thread > > with another problem most certain only existing in head. > >=20 > >=20 > > I found another trail, which hopefully is more usefull for solving the > > problem Oliver described. > >=20 > > Whe I try to build lang/lua I get this error: > >=20 > > [..snip..] > > cc -o liblua.so -O2 -fno-strict-aliasing -pipe -msse3 -Wall > > -DLUA_USE_LINUX -shared -Wl,-soname=3Dliblua-5.1.so.1 lapi.o lcode.o > > ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o > > lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o > > lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o > > lstrlib.o loadlib.o linit.o > > ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o > > llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o > > ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o > > lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o > > ranlib liblua.a > > cc -o lua lua.o liblua.a -lm -Wl,-E -lreadline > > cc -o luac luac.o print.o liblua.a -lm -Wl,-E -lreadline > > /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' > > can not be used when making a shared object; recompile with -fPIC > > lapi.o: could not read symbols: Bad value > > *** Error code 1 > >=20 > >=20 > > It also gives a linker error, almost the same relocation is named. This > > does only happen with option '-msse3' enabled in /etc/make.conf: > >=20 > > CFLAGS=3D -O2 -fno-strict-aliasing -pipe -msse3 > >=20 > > Using CLFAGS without -msse3 (default) works well: > >=20 > > CFLAGS=3D -O2 -fno-strict-aliasing -pipe > >=20 > >=20 > > The systems processor, were this happens, is a > >=20 > > CPU: AMD Phenom(tm) II X6 1090T Processor (3214.32-MHz K8-class CPU) > > Origin =3D "AuthenticAMD" Id =3D 0x100fa0 Family =3D 10 Model =3D a > > Stepping =3D 0 > > Features=3D0x178bfbff > >=20 > > Features2=3D0x802009 > > AMD > > Features=3D0xee500800 > > AMD > > Features2=3D0x37ff > >=20 > > TSC: P-state invariant, performance statistics > >=20 > > FreeBSD 10-CURRENT (amd64) r228920 > >=20 > > In hope of a more belonging posting, > > Rainer > > _______________________________________________ >=20 >=20 > WOW! >=20 > I tried lang/lua on FreeBSD 9.0-PRE and see exactly this error: >=20 > clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX > -c print.c > clang -o liblua.so -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall > -DLUA_USE_LINUX -shared -Wl,-soname=3Dliblua-5.1.so.1 lapi.o lcode.o > ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o > lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o > lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o > lstrlib.o loadlib.o linit.o > /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' > can not be used when making a shared object; recompile with -fPIC > lapi.o: could not read symbols: Bad value > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > *** Error code 1 > ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o > llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o > ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o > lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o > ranlib liblua.a > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 1 >=20 > Stop in /usr/ports/lang/lua. >=20 > =3D=3D=3D>>> make failed for lang/lua > =3D=3D=3D>>> Aborting update >=20 >=20 >=20 > On FreeBSD 10.0-CURRENT I see this: > clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX > -c linit.c > ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o > llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o > ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o > lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o > ranlib liblua.a > clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX > -c lua.c > clang -o lua lua.o liblua.a -lm -Wl,-E -lreadline > clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX > -c luac.c > clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LINUX > -c print.c > clang -o luac luac.o print.o liblua.a -lm -Wl,-E -lreadline > clang -o liblua.so -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall > -DLUA_USE_LINUX -shared -Wl,-soname=3Dliblua-5.1.so.1 lapi.o lcode.o > ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o > lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o > lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o > lstrlib.o loadlib.o linit.o > /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' > can not be used when making a shared object; recompile with -fPIC > lapi.o: could not read symbols: Bad value > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > *** Error code 1 >=20 > Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. > *** Error code 1 >=20 > Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. > *** Error code 1 >=20 > Stop in /usr/ports/lang/lua/work/lua-5.1.4. > *** Error code 1 >=20 > Stop in /usr/ports/lang/lua. >=20 > =3D=3D=3D>>> make failed for lang/lua > =3D=3D=3D>>> Aborting update >=20 > Terminated > Terminated >=20 > This is very strange! What is strange ? It is exactly the same problem as in the first message started this thread. You must use -fPIC flag for compiler when compiling objects that shall be later linked into dso. So, for lua case, -fPIC must be present on the cc -c command line. Again, -msse3 is not relevant there. Presense of -msse3 flag might casually change compiler output to generate the relocation unsuitable for dso, but compiler has full permit to do so without -msse3 as well. Issue with broken gcc 4.6 build is different, it is indeed due to recent changes in system headers due to C11 compliance work. Hopefully, Ed will fix it. --EUBiG/BDWfQOM97z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk78VggACgkQC3+MBN1Mb4hN4wCfSZQ3tHL8OQ+3k8zq8lNr+NfK mvkAoMd0mvwXqpjlLoomyIDqb0xkeXF4 =ypP7 -----END PGP SIGNATURE----- --EUBiG/BDWfQOM97z-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 12:19:27 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C101A106564A; Thu, 29 Dec 2011 12:19:27 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 62AC08FC17; Thu, 29 Dec 2011 12:19:27 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1RgExC-0007G7-7Q>; Thu, 29 Dec 2011 13:19:26 +0100 Received: from e178008034.adsl.alicedsl.de ([85.178.8.34] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1RgExC-0007kE-03>; Thu, 29 Dec 2011 13:19:26 +0100 Message-ID: <4EFC5ACD.5010701@zedat.fu-berlin.de> Date: Thu, 29 Dec 2011 13:19:25 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Kostik Belousov References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> <20111228181054.GF1895@hoeg.nl> <4EFB5E0C.90302@zedat.fu-berlin.de> <20111228183132.GB50300@deviant.kiev.zoral.com.ua> <4EFC4579.6060608@gwdg.de> <4EFC4CCC.3050507@zedat.fu-berlin.de> <20111229115904.GH50300@deviant.kiev.zoral.com.ua> In-Reply-To: <20111229115904.GH50300@deviant.kiev.zoral.com.ua> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8486F0C1902EA172FA10AF3C" X-Originating-IP: 85.178.8.34 Cc: Ed Schouten , Current FreeBSD , Ports FreeBSD Subject: Re: lang/lua: /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' can not be used when making a shared object; recompile with -fPIC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 12:19:27 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8486F0C1902EA172FA10AF3C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 12/29/11 12:59, schrieb Kostik Belousov: > On Thu, Dec 29, 2011 at 12:19:40PM +0100, O. Hartmann wrote: >> Am 12/29/11 11:48, schrieb Rainer Hurling: >>> On 28.12.2011 19:31 (UTC+1), Kostik Belousov wrote: >>>> On Wed, Dec 28, 2011 at 07:21:00PM +0100, O. Hartmann wrote: >>>>> Am 12/28/11 19:10, schrieb Ed Schouten: >>>>>> * Rainer Hurling, 20111228 17:31: >>>>>>> error: macro "_Static_assert" passed 3 arguments, but takes just = 2 >>>>>>> In file included from >>>>>>> /usr/ports/lang/gcc46/work/gcc-4.6-20111209/libstdc++-v3/include/= precompiled/stdc++.h:103:0: >>>>>>> >>>>>> >>>>>> Hmmm... This seems to apply to my changes. I will look into this >>>>>> tomorrow. Thanks for the report! >>>>>> >>>>> >>>>> >>>>> Be aware that the error produced by the linker I mentioned in the >>>>> initial post occurs on FreeBSD 10 as well as FreeBSD 9.0. >>>>> >>>>> I already filed a PR about the problem of a non compiling lang/gcc4= 6 >>>>> today (ports/163672: lang/gcc46: make failed for lang/gcc46). For t= est >>>>> puproses, I rebuild gcc46 on our FreeBSD 9.0 boxes - without any >>>>> problem. >>>>> >>>>> I guess, the commit r228902 has been done to FreeBSD 10.0 and not 9= =2E0. >>>> >>>> Obviously, linker error during the compilation of third-party softwa= re >>>> has nothing to do with compiler error occuring when building gcc. >>>> >>>> Do people ever read the texts of the messages ? >>> >>> Kostik, probably you are right. I had read the messages, but there ar= e >>> some strange errors with gcc46 on head for two days now, which leaded= me >>> in the wrong direction. So sorry for erroneously 'hijacking' this thr= ead >>> with another problem most certain only existing in head. >>> >>> >>> I found another trail, which hopefully is more usefull for solving th= e >>> problem Oliver described. >>> >>> Whe I try to build lang/lua I get this error: >>> >>> [..snip..] >>> cc -o liblua.so -O2 -fno-strict-aliasing -pipe -msse3 -Wall >>> -DLUA_USE_LINUX -shared -Wl,-soname=3Dliblua-5.1.so.1 lapi.o lcode.= o >>> ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes= =2Eo >>> lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o >>> lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o >>> lstrlib.o loadlib.o linit.o >>> ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o >>> llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltabl= e.o >>> ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o >>> lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o >>> ranlib liblua.a >>> cc -o lua lua.o liblua.a -lm -Wl,-E -lreadline >>> cc -o luac luac.o print.o liblua.a -lm -Wl,-E -lreadline >>> /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_'= >>> can not be used when making a shared object; recompile with -fPIC >>> lapi.o: could not read symbols: Bad value >>> *** Error code 1 >>> >>> >>> It also gives a linker error, almost the same relocation is named. Th= is >>> does only happen with option '-msse3' enabled in /etc/make.conf: >>> >>> CFLAGS=3D -O2 -fno-strict-aliasing -pipe -msse3 >>> >>> Using CLFAGS without -msse3 (default) works well: >>> >>> CFLAGS=3D -O2 -fno-strict-aliasing -pipe >>> >>> >>> The systems processor, were this happens, is a >>> >>> CPU: AMD Phenom(tm) II X6 1090T Processor (3214.32-MHz K8-class CPU) >>> Origin =3D "AuthenticAMD" Id =3D 0x100fa0 Family =3D 10 Model =3D= a >>> Stepping =3D 0 >>> Features=3D0x178bfbff >>> >>> Features2=3D0x802009 >>> AMD >>> Features=3D0xee500800 >>> AMD >>> Features2=3D0x37ff >>> >>> TSC: P-state invariant, performance statistics >>> >>> FreeBSD 10-CURRENT (amd64) r228920 >>> >>> In hope of a more belonging posting, >>> Rainer >>> _______________________________________________ >> >> >> WOW! >> >> I tried lang/lua on FreeBSD 9.0-PRE and see exactly this error: >> >> clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_L= INUX >> -c print.c >> clang -o liblua.so -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wal= l >> -DLUA_USE_LINUX -shared -Wl,-soname=3Dliblua-5.1.so.1 lapi.o lcode.o= >> ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.= o >> lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o >> lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o >> lstrlib.o loadlib.o linit.o >> /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' >> can not be used when making a shared object; recompile with -fPIC >> lapi.o: could not read symbols: Bad value >> clang: error: linker command failed with exit code 1 (use -v to see >> invocation) >> *** Error code 1 >> ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o >> llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable= =2Eo >> ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o >> lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o >> ranlib liblua.a >> 1 error >> *** Error code 2 >> 1 error >> *** Error code 2 >> 1 error >> *** Error code 1 >> >> Stop in /usr/ports/lang/lua. >> >> =3D=3D=3D>>> make failed for lang/lua >> =3D=3D=3D>>> Aborting update >> >> >> >> On FreeBSD 10.0-CURRENT I see this: >> clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LI= NUX >> -c linit.c >> ar rcu liblua.a lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o >> llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable= =2Eo >> ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o >> lmathlib.o loslib.o ltablib.o lstrlib.o loadlib.o linit.o >> ranlib liblua.a >> clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LI= NUX >> -c lua.c >> clang -o lua lua.o liblua.a -lm -Wl,-E -lreadline >> clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LI= NUX >> -c luac.c >> clang -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall -DLUA_USE_LI= NUX >> -c print.c >> clang -o luac luac.o print.o liblua.a -lm -Wl,-E -lreadline >> clang -o liblua.so -O2 -fno-strict-aliasing -pipe -march=3Dcore2 -Wall= >> -DLUA_USE_LINUX -shared -Wl,-soname=3Dliblua-5.1.so.1 lapi.o lcode.o= >> ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.= o >> lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o >> lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o ltablib.o >> lstrlib.o loadlib.o linit.o >> /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' >> can not be used when making a shared object; recompile with -fPIC >> lapi.o: could not read symbols: Bad value >> clang: error: linker command failed with exit code 1 (use -v to see >> invocation) >> *** Error code 1 >> >> Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. >> *** Error code 1 >> >> Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. >> *** Error code 1 >> >> Stop in /usr/ports/lang/lua/work/lua-5.1.4. >> *** Error code 1 >> >> Stop in /usr/ports/lang/lua. >> >> =3D=3D=3D>>> make failed for lang/lua >> =3D=3D=3D>>> Aborting update >> >> Terminated >> Terminated >> >> This is very strange! > What is strange ? It is exactly the same problem as in the first messag= e > started this thread. You must use -fPIC flag for compiler when compilin= g > objects that shall be later linked into dso. So, for lua case, -fPIC > must be present on the cc -c command line. This therefore strange, since this problem with lua occurs on machines, where I've set "CFLAGS=3D" and "COPTFLAGS=3D" as in /usr/share/examples/etc/make.conf and on one box, one box I accidentally set those flags to "CFLAGS+=3D" and "COPTFLAGS+=3D" and there it works an= d the -fPIC flag is set by the FreeBSD's port framework. So I guess there is a bug introduced with one of the last Mk-files update= s. >=20 > Again, -msse3 is not relevant there. Presense of -msse3 flag might > casually change compiler output to generate the relocation unsuitable > for dso, but compiler has full permit to do so without -msse3 as well. >=20 > Issue with broken gcc 4.6 build is different, it is indeed due to recen= t > changes in system headers due to C11 compliance work. Hopefully, Ed wil= l > fix it. --------------enig8486F0C1902EA172FA10AF3C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO/FrNAAoJEOgBcD7A/5N8W1gH/0avBCfZqwQrMTI19kefBPmg JVxfjGrUrFAuS31aGd6ss30uiDvbkez3BIilSzJAXBTkKtEn242bxjlia837/zMa uvC6YgY2WSnNjbQakh46rcqZvs56mAfnaAO6rj9CYH3ZGuVyVF/lxYC4n9hedO/2 L9NJSjh0Pt0o8AbdyiivaTOOK7+2FWR+bP+V/eHRP43T8ZBRuo8wwxAXO8wonp8r /2+15Jn9vwXNznP/rUsBUGkkkXOUN+bECygkgSwzH1NIFdWhbdgyQPHgMzU1uM/X oXJ2Ycq0J8F7R+LHD/pcS9nGlwANOvVIq6+r+PLFpuQkNJzKkNO6SguXPn6PxaY= =XAJh -----END PGP SIGNATURE----- --------------enig8486F0C1902EA172FA10AF3C-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 07:26:48 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D239106564A for ; Thu, 29 Dec 2011 07:26:48 +0000 (UTC) (envelope-from peterc@luddite.com.au) Received: from arquebus.com.au (proxy.arquebus.com.au [203.20.87.4]) by mx1.freebsd.org (Postfix) with ESMTP id B744B8FC0C for ; Thu, 29 Dec 2011 07:26:47 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=luddite.com.au; h=Date:From:Subject; b=UtIB4ZI5qMvaxKzDeIw7B2dG+ajhBo1NAvk2iTiWm7pmlpimcpNF+vsiGIevUjnSgQHQgPXh6aY/N8o9G/F6BLmKoWA+Hffk3UAaL7ds7dR3L6e2lqZK78yMpa7J98a+; X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=203.20.87.108; Message-ID: <4EFC1260.1060503@luddite.com.au> Date: Thu, 29 Dec 2011 18:10:24 +1100 From: "Peter J. Cherny" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111112 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated-User: peterc@arquebus.com.au X-Mailman-Approved-At: Thu, 29 Dec 2011 12:28:46 +0000 Subject: Apropos Removal of sysinstall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 07:26:48 -0000 Rather than hijack the previous thread, it's probably time to make a few comments on the current and future installation and use of ZFS FreeBSD. I've used both Solaris and FreeBSD since nearly day one for both OSs, so have a deal of familiarity in their use. I believe removal of sysinstall exposes the community's blindness to a major parts of it's future, ZFS root. Other than following arcane recipes, the only way to create a system with ZFS root is by using Martin Matuška's excellent mfsboot images. Where are the plans for making this functionality mainstream ? I believe that unless FreeBSD gets it's act together, Debian/dpkg/zfsonlinux is starting to look like a much more supportable environment (i.e. has a future) Sadly the lack of xen already often forces me to run FreeBSD VMs under Debian. Flames happily accepted if this helps codify FreeBSD's future, but I fear it will go the way of Solaris and be irrelevant to those of us who for decades have used both in the server space. pjc From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 12:34:04 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA557106566C for ; Thu, 29 Dec 2011 12:34:04 +0000 (UTC) (envelope-from mark@exonetric.com) Received: from relay0.exonetric.net (relay0.exonetric.net [82.138.248.161]) by mx1.freebsd.org (Postfix) with ESMTP id 6D3338FC08 for ; Thu, 29 Dec 2011 12:34:04 +0000 (UTC) Received: from miami.exonetric.net (miami.exonetric.net [82.138.248.154]) by relay0.exonetric.net (Postfix) with ESMTP id 10B9557004; Thu, 29 Dec 2011 12:34:03 +0000 (GMT) Date: Thu, 29 Dec 2011 12:34:02 +0000 (GMT) From: Mark Blackman X-X-Sender: mb@miami.exonetric.net To: "Peter J. Cherny" In-Reply-To: <4EFC1260.1060503@luddite.com.au> Message-ID: References: <4EFC1260.1060503@luddite.com.au> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Apropos Removal of sysinstall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 12:34:04 -0000 On Thu, 29 Dec 2011, Peter J. Cherny wrote: > I believe removal of sysinstall exposes the community's blindness to a major > parts of it's future, ZFS root. > > Other than following arcane recipes, > the only way to create a system with ZFS root is by using Martin Matu?ka's > excellent mfsboot images. > > Where are the plans for making this functionality mainstream ? What's stopping this? lack of effort/time or consensus? I know it's a volunteer project and there's lots of resource constraints, but ZFS on root seems like such a no-brainer that I can only assume it's quite hard or nobody has quite decided what it should look like. - Mark From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 12:35:10 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F5621065675 for ; Thu, 29 Dec 2011 12:35:10 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id 7FAE98FC08 for ; Thu, 29 Dec 2011 12:35:09 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.4/8.14.4) with ESMTP id pBTCYxEh092208 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 29 Dec 2011 14:35:04 +0200 (EET) (envelope-from daniel@digsys.bg) Message-ID: <4EFC5E72.806@digsys.bg> Date: Thu, 29 Dec 2011 14:34:58 +0200 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111228 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> <20111228181054.GF1895@hoeg.nl> <4EFB5E0C.90302@zedat.fu-berlin.de> <20111228183132.GB50300@deviant.kiev.zoral.com.ua> <4EFC4579.6060608@gwdg.de> <4EFC4CCC.3050507@zedat.fu-berlin.de> <20111229115904.GH50300@deviant.kiev.zoral.com.ua> <4EFC5ACD.5010701@zedat.fu-berlin.de> In-Reply-To: <4EFC5ACD.5010701@zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: lang/lua: /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' can not be used when making a shared object; recompile with -fPIC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 12:35:10 -0000 On 29.12.11 14:19, O. Hartmann wrote: > Am 12/29/11 12:59, schrieb Kostik Belousov: >> On Thu, Dec 29, 2011 at 12:19:40PM +0100, O. Hartmann wrote: >>> [...] >>> /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' >>> can not be used when making a shared object; recompile with -fPIC >>> lapi.o: could not read symbols: Bad value >>> clang: error: linker command failed with exit code 1 (use -v to see >>> invocation) >>> *** Error code 1 >>> >>> Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. >>> *** Error code 1 >>> >>> Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. >>> *** Error code 1 >>> >>> Stop in /usr/ports/lang/lua/work/lua-5.1.4. >>> *** Error code 1 >>> >>> Stop in /usr/ports/lang/lua. >>> >>> ===>>> make failed for lang/lua >>> ===>>> Aborting update >>> >>> Terminated >>> Terminated >>> >>> This is very strange! >> What is strange ? It is exactly the same problem as in the first message >> started this thread. You must use -fPIC flag for compiler when compiling >> objects that shall be later linked into dso. So, for lua case, -fPIC >> must be present on the cc -c command line. > This therefore strange, since this problem with lua occurs on machines, > where I've set "CFLAGS=" and "COPTFLAGS=" as in > /usr/share/examples/etc/make.conf and on one box, one box I accidentally > set those flags to "CFLAGS+=" and "COPTFLAGS+=" and there it works and > the -fPIC flag is set by the FreeBSD's port framework. > > So I guess there is a bug introduced with one of the last Mk-files updates. > As suggested by the "howto" for using newer GCC versions, http://www.freebsd.org/doc/en/articles/custom-gcc/article.html you are supposed to use CFLAGS+= to add additional compile flags. By the way, "-O2 -fno-strict-aliasing -pipe" are the default flags, that are used when CFLAGS is not set by the user. COPTFLAGS is used only to build the kernel and doing it with non-system GCC is not likely to be safe. Daniel From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 12:59:13 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED594106568D; Thu, 29 Dec 2011 12:59:13 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 97A4D8FC1B; Thu, 29 Dec 2011 12:59:13 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1RgFZg-0003Y7-ET>; Thu, 29 Dec 2011 13:59:12 +0100 Received: from e178008034.adsl.alicedsl.de ([85.178.8.34] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1RgFZg-0001As-8m>; Thu, 29 Dec 2011 13:59:12 +0100 Message-ID: <4EFC641F.4050900@zedat.fu-berlin.de> Date: Thu, 29 Dec 2011 13:59:11 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Daniel Kalchev References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> <20111228181054.GF1895@hoeg.nl> <4EFB5E0C.90302@zedat.fu-berlin.de> <20111228183132.GB50300@deviant.kiev.zoral.com.ua> <4EFC4579.6060608@gwdg.de> <4EFC4CCC.3050507@zedat.fu-berlin.de> <20111229115904.GH50300@deviant.kiev.zoral.com.ua> <4EFC5ACD.5010701@zedat.fu-berlin.de> <4EFC5E72.806@digsys.bg> In-Reply-To: <4EFC5E72.806@digsys.bg> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig462B8D7C2E1809F44A62F02C" X-Originating-IP: 85.178.8.34 Cc: Kostik Belousov , freebsd-current@freebsd.org, Ports FreeBSD Subject: Re: lang/lua: /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' can not be used when making a shared object; recompile with -fPIC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 12:59:14 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig462B8D7C2E1809F44A62F02C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 12/29/11 13:34, schrieb Daniel Kalchev: >=20 >=20 > On 29.12.11 14:19, O. Hartmann wrote: >> Am 12/29/11 12:59, schrieb Kostik Belousov: >>> On Thu, Dec 29, 2011 at 12:19:40PM +0100, O. Hartmann wrote: >>>> [...] >>>> /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_= ' >>>> can not be used when making a shared object; recompile with -fPIC >>>> lapi.o: could not read symbols: Bad value >>>> clang: error: linker command failed with exit code 1 (use -v to see >>>> invocation) >>>> *** Error code 1 >>>> >>>> Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. >>>> *** Error code 1 >>>> >>>> Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. >>>> *** Error code 1 >>>> >>>> Stop in /usr/ports/lang/lua/work/lua-5.1.4. >>>> *** Error code 1 >>>> >>>> Stop in /usr/ports/lang/lua. >>>> >>>> =3D=3D=3D>>> make failed for lang/lua >>>> =3D=3D=3D>>> Aborting update >>>> >>>> Terminated >>>> Terminated >>>> >>>> This is very strange! >>> What is strange ? It is exactly the same problem as in the first mess= age >>> started this thread. You must use -fPIC flag for compiler when compil= ing >>> objects that shall be later linked into dso. So, for lua case, -fPIC >>> must be present on the cc -c command line. >> This therefore strange, since this problem with lua occurs on machines= , >> where I've set "CFLAGS=3D" and "COPTFLAGS=3D" as in >> /usr/share/examples/etc/make.conf and on one box, one box I accidental= ly >> set those flags to "CFLAGS+=3D" and "COPTFLAGS+=3D" and there it works= and >> the -fPIC flag is set by the FreeBSD's port framework. >> >> So I guess there is a bug introduced with one of the last Mk-files >> updates. >> >=20 > As suggested by the "howto" for using newer GCC versions, > http://www.freebsd.org/doc/en/articles/custom-gcc/article.html you are > supposed to use CFLAGS+=3D to add additional compile flags. Just for the record I'd like to repeat, that the error above mentioned is also with the legacy FreeBSD's gcc 4.2.X compiler. As Kostik Belousov made clear in his last posting, the error occurs due to a missing -fPIC - which is now clear to me. People not sleeping with their OS, like myself, would simply copy the make.conf from /usr/share/examples/etc/ and set some additional flags. Then the problem will occur again. Maybe it would be wise to reflect this issue by some additional words in make.conf? >=20 > By the way, "-O2 -fno-strict-aliasing -pipe" are the default flags, tha= t > are used when CFLAGS is not set by the user. >=20 > COPTFLAGS is used only to build the kernel and doing it with non-system= > GCC is not likely to be safe. >=20 > Daniel Oliver --------------enig462B8D7C2E1809F44A62F02C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO/GQfAAoJEOgBcD7A/5N8kgwH/0xKqHoUJ7/UXokd+cqYQlXw emm2odCZRtsTIyjFQfZuJzOoh0mpiP0UXxD5vh+U95YjTClKwOY1KnINlxNKsunS IDY/fBg0a+5e6GucIuTPRqrZF1hEzAgr2xAUbMiZK08P+WA3ZVuN/4KqCBeWdjvO aPb5wZcIJOR3IZpNksZpdv9inpiTsu9EJHH5d/o0x7IgW/GfjDOf7Jg3/oRza+JL TDK+UXL5VizherRe6FDvpghaDk+pzC81PzN5Wjs4Cm/2FjO+HCZJb1GC7kQfsFYx IHCkqahV8ttmtVn2kVNL27dLL/sVVqOhq06Hxflm45GQXGP1xXjFM9WOMyU+vps= =6rDG -----END PGP SIGNATURE----- --------------enig462B8D7C2E1809F44A62F02C-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 14:06:06 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C52A106564A; Thu, 29 Dec 2011 14:06:06 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from fmailer.gwdg.de (fmailer.gwdg.de [134.76.11.16]) by mx1.freebsd.org (Postfix) with ESMTP id EB3708FC12; Thu, 29 Dec 2011 14:06:05 +0000 (UTC) Received: from pd951ce14.dip.t-dialin.net ([217.81.206.20] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1RgGaM-0008Mm-5R; Thu, 29 Dec 2011 15:03:58 +0100 Message-ID: <4EFC73C1.1060303@gwdg.de> Date: Thu, 29 Dec 2011 15:05:53 +0100 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: "O. Hartmann" References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> <20111228181054.GF1895@hoeg.nl> <4EFB5E0C.90302@zedat.fu-berlin.de> <20111228183132.GB50300@deviant.kiev.zoral.com.ua> <4EFC4579.6060608@gwdg.de> <4EFC4CCC.3050507@zedat.fu-berlin.de> <20111229115904.GH50300@deviant.kiev.zoral.com.ua> <4EFC5ACD.5010701@zedat.fu-berlin.de> <4EFC5E72.806@digsys.bg> <4EFC641F.4050900@zedat.fu-berlin.de> In-Reply-To: <4EFC641F.4050900@zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: Kostik Belousov , freebsd-current@freebsd.org, Ports FreeBSD , Daniel Kalchev Subject: Re: lang/lua: /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' can not be used when making a shared object; recompile with -fPIC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 14:06:06 -0000 On 29.12.2011 13:59 (UTC+1), O. Hartmann wrote: > Am 12/29/11 13:34, schrieb Daniel Kalchev: >> >> >> On 29.12.11 14:19, O. Hartmann wrote: >>> Am 12/29/11 12:59, schrieb Kostik Belousov: >>>> On Thu, Dec 29, 2011 at 12:19:40PM +0100, O. Hartmann wrote: >>>>> [...] >>>>> /usr/bin/ld: lapi.o: relocation R_X86_64_32 against `luaO_nilobject_' >>>>> can not be used when making a shared object; recompile with -fPIC >>>>> lapi.o: could not read symbols: Bad value >>>>> clang: error: linker command failed with exit code 1 (use -v to see >>>>> invocation) >>>>> *** Error code 1 >>>>> >>>>> Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. >>>>> *** Error code 1 >>>>> >>>>> Stop in /usr/ports/lang/lua/work/lua-5.1.4/src. >>>>> *** Error code 1 >>>>> >>>>> Stop in /usr/ports/lang/lua/work/lua-5.1.4. >>>>> *** Error code 1 >>>>> >>>>> Stop in /usr/ports/lang/lua. >>>>> >>>>> ===>>> make failed for lang/lua >>>>> ===>>> Aborting update >>>>> >>>>> Terminated >>>>> Terminated >>>>> >>>>> This is very strange! >>>> What is strange ? It is exactly the same problem as in the first message >>>> started this thread. You must use -fPIC flag for compiler when compiling >>>> objects that shall be later linked into dso. So, for lua case, -fPIC >>>> must be present on the cc -c command line. >>> This therefore strange, since this problem with lua occurs on machines, >>> where I've set "CFLAGS=" and "COPTFLAGS=" as in >>> /usr/share/examples/etc/make.conf and on one box, one box I accidentally >>> set those flags to "CFLAGS+=" and "COPTFLAGS+=" and there it works and >>> the -fPIC flag is set by the FreeBSD's port framework. >>> >>> So I guess there is a bug introduced with one of the last Mk-files >>> updates. >>> >> >> As suggested by the "howto" for using newer GCC versions, >> http://www.freebsd.org/doc/en/articles/custom-gcc/article.html you are >> supposed to use CFLAGS+= to add additional compile flags. > > Just for the record I'd like to repeat, that the error above mentioned > is also with the legacy FreeBSD's gcc 4.2.X compiler. > > As Kostik Belousov made clear in his last posting, the error occurs due > to a missing -fPIC - which is now clear to me. > > People not sleeping with their OS, like myself, would simply copy the > make.conf from /usr/share/examples/etc/ and set some additional flags. > Then the problem will occur again. Maybe it would be wise to reflect > this issue by some additional words in make.conf? As stated earlier, the following fails in /etc/make.conf for lang/lua: CFLAGS= -O2 -fno-strict-aliasing -pipe -msse3 The next one works ( += instead of = ) and -fPIC is preserved this way: CFLAGS+= -O2 -fno-strict-aliasing -pipe -msse3 Thanks, Kostik and Daniel for clearing this. I think, like Oliver, that this should be mentioned in /etc/make.conf or make.conf(5). Rainer >> By the way, "-O2 -fno-strict-aliasing -pipe" are the default flags, that >> are used when CFLAGS is not set by the user. >> >> COPTFLAGS is used only to build the kernel and doing it with non-system >> GCC is not likely to be safe. >> >> Daniel > > > Oliver From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 14:07:21 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E93F1065672; Thu, 29 Dec 2011 14:07:21 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) by mx1.freebsd.org (Postfix) with ESMTP id 0FE728FC1D; Thu, 29 Dec 2011 14:07:21 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 58F4225D385D; Thu, 29 Dec 2011 14:07:19 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 62CF9BD809E; Thu, 29 Dec 2011 14:07:18 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id wi1GSx9oWhfw; Thu, 29 Dec 2011 14:07:17 +0000 (UTC) Received: from orange-en1.sbone.de (orange-en1.sbone.de [IPv6:fde9:577b:c1a9:31:cabc:c8ff:fecf:e8e3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 74AC7BD809C; Thu, 29 Dec 2011 14:07:16 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Bjoern A. Zeeb" In-Reply-To: Date: Thu, 29 Dec 2011 14:07:15 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4EFC1260.1060503@luddite.com.au> To: Mark Blackman X-Mailer: Apple Mail (2.1084) Cc: freebsd-current@freebsd.org, "Peter J. Cherny" Subject: Re: Apropos Removal of sysinstall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 14:07:21 -0000 On 29. Dec 2011, at 12:34 , Mark Blackman wrote: > On Thu, 29 Dec 2011, Peter J. Cherny wrote: >> I believe removal of sysinstall exposes the community's blindness to = a major parts of it's future, ZFS root. >>=20 >> Other than following arcane recipes, >> the only way to create a system with ZFS root is by using Martin = Matu?ka's excellent mfsboot images. >>=20 >> Where are the plans for making this functionality mainstream ? >=20 > What's stopping this? lack of effort/time or consensus? > I know it's a volunteer project and there's lots of resource = constraints, > but ZFS on root seems like such a no-brainer that I can only assume = it's > quite hard or nobody has quite decided what it should look like. Not sure if it's a no-brianer but I seem to remember that there had been patches prepared for bsdinstall which were never finished/committed. I'll let that person follow-up himself on the state to where he got. /bz --=20 Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family.= From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 14:17:04 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09D84106566C for ; Thu, 29 Dec 2011 14:17:04 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) by mx1.freebsd.org (Postfix) with ESMTP id B6C3A8FC0A for ; Thu, 29 Dec 2011 14:17:03 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 01C3F25D3872; Thu, 29 Dec 2011 14:17:02 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 4068EBD809F; Thu, 29 Dec 2011 14:17:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id cF0n4SEvDFUx; Thu, 29 Dec 2011 14:17:01 +0000 (UTC) Received: from orange-en1.sbone.de (orange-en1.sbone.de [IPv6:fde9:577b:c1a9:31:cabc:c8ff:fecf:e8e3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 42476BD809D; Thu, 29 Dec 2011 14:17:01 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Bjoern A. Zeeb" In-Reply-To: <4EFC1260.1060503@luddite.com.au> Date: Thu, 29 Dec 2011 14:17:00 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4EFC1260.1060503@luddite.com.au> To: Peter J. Cherny X-Mailer: Apple Mail (2.1084) Cc: freebsd-current@freebsd.org Subject: Re: Apropos Removal of sysinstall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 14:17:04 -0000 On 29. Dec 2011, at 07:10 , Peter J. Cherny wrote: > I believe removal of sysinstall exposes the community's blindness to a = major parts of it's future, ZFS root. Oh if it was for ZFS root only.. package management is gone in 10 with = that as well but there is work in progress for the new system so it'll be back and = hopefully be just awesome:) > Sadly the lack of xen already often forces me to run FreeBSD VMs under = Debian. Xen is being worked on as well even dom0. bhyve is coming along as = well. ... There's plenty of virtualization if not jails ongoing or wrapping up. A good start to get an idea if the latest ponderings/wishlist of = developers and devsummit attendees can be found here: http://wiki.freebsd.org/FreeBSD10 Some of these things have happened already and some even made it into = the upcoming 9.0 and should be crossed off. /bz --=20 Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 14:49:31 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC985106564A; Thu, 29 Dec 2011 14:49:31 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from mx0.hoeg.nl (mx0.hoeg.nl [IPv6:2a01:4f8:101:5343::aa]) by mx1.freebsd.org (Postfix) with ESMTP id 8820F8FC0A; Thu, 29 Dec 2011 14:49:31 +0000 (UTC) Received: by mx0.hoeg.nl (Postfix, from userid 1000) id A11C02A28CBC; Thu, 29 Dec 2011 15:49:30 +0100 (CET) Date: Thu, 29 Dec 2011 15:49:30 +0100 From: Ed Schouten To: Rainer Hurling Message-ID: <20111229144930.GG1895@hoeg.nl> References: <4EFAF3FC.60002@zedat.fu-berlin.de> <20111228135808.GW50300@deviant.kiev.zoral.com.ua> <4EFB2344.3000302@zedat.fu-berlin.de> <20111228142957.GX50300@deviant.kiev.zoral.com.ua> <4EFB447D.3000808@gwdg.de> <20111228181054.GF1895@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kH8JNVvasRCCW1Oz" Content-Disposition: inline In-Reply-To: <20111228181054.GF1895@hoeg.nl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Kostik Belousov , Current FreeBSD , "O. Hartmann" , Ports FreeBSD Subject: [Resolved] GCC 4.6 compilation problems w.r.t. static_assert X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 14:49:32 -0000 --kH8JNVvasRCCW1Oz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Ed Schouten , 20111228 19:10: > Hmmm... This seems to apply to my changes. I will look into this > tomorrow. Thanks for the report! Just to clarify, as mentioned earlier in this thread, the linking problems problems are not related by my C11 patches, as they are only part of HEAD. It seems they were caused due to local configuration problems and have been resolved. The GCC 4.6 compilation problem on HEAD was caused by one of my changes. Please update your system to r228955 or later. Thanks for reporting. --=20 Ed Schouten WWW: http://80386.nl/ --kH8JNVvasRCCW1Oz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQIcBAEBAgAGBQJO/H36AAoJEG5e2P40kaK77MUQAJQBsTZgjkCQIQ2uNmcGFV87 Eu2MIJMUWwSMLHu2tJ9sWS9HsEodxJWc8LlXoB17XTJM8r71aBxuUolvrnGhFway 8wy0OknYvbVVyloHc1eSPIR6UxWOHFbTCVyWLZ9QQc1eX8VvfKDNq9sYeRp8OQ3h ZjmdeItHNSXvZU1J5Og2mo+6qp/CkchJtgPmSkaBvTbMmVZryi+2pFU7uSudXPHV CXKBn7Jkzor4IJMFhfDSI2X448gGEOIamMonuIuhhtDRn3YRHXYcPTyLpzWK9V9e UV85kocXURdn+O442ZrtNRbsCndGh1OHvpyVDl2DUTHWLqLAlTxIxbqempK5oxck mzXgozZohXrkHSeh/nJkmdeTJ/W8L8EnYzmVzTyMwJ3btXkyUb4a38HG5pRhjazK BOenhfPg36gmQYbwo3MLTHM5D6XCtsmbpLei6kqMei9QYduwaHPm9waf5Dli3DFm bJSHxinsYU7PDjftAaOcD3hrM93AxpPBAgd+yoMWz2fRAQF5ICGSQXoeeiprET2R qc/GRa1EAgMpUSU/zb3+K7OdY66Z/9kzqT17hOXTwbkk8BZOMA+d4aVlhulrHz10 YJL9q6inEXzCDDnt/8/an4Wb3ZB4fitVqMH+Aww8xXTJyMHXgyZcgO0Cje511OER 126ZhD0DryLY4I1VDVij =jUy8 -----END PGP SIGNATURE----- --kH8JNVvasRCCW1Oz-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 15:20:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C49E106566B for ; Thu, 29 Dec 2011 15:20:32 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from adsum.doit.wisc.edu (adsum.doit.wisc.edu [144.92.197.210]) by mx1.freebsd.org (Postfix) with ESMTP id 0E7988FC08 for ; Thu, 29 Dec 2011 15:20:31 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth1.wiscmail.wisc.edu by smtpauth1.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LWZ0050O1A7LY00@smtpauth1.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Thu, 29 Dec 2011 09:20:31 -0600 (CST) Received: from wanderer.tachypleus.net ([unknown] [76.210.77.223]) by smtpauth1.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LWZ00KIC19YOT10@smtpauth1.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Thu, 29 Dec 2011 09:20:22 -0600 (CST) Date: Thu, 29 Dec 2011 07:20:20 -0800 From: Nathan Whitehorn In-reply-to: To: freebsd-current@freebsd.org Message-id: <4EFC8534.7040903@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.77.223 X-Spam-PmxInfo: Server=avs-12, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.12.29.150914, SenderIP=76.210.77.223 References: <4EFC1260.1060503@luddite.com.au> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111213 Thunderbird/8.0 Subject: Re: Apropos Removal of sysinstall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 15:20:32 -0000 On 12/29/11 04:34, Mark Blackman wrote: > > > On Thu, 29 Dec 2011, Peter J. Cherny wrote: >> I believe removal of sysinstall exposes the community's blindness to a >> major parts of it's future, ZFS root. >> >> Other than following arcane recipes, >> the only way to create a system with ZFS root is by using Martin >> Matu?ka's excellent mfsboot images. >> >> Where are the plans for making this functionality mainstream ? > > What's stopping this? lack of effort/time or consensus? > I know it's a volunteer project and there's lots of resource constraints, > but ZFS on root seems like such a no-brainer that I can only assume it's > quite hard or nobody has quite decided what it should look like. It's not very hard. Several people volunteered to do this a long time ago, and for reasons of time, I guess, it didn't happen or wasn't finished. Since they were doing it, it was silly for other people to work on it, and so here we are. Maybe this discussion will prompt patches. What needs to be done is the following: - Write a zfs_ops.c file as an analog to gpart_ops.c in src/usr.sbin/bsdinstall/partedit that implements the Add/Delete/Modify buttons for ZFS filesystems in zpools. Some logic to avoid touching the disks until the user presses finish is also necessary. - Write some code to show ZFS file systems in zpools in the main partition editor screen, like the existing gpart walk code - Code to add partitions to zpools (probably just check for freebsd-zfs type and then use the mountpoint as the zpool name or something) when they are created. I unfortunately don't have much FreeBSD time at the moment, so can't complete this. But I will very, very happily provide advice and integrate patches. -Nathan From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 15:31:01 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E62A2106564A; Thu, 29 Dec 2011 15:31:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id BD8698FC0C; Thu, 29 Dec 2011 15:31:01 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 764CF46B55; Thu, 29 Dec 2011 10:31:01 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id DFB49B914; Thu, 29 Dec 2011 10:31:00 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 29 Dec 2011 09:47:56 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <20111225214033.GA1933@freebsd.org> In-Reply-To: <20111225214033.GA1933@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201112290947.56982.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 29 Dec 2011 10:31:01 -0500 (EST) Cc: Alexander Best Subject: Re: starting the annual discussion regarding top(1)'s CPU usage statistics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 15:31:02 -0000 On Sunday, December 25, 2011 4:40:33 pm Alexander Best wrote: > ok...so we all know that top(1) cannot compute the exact CPU usage for all > processes, since some processes get spawned and exit so fast that they don't > fall into the calculation range. i think nobody is getting angry when top(1) > is off by a few percent. > > however please take a look at the following top(1) output. this is just > ridiculous! out of 800% of CPU power, almost 600% mysteriously vanished. is > there really nothing to improve top(1)'s behaviour when the CPU is dealing with > a lot of short processes (time wise) with a hugh CPU burst? Do you have a lot of short-lived processes? (For example, a -j X build?) top(1) can't do anything about processes it doesn't see (since they are so short-lived and it only samples every N seconds), but those processes still accumulate CPU time and %CPU. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 15:31:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 169AF106566B; Thu, 29 Dec 2011 15:31:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id DFA138FC12; Thu, 29 Dec 2011 15:31:02 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 9641646B3F; Thu, 29 Dec 2011 10:31:02 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1C449B960; Thu, 29 Dec 2011 10:31:02 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 29 Dec 2011 09:52:06 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <4EF904F2.4020109@FreeBSD.org> <4EFA1C9C.60601@FreeBSD.org> <4EFA7FD4.10600@freebsd.org> In-Reply-To: <4EFA7FD4.10600@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112290952.06834.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 29 Dec 2011 10:31:02 -0500 (EST) Cc: Lawrence Stewart , Doug Barton , Ron McDowell Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 15:31:03 -0000 On Tuesday, December 27, 2011 9:32:52 pm Lawrence Stewart wrote: > On 12/28/11 06:29, Doug Barton wrote: > > On 12/27/2011 03:48, Lawrence Stewart wrote: > >> On the topic of Doug's actual question, I see minimal sense in > >> resurrecting sysinstall in head now. I would suggest it be done much > >> closer to (say, 6 months before) the 10.0 release cycle, if no suitable > >> post-installation configuration tool has materialised. > > > > My concern about that approach is that 9.0 hasn't even been released yet > > and we've already seen changes that are going to make it hard to > > resurrect sysinstall if that's the decision we come to. Waiting another > > year or 2 would make it impossible. > > Which changes are you referring to? I would have thought a reverse merge > to undo the deletion of the sysinstall and old libdialog sources would > be very minimal work. We'd also probably need a few extra build system > changes to make sure old libdialog is perhaps statically compiled into > sysinstall as it would be the only in-tree consumer, but that's not hard > either. I may be lacking some imagination, but don't really see why it > would become harder the longer we wait. I think Doug is worried that the list will just get longer, and I agree. Bits rot faster once they aren't part of the build. It is easy to delete sysinstall or trim it, it is not easy to resurrect it. Personally, the one time I used bsdinstall recently I found it to be a bit uneven, and not really a step forward for a new user compared to the "standard" install mode of sysinstall. It's biggest win is it's ability to do more disk configurations, but it seemed less user-friendly in almost every other regard (and even the disk editor seemd less user-friendly even if it had more functionality). -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 15:31:33 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BC541065704; Thu, 29 Dec 2011 15:31:33 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from mx0.hoeg.nl (mx0.hoeg.nl [IPv6:2a01:4f8:101:5343::aa]) by mx1.freebsd.org (Postfix) with ESMTP id E595E8FC12; Thu, 29 Dec 2011 15:31:32 +0000 (UTC) Received: by mx0.hoeg.nl (Postfix, from userid 1000) id 5B94A2A28CC3; Thu, 29 Dec 2011 16:31:32 +0100 (CET) Date: Thu, 29 Dec 2011 16:31:32 +0100 From: Ed Schouten To: freebsd-current@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Message-ID: <20111229153132.GI1895@hoeg.nl> References: <20111226101040.GA6361@freebsd.org> <20111227010449.GA6244@twoflower.paeps.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3W6riq+uV6J42Ub" Content-Disposition: inline In-Reply-To: <20111227010449.GA6244@twoflower.paeps.cx> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 15:31:33 -0000 --u3W6riq+uV6J42Ub Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Philip Paeps , 20111227 02:04: > Wouldn't it be better to set WARNS=3Dx rather than WERROR=3D? Not entirely related to the discussion, but worth mentioning: WARNS is only used by -- not . --=20 Ed Schouten WWW: http://80386.nl/ --u3W6riq+uV6J42Ub Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQIcBAEBAgAGBQJO/IfUAAoJEG5e2P40kaK7RiQP/3ki4pMwhoej8ptchr8p6MGX QBNW0qsbwzXShl8h4iHU9CDg7y5Nx1npfkT7aMqtDRCuX0E6rxovsGo77Em1amwG LilQT8SYoxBtEPB9fLXH/ul3GCzvBM3gjDJHZKB+zLILHLCfn8vUYJww0orfrDFF WCH2wBQhKD04nd0rzauU2LQiIAj145N10emvHmH6poDDlbObJX1jSox6nEq1+gu6 NNSqOKuFInCsjc6iRI8QWbmDgoMWhPAlHY6SfTXKOug8dg9CKCIO6noBURIsNa37 FNAk6DXbMIStf4uMtQIb1mDQ4H66qKLDzgDHOX8TnKN4bnK26H6me0yKe2XCBVxv x0+MaWQ87zwRu4Xz4EZmP89rfawufIHSleL6/MVc/9i6OIRC1IGRsXRRh6ppkkmb /AWb1vsY+jwFFN7NJt4Y2DNSuMpj3pGnJEjqtiLGHjTODWa4nUXnqCX/fm2nZy9b b6U1G+F51olPke/9MnrqgO7F1qaBNIWnyAozZ0Vn/MBFLaySB15LIyedKwQNjYuG PRo2FTs69zEJeIOahguyjz7Wgj+nmNp4xFI5K7aECCriJUUAnoi7SOWxYfyQi0eu jGWjA6/2Okjg3rk0nOC1nG3cfYNb8trFx2G7fnHu07V1M56eGvntwiJ48mYp6I5t Lte52ACz1O2urUCJgDAw =LjXm -----END PGP SIGNATURE----- --u3W6riq+uV6J42Ub-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 15:31:33 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BC541065704; Thu, 29 Dec 2011 15:31:33 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from mx0.hoeg.nl (mx0.hoeg.nl [IPv6:2a01:4f8:101:5343::aa]) by mx1.freebsd.org (Postfix) with ESMTP id E595E8FC12; Thu, 29 Dec 2011 15:31:32 +0000 (UTC) Received: by mx0.hoeg.nl (Postfix, from userid 1000) id 5B94A2A28CC3; Thu, 29 Dec 2011 16:31:32 +0100 (CET) Date: Thu, 29 Dec 2011 16:31:32 +0100 From: Ed Schouten To: freebsd-current@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Message-ID: <20111229153132.GI1895@hoeg.nl> References: <20111226101040.GA6361@freebsd.org> <20111227010449.GA6244@twoflower.paeps.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3W6riq+uV6J42Ub" Content-Disposition: inline In-Reply-To: <20111227010449.GA6244@twoflower.paeps.cx> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 15:31:33 -0000 --u3W6riq+uV6J42Ub Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Philip Paeps , 20111227 02:04: > Wouldn't it be better to set WARNS=3Dx rather than WERROR=3D? Not entirely related to the discussion, but worth mentioning: WARNS is only used by -- not . --=20 Ed Schouten WWW: http://80386.nl/ --u3W6riq+uV6J42Ub Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQIcBAEBAgAGBQJO/IfUAAoJEG5e2P40kaK7RiQP/3ki4pMwhoej8ptchr8p6MGX QBNW0qsbwzXShl8h4iHU9CDg7y5Nx1npfkT7aMqtDRCuX0E6rxovsGo77Em1amwG LilQT8SYoxBtEPB9fLXH/ul3GCzvBM3gjDJHZKB+zLILHLCfn8vUYJww0orfrDFF WCH2wBQhKD04nd0rzauU2LQiIAj145N10emvHmH6poDDlbObJX1jSox6nEq1+gu6 NNSqOKuFInCsjc6iRI8QWbmDgoMWhPAlHY6SfTXKOug8dg9CKCIO6noBURIsNa37 FNAk6DXbMIStf4uMtQIb1mDQ4H66qKLDzgDHOX8TnKN4bnK26H6me0yKe2XCBVxv x0+MaWQ87zwRu4Xz4EZmP89rfawufIHSleL6/MVc/9i6OIRC1IGRsXRRh6ppkkmb /AWb1vsY+jwFFN7NJt4Y2DNSuMpj3pGnJEjqtiLGHjTODWa4nUXnqCX/fm2nZy9b b6U1G+F51olPke/9MnrqgO7F1qaBNIWnyAozZ0Vn/MBFLaySB15LIyedKwQNjYuG PRo2FTs69zEJeIOahguyjz7Wgj+nmNp4xFI5K7aECCriJUUAnoi7SOWxYfyQi0eu jGWjA6/2Okjg3rk0nOC1nG3cfYNb8trFx2G7fnHu07V1M56eGvntwiJ48mYp6I5t Lte52ACz1O2urUCJgDAw =LjXm -----END PGP SIGNATURE----- --u3W6riq+uV6J42Ub-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 16:24:26 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BD38106566B; Thu, 29 Dec 2011 16:24:26 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1E6408FC15; Thu, 29 Dec 2011 16:24:26 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id CA95646B37; Thu, 29 Dec 2011 11:24:25 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 418EAB974; Thu, 29 Dec 2011 11:24:25 -0500 (EST) From: John Baldwin To: =?windows-1251?b?yu7t/Oru4iDF4uPl7ejp?= Date: Thu, 29 Dec 2011 11:12:59 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <20111022084931.GD1697@garage.freebsd.pl> <201112200952.44690.jhb@freebsd.org> <1632420869.20111225180133@yandex.ru> In-Reply-To: <1632420869.20111225180133@yandex.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Message-Id: <201112291112.59912.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 29 Dec 2011 11:24:25 -0500 (EST) Cc: Andre Oppermann , freebsd-net@freebsd.org, Pawel Jakub Dawidek , freebsd-current@freebsd.org, Kostik Belousov , Lawrence Stewart Subject: Re: 9.0-RC1 panic in tcp_input: negative winow. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 16:24:26 -0000 On Sunday, December 25, 2011 11:01:33 am =CA=EE=ED=FC=EA=EE=E2 =C5=E2=E3=E5= =ED=E8=E9 wrote: > =C7=E4=F0=E0=E2=F1=F2=E2=F3=E9=F2=E5, John. >=20 > =C2=FB =EF=E8=F1=E0=EB=E8 20 =E4=E5=EA=E0=E1=F0=FF 2011 =E3., 16:52:44: >=20 > JB> On Saturday, December 17, 2011 6:21:27 pm Pawel Jakub Dawidek wrote: > >> On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote: > >> > An update. I've sent Pawel a testing patch to see if my hypothesis = is correct > >> > (www.freebsd.org/~jhb/patches/tcp_negwin_test.patch). If it is then= I intend > >> > to commit www.freebsd.org/~jhb/patches/tcp_negwin2.patch as the fix. > >>=20 > >> Unfortunately it paniced today. Take a look at: > >>=20 > >> http://people.freebsd.org/~pjd/misc/tcp_panic.jpg >=20 > JB> Ok, the one use case I was worried about is happening regularly befor= e your > JB> panic, so that is good. Can you use gdb to figure out which call to > JB> tcp_output() is actually panic'ing? I wonder if it is this case: >=20 > JB> /* > JB> * Return any desired output. > JB> */ > JB> if (needoutput || (tp->t_flags & TF_ACKNOW)) { > JB> (void) tcp_output(tp); > JB> /* XXX: Debug */ > JB> KASSERT(SEQ_GEQ(tp->rcv_adv, tp->rcv_nxt), > JB> ("tcp_input: negative window after ACK")); >=20 > JB> And if 'needoutput' is true, but TF_ACKNOW is not set, and tcp_output= () decides > JB> to not do anything. I've updated tcp_negwin_test.patch to not panic = if that call > JB> to tcp_output() doesn't actually send a packet. Please re-test. >=20 >=20 > # uname -a > FreeBSD meta-up 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #4: Sat Dec 24 13:5= 9:20 EET 2011 @:/usr/obj/usr/src/sys/KES_KERN_v10 i386 >=20 > rebooting once per day. Now I compile kernel with debug options. > Can you advice me which and where I find debug info when it will > reboting next time? so I can help to debug problem Are you using the patch at the URL above (tcp_negwin_test.patch)? If not, can you try applying that patch and seeing if you still get any panics? =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 16:24:26 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B76AB1065673; Thu, 29 Dec 2011 16:24:26 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8E29E8FC16; Thu, 29 Dec 2011 16:24:26 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 4481246B3F; Thu, 29 Dec 2011 11:24:26 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 99F8BB93A; Thu, 29 Dec 2011 11:24:25 -0500 (EST) From: John Baldwin To: Larry Rosenman Date: Thu, 29 Dec 2011 11:17:49 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <4EF48065.8000802@lerctr.org> <4EF4AF5C.1060000@lerctr.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112291117.49679.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 29 Dec 2011 11:24:25 -0500 (EST) Cc: Alexander Motin , freebsd-current@freebsd.org Subject: Re: scheduler panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 16:24:26 -0000 On Sunday, December 25, 2011 10:48:32 am Larry Rosenman wrote: > On Fri, 23 Dec 2011, Larry Rosenman wrote: > > On 12/23/2011 8:54 AM, John Baldwin wrote: > >> The sloppiest fix might be to do this: > >> > >> Index: sched_ule.c > >> =================================================================== > >> > >> > > - --- sched_ule.c (revision 228777) > >> +++ sched_ule.c (working copy) @@ -1434,7 +1434,8 @@ > >> sched_priority(struct thread *td) } else { pri = SCHED_PRI_MIN; if > >> (td->td_sched->ts_ticks) - pri += SCHED_PRI_TICKS(td->td_sched); > >> + pri += min(SCHED_PRI_TICKS(td->td_sched), + > >> SCHED_PRI_RANGE); pri += SCHED_PRI_NICE(td->td_proc->p_nice); > >> KASSERT(pri >= PRI_MIN_BATCH && pri <= PRI_MAX_BATCH, > >> ("sched_priority: invalid priority %d: nice %d, " > >> > > > > I've applied this to both the host and the guest, and am recompiling > > the guest kernel (hopefully it'll stay up long enough...). > > > > I'll report back. > > > > Do y'all (FreeBSD Devs) want a PR? > > > > > I've run 2 complete buildworld/buildkernel cycles with the patch applied > in the guest, and it's made it all the way through. It wouldn't > do that without it. > > Can we get this (or something else like it) applied? > > Do I need to file a PR? I've committed this. I do think the root problem is an issue with the clock interrupts, but this seems to be a common enough problem I think a workaround is warranted. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 15:37:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B5411065673 for ; Thu, 29 Dec 2011 15:37:32 +0000 (UTC) (envelope-from gabor@t-hosting.hu) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id 51CB18FC1B for ; Thu, 29 Dec 2011 15:37:32 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id 4294B14E697D; Thu, 29 Dec 2011 16:22:26 +0100 (CET) X-Virus-Scanned: amavisd-new at server.mypc.hu Received: from server.mypc.hu ([127.0.0.1]) by server.mypc.hu (server.mypc.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id FeV8bz8HL8Ag; Thu, 29 Dec 2011 16:22:24 +0100 (CET) Received: from [192.168.1.117] (catv-80-98-232-12.catv.broadband.hu [80.98.232.12]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id 089FC14E68EA; Thu, 29 Dec 2011 16:22:24 +0100 (CET) Message-ID: <4EFC85AB.8070303@t-hosting.hu> Date: Thu, 29 Dec 2011 16:22:19 +0100 From: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0a2) Gecko/20111122 Thunderbird/10.0a2 MIME-Version: 1.0 To: Randy Bush References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 29 Dec 2011 16:34:26 +0000 Cc: FreeBSD Current Subject: Re: grep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 15:37:32 -0000 On 2011.12.28. 23:35, Randy Bush wrote: > FreeBSD ran.psg.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4: Sat Dec 24 12:33:51 UTC 2011 root@ran.psg.com:/usr/obj/usr/src/sys/RAN amd64 > > % echo foo | grep foo > % > > What about 'grep -V'? Or 'which grep'? Gabor From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 16:37:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C80ED106566C; Thu, 29 Dec 2011 16:37:29 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id 94F6F8FC16; Thu, 29 Dec 2011 16:37:29 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LWZ0030Q4UG4R00@smtpauth2.wiscmail.wisc.edu>; Thu, 29 Dec 2011 10:37:28 -0600 (CST) Received: from wanderer.tachypleus.net ([unknown] [76.210.77.223]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LWZ00ECK4UDWC20@smtpauth2.wiscmail.wisc.edu>; Thu, 29 Dec 2011 10:37:26 -0600 (CST) Date: Thu, 29 Dec 2011 08:37:25 -0800 From: Nathan Whitehorn In-reply-to: <201112290952.06834.jhb@freebsd.org> To: John Baldwin Message-id: <4EFC9745.3050901@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.77.223 X-Spam-PmxInfo: Server=avs-9, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.12.29.162715, SenderIP=76.210.77.223 References: <4EF904F2.4020109@FreeBSD.org> <4EFA1C9C.60601@FreeBSD.org> <4EFA7FD4.10600@freebsd.org> <201112290952.06834.jhb@freebsd.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111213 Thunderbird/8.0 Cc: Lawrence Stewart , freebsd-current@freebsd.org, Ron McDowell , Doug Barton Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 16:37:29 -0000 On 12/29/11 06:52, John Baldwin wrote: > On Tuesday, December 27, 2011 9:32:52 pm Lawrence Stewart wrote: >> On 12/28/11 06:29, Doug Barton wrote: >>> On 12/27/2011 03:48, Lawrence Stewart wrote: >>>> On the topic of Doug's actual question, I see minimal sense in >>>> resurrecting sysinstall in head now. I would suggest it be done much >>>> closer to (say, 6 months before) the 10.0 release cycle, if no suitable >>>> post-installation configuration tool has materialised. >>> >>> My concern about that approach is that 9.0 hasn't even been released yet >>> and we've already seen changes that are going to make it hard to >>> resurrect sysinstall if that's the decision we come to. Waiting another >>> year or 2 would make it impossible. >> >> Which changes are you referring to? I would have thought a reverse merge >> to undo the deletion of the sysinstall and old libdialog sources would >> be very minimal work. We'd also probably need a few extra build system >> changes to make sure old libdialog is perhaps statically compiled into >> sysinstall as it would be the only in-tree consumer, but that's not hard >> either. I may be lacking some imagination, but don't really see why it >> would become harder the longer we wait. > > I think Doug is worried that the list will just get longer, and I agree. > Bits rot faster once they aren't part of the build. It is easy to delete > sysinstall or trim it, it is not easy to resurrect it. Personally, the one > time I used bsdinstall recently I found it to be a bit uneven, and not really > a step forward for a new user compared to the "standard" install mode of > sysinstall. It's biggest win is it's ability to do more disk configurations, > but it seemed less user-friendly in almost every other regard (and even the > disk editor seemd less user-friendly even if it had more functionality). > I'd appreciate any specific comments you might have, and especially specific suggestions for improvements. Except from people who are old hands at sysinstall, I've received almost universally positive comments on the user experience. Patches would be even more appreciated, since real life has intervened to steal most of my FreeBSD time. -Nathan From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 17:41:06 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C786106567A for ; Thu, 29 Dec 2011 17:41:06 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id D82378FC1D for ; Thu, 29 Dec 2011 17:41:05 +0000 (UTC) Received: by eekc50 with SMTP id c50so15880621eek.13 for ; Thu, 29 Dec 2011 09:41:05 -0800 (PST) Received: by 10.14.126.80 with SMTP id a56mr14923538eei.121.1325180463996; Thu, 29 Dec 2011 09:41:03 -0800 (PST) Received: from gizmo.my.domain (nat140-249-205-109.tvoe.tv. [109.205.249.140]) by mx.google.com with ESMTPS id b49sm105663295eec.9.2011.12.29.09.41.01 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 29 Dec 2011 09:41:02 -0800 (PST) From: Oleg Ginzburg To: freebsd-current@freebsd.org Date: Thu, 29 Dec 2011 21:41:39 +0400 User-Agent: KMail/1.13.7 (FreeBSD/9.0-PRERELEASE; KDE/4.7.3; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112292141.39063.olevole@olevole.ru> Subject: segfault from php/freebsd/dtrace X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 17:41:06 -0000 Hi maillist, I try to use dtrace + php/dtrace on the freebsd. In certain cases ive get Segmentation fault and don't understand what of subsystem has a problem. For this purpose: 1) have PHP with DTrace probes, for example: svn co https://svn.php.net/repository/php/php-src/trunk php-trunk php-trunk/buildconf ( needs bison && re2c ) php-trunk/configure --enable-dtrace ( then bulds as usual) 2) have FreeBSD with world/kernel Dtrace support 3) Run php for providing dtrace/php probes % php 4) Execute dtrace with PHP probes, for example, watch the errors: % dtrace -s /dev/stdin #pragma D option quiet php*:::error { printf("Error: %s in line %d (%s)\n", copyinstr(arg0), arg2, copyinstr(arg1)); } ^D 4) Run PHP with some error, for example: % php -E "thisisit" ^D Result: Dtrace ouput (this is ok): Error: syntax error, unexpected end of file in line 1 (Command line end code) % php -E "thisisit" Segmentation fault (core dumped) % gdb -c ./php.core /usr/local/bin/php GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Core was generated by `php'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libelf.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libelf.so.1 Reading symbols from /lib/libcrypt.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.5 Reading symbols from /lib/libz.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.6 Reading symbols from /usr/local/lib/libpcre.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /usr/lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/librt.so.1 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/local/lib/libxml2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxml2.so.5 Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00000008021c6a37 in strlen () from /lib/libc.so.7 [New Thread 802807400 (LWP 100326/php)] (gdb) file No executable file now. /usr/src/gnu/usr.bin/gdb/libgdb/fbsd-threads.c:484: internal-error: fbsd_thread_new_objfile: Assertion `proc_handle.pid == 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) n /usr/src/gnu/usr.bin/gdb/libgdb/fbsd-threads.c:484: internal-error: fbsd_thread_new_objfile: Assertion `proc_handle.pid == 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) n (gdb) bt #0 0x00000008021c6a37 in ?? () from /lib/libc.so.7 /usr/src/gnu/usr.bin/gdb/libgdb/../../../../contrib/gdb/gdb/dwarf2- frame.c:613: internal-error: dwarf2_frame_cache: Assertion `fde != NULL' failed. Backtrace for php.core: fbsd-strace# gdb -c ./php.core /usr/local/bin/php GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Core was generated by `php'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libelf.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libelf.so.1 Reading symbols from /lib/libcrypt.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.5 Reading symbols from /lib/libz.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.6 Reading symbols from /usr/local/lib/libpcre.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /usr/lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/librt.so.1 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/local/lib/libxml2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxml2.so.5 Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00000008021c6a37 in strlen () from /lib/libc.so.7 [New Thread 802807400 (LWP 100326/php)] (gdb) bt #0 0x00000008021c6a37 in strlen () from /lib/libc.so.7 #1 0x0000000000511b7a in vspprintf () #2 0x000000000050ecd7 in php_error_cb () #3 0x0000000000568ba4 in zend_error_noreturn () #4 0x000000000052e414 in zendparse () #5 0x000000000053c8fb in compile_string () #6 0x000000000055b523 in zend_eval_stringl () #7 0x000000000055b799 in zend_eval_stringl_ex () #8 0x000000000060bee0 in do_cli () #9 0x000000000060c6b4 in main () #10 0x0000000000419bbe in _start () #11 0x000000080098b000 in ?? () #12 0x0000000000000000 in ?? () #13 0x0000000000000003 in ?? () #14 0x00007fffffffdde8 in ?? () #15 0x00007fffffffddec in ?? () #16 0x00007fffffffddef in ?? () #17 0x0000000000000000 in ?? () #18 0x00007fffffffddf8 in ?? () #19 0x00007fffffffde03 in ?? () #20 0x00007fffffffde18 in ?? () #21 0x00007fffffffde24 in ?? () #22 0x00007fffffffde38 in ?? () #23 0x00007fffffffde8f in ?? () #24 0x00007fffffffde9e in ?? () #25 0x00007fffffffdea9 in ?? () #26 0x00007fffffffdeb3 in ?? () #27 0x00007fffffffdec4 in ?? () #28 0x00007fffffffded3 in ?? () #29 0x00007fffffffdee2 in ?? () #30 0x00007fffffffdef3 in ?? () #31 0x00007fffffffdefb in ?? () #32 0x00007fffffffdf0f in ?? () #33 0x00007fffffffdf1c in ?? () #34 0x00007fffffffdf28 in ?? () #35 0x00007fffffffdf43 in ?? () #36 0x00007fffffffdf5a in ?? () #37 0x00007fffffffdf64 in ?? () #38 0x0000000000000000 in ?? () #39 0x0000000000000003 in ?? () #40 0x0000000000400040 in ?? () #41 0x0000000000000004 in ?? () #42 0x0000000000000038 in ?? () #43 0x0000000000000005 in ?? () #44 0x0000000000000008 in ?? () #45 0x0000000000000006 in ?? () #46 0x0000000000001000 in ?? () #47 0x0000000000000008 in ?? () #48 0x0000000000000000 in ?? () #49 0x0000000000000009 in ?? () #50 0x0000000000419b30 in ?? () #51 0x0000000000000007 in ?? () #52 0x0000000800951000 in ?? () #53 0x000000000000000f in ?? () #54 #55 0x0000000000000000 in ?? () Previous frame inner to this frame (corrupt stack?) In a case when php it is compiled with debug symbols, Segfault is absent. --//Cut of /usr/src/gnu/usr.bin/gdb/libgdb/fbsd-threads.c//-- static void fbsd_thread_new_objfile (struct objfile *objfile) { td_err_e err; if (objfile == NULL) { /* All symbols have been discarded. If the thread_db target is active, deactivate it now. */ if (fbsd_thread_active) { gdb_assert (proc_handle.pid == 0); << Here is 484 string mentioned by backtrace << fbsd_thread_active = 0; } goto quit; } --//End of Cut//-- There are the ideas, what the part can cause a problem? From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 17:37:00 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0002C106566B for ; Thu, 29 Dec 2011 17:36:59 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8B56A8FC14 for ; Thu, 29 Dec 2011 17:36:59 +0000 (UTC) Received: by eekc50 with SMTP id c50so15877945eek.13 for ; Thu, 29 Dec 2011 09:36:58 -0800 (PST) Received: by 10.14.32.14 with SMTP id n14mr14440394eea.64.1325180218197; Thu, 29 Dec 2011 09:36:58 -0800 (PST) Received: from gizmo.my.domain (nat140-249-205-109.tvoe.tv. [109.205.249.140]) by mx.google.com with ESMTPS id 76sm136764724eeh.0.2011.12.29.09.36.56 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 29 Dec 2011 09:36:57 -0800 (PST) From: Oleg Ginzburg To: freebsd-current@freebsd.org Date: Thu, 29 Dec 2011 21:37:33 +0400 User-Agent: KMail/1.13.7 (FreeBSD/9.0-PRERELEASE; KDE/4.7.3; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201112292137.33189.olevole@olevole.ru> X-Mailman-Approved-At: Thu, 29 Dec 2011 17:53:20 +0000 Subject: segfault from php/freebsd/dtrace X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 17:37:00 -0000 Hi maillist, I try to use dtrace + php/dtrace on the freebsd. In certain cases ive get Segmentation fault and don't understand what of subsystem has a problem. For this purpose: 1) have PHP with DTrace probes, for example: svn co https://svn.php.net/repository/php/php-src/trunk php-trunk php-trunk/buildconf ( needs bison && re2c ) php-trunk/configure --enable-dtrace ( then bulds as usual) 2) have FreeBSD with world/kernel Dtrace support 3) Run php for providing dtrace/php probes % php 4) Execute dtrace with PHP probes, for example, watch the errors: % dtrace -s /dev/stdin #pragma D option quiet php*:::error { printf("Error: %s in line %d (%s)\n", copyinstr(arg0), arg2, copyinstr(arg1)); } ^D 4) Run PHP with some error, for example: % php -E "thisisit" ^D Result: Dtrace ouput (this is ok): Error: syntax error, unexpected end of file in line 1 (Command line end code) % php -E "thisisit" Segmentation fault (core dumped) % gdb -c ./php.core /usr/local/bin/php GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Core was generated by `php'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libelf.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libelf.so.1 Reading symbols from /lib/libcrypt.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.5 Reading symbols from /lib/libz.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.6 Reading symbols from /usr/local/lib/libpcre.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /usr/lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/librt.so.1 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/local/lib/libxml2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxml2.so.5 Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00000008021c6a37 in strlen () from /lib/libc.so.7 [New Thread 802807400 (LWP 100326/php)] (gdb) file No executable file now. /usr/src/gnu/usr.bin/gdb/libgdb/fbsd-threads.c:484: internal-error: fbsd_thread_new_objfile: Assertion `proc_handle.pid == 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) n /usr/src/gnu/usr.bin/gdb/libgdb/fbsd-threads.c:484: internal-error: fbsd_thread_new_objfile: Assertion `proc_handle.pid == 0' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) n (gdb) bt #0 0x00000008021c6a37 in ?? () from /lib/libc.so.7 /usr/src/gnu/usr.bin/gdb/libgdb/../../../../contrib/gdb/gdb/dwarf2- frame.c:613: internal-error: dwarf2_frame_cache: Assertion `fde != NULL' failed. Backtrace for php.core: fbsd-strace# gdb -c ./php.core /usr/local/bin/php GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Core was generated by `php'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libelf.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libelf.so.1 Reading symbols from /lib/libcrypt.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libcrypt.so.5 Reading symbols from /lib/libz.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.6 Reading symbols from /usr/local/lib/libpcre.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /usr/lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/librt.so.1 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/local/lib/libxml2.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libxml2.so.5 Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libiconv.so.3 Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00000008021c6a37 in strlen () from /lib/libc.so.7 [New Thread 802807400 (LWP 100326/php)] (gdb) bt #0 0x00000008021c6a37 in strlen () from /lib/libc.so.7 #1 0x0000000000511b7a in vspprintf () #2 0x000000000050ecd7 in php_error_cb () #3 0x0000000000568ba4 in zend_error_noreturn () #4 0x000000000052e414 in zendparse () #5 0x000000000053c8fb in compile_string () #6 0x000000000055b523 in zend_eval_stringl () #7 0x000000000055b799 in zend_eval_stringl_ex () #8 0x000000000060bee0 in do_cli () #9 0x000000000060c6b4 in main () #10 0x0000000000419bbe in _start () #11 0x000000080098b000 in ?? () #12 0x0000000000000000 in ?? () #13 0x0000000000000003 in ?? () #14 0x00007fffffffdde8 in ?? () #15 0x00007fffffffddec in ?? () #16 0x00007fffffffddef in ?? () #17 0x0000000000000000 in ?? () #18 0x00007fffffffddf8 in ?? () #19 0x00007fffffffde03 in ?? () #20 0x00007fffffffde18 in ?? () #21 0x00007fffffffde24 in ?? () #22 0x00007fffffffde38 in ?? () #23 0x00007fffffffde8f in ?? () #24 0x00007fffffffde9e in ?? () #25 0x00007fffffffdea9 in ?? () #26 0x00007fffffffdeb3 in ?? () #27 0x00007fffffffdec4 in ?? () #28 0x00007fffffffded3 in ?? () #29 0x00007fffffffdee2 in ?? () #30 0x00007fffffffdef3 in ?? () #31 0x00007fffffffdefb in ?? () #32 0x00007fffffffdf0f in ?? () #33 0x00007fffffffdf1c in ?? () #34 0x00007fffffffdf28 in ?? () #35 0x00007fffffffdf43 in ?? () #36 0x00007fffffffdf5a in ?? () #37 0x00007fffffffdf64 in ?? () #38 0x0000000000000000 in ?? () #39 0x0000000000000003 in ?? () #40 0x0000000000400040 in ?? () #41 0x0000000000000004 in ?? () #42 0x0000000000000038 in ?? () #43 0x0000000000000005 in ?? () #44 0x0000000000000008 in ?? () #45 0x0000000000000006 in ?? () #46 0x0000000000001000 in ?? () #47 0x0000000000000008 in ?? () #48 0x0000000000000000 in ?? () #49 0x0000000000000009 in ?? () #50 0x0000000000419b30 in ?? () #51 0x0000000000000007 in ?? () #52 0x0000000800951000 in ?? () #53 0x000000000000000f in ?? () #54 #55 0x0000000000000000 in ?? () Previous frame inner to this frame (corrupt stack?) In a case when php it is compiled with debug symbols, Segfault is absent. --//Cut of /usr/src/gnu/usr.bin/gdb/libgdb/fbsd-threads.c//-- static void fbsd_thread_new_objfile (struct objfile *objfile) { td_err_e err; if (objfile == NULL) { /* All symbols have been discarded. If the thread_db target is active, deactivate it now. */ if (fbsd_thread_active) { gdb_assert (proc_handle.pid == 0); << Here is 484 string mentioned by backtrace << fbsd_thread_active = 0; } goto quit; } --//End of Cut//-- There are the ideas, what the part can cause a problem? From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 17:55:31 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03C96106566B; Thu, 29 Dec 2011 17:55:31 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 84FD88FC1D; Thu, 29 Dec 2011 17:55:30 +0000 (UTC) Received: by iadj38 with SMTP id j38so30286522iad.13 for ; Thu, 29 Dec 2011 09:55:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JIN9qfumQ9y4H48VJc6LSHY6LJcWUeOJJySLdlYRtRA=; b=v763tjif8KRCg/Wlo7oN2DDryH45oR28iwPFoBrjOwggGxg6iIXxv6yy+JbTeHWJca +LpQl/ri6Jh09HBRgHKu+l/E7vNKeT/AHO/OOUmI7zinP4As6qBiURnacIJjmqQwPJJ6 kodbj3qOSAoON+xB9XDhXLC1uphWldxsenCyQ= MIME-Version: 1.0 Received: by 10.42.159.195 with SMTP id m3mr38976140icx.33.1325181330085; Thu, 29 Dec 2011 09:55:30 -0800 (PST) Received: by 10.42.168.137 with HTTP; Thu, 29 Dec 2011 09:55:30 -0800 (PST) In-Reply-To: <4EFC9745.3050901@freebsd.org> References: <4EF904F2.4020109@FreeBSD.org> <4EFA1C9C.60601@FreeBSD.org> <4EFA7FD4.10600@freebsd.org> <201112290952.06834.jhb@freebsd.org> <4EFC9745.3050901@freebsd.org> Date: Thu, 29 Dec 2011 12:55:30 -0500 Message-ID: From: Mehmet Erol Sanliturk To: Nathan Whitehorn Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Lawrence Stewart , freebsd-current@freebsd.org, Ron McDowell , Doug Barton Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 17:55:31 -0000 On Thu, Dec 29, 2011 at 11:37 AM, Nathan Whitehorn wrote: > On 12/29/11 06:52, John Baldwin wrote: > >> On Tuesday, December 27, 2011 9:32:52 pm Lawrence Stewart wrote: >> >>> On 12/28/11 06:29, Doug Barton wrote: >>> >>>> On 12/27/2011 03:48, Lawrence Stewart wrote: >>>> >>>>> On the topic of Doug's actual question, I see minimal sense in >>>>> resurrecting sysinstall in head now. I would suggest it be done much >>>>> closer to (say, 6 months before) the 10.0 release cycle, if no suitable >>>>> post-installation configuration tool has materialised. >>>>> >>>> >>>> My concern about that approach is that 9.0 hasn't even been released yet >>>> and we've already seen changes that are going to make it hard to >>>> resurrect sysinstall if that's the decision we come to. Waiting another >>>> year or 2 would make it impossible. >>>> >>> >>> Which changes are you referring to? I would have thought a reverse merge >>> to undo the deletion of the sysinstall and old libdialog sources would >>> be very minimal work. We'd also probably need a few extra build system >>> changes to make sure old libdialog is perhaps statically compiled into >>> sysinstall as it would be the only in-tree consumer, but that's not hard >>> either. I may be lacking some imagination, but don't really see why it >>> would become harder the longer we wait. >>> >> >> I think Doug is worried that the list will just get longer, and I agree. >> Bits rot faster once they aren't part of the build. It is easy to delete >> sysinstall or trim it, it is not easy to resurrect it. Personally, the >> one >> time I used bsdinstall recently I found it to be a bit uneven, and not >> really >> a step forward for a new user compared to the "standard" install mode of >> sysinstall. It's biggest win is it's ability to do more disk >> configurations, >> but it seemed less user-friendly in almost every other regard (and even >> the >> disk editor seemd less user-friendly even if it had more functionality). >> >> > I'd appreciate any specific comments you might have, and especially > specific suggestions for improvements. Except from people who are old hands > at sysinstall, I've received almost universally positive comments on the > user experience. Patches would be even more appreciated, since real life > has intervened to steal most of my FreeBSD time. > -Nathan > I have installed FreeBSD 9.0 release candidates by using bsdinstall . I have selected only guided hard disk setup by selecting all defaults . For a less experienced person , by selecting the only defaults , and giving root password , a single user definition is sufficient to a successful install . With this structure of bsdinstall , I think , it is very well designed and expertly implemented . My suggestion would be , for immediate adjustment , after selecting "REBOOT" , since installer may know that install is from CD/DVD , may unmount CD/DVD , warn the user to remove CD/DVD , and request "press a key to continue" for booting . Since this part is missing , it is becoming necessary to enter a race between the user and the computer to find an interval to eject CD/DVD before captured by the BIOS . I did not use USB for install . I do not know how it is handled , but unmounting and extracting the USB stick and pressing a key to continue is also will be useful , if it is not already like that . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 18:18:37 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB6DE1065670; Thu, 29 Dec 2011 18:18:37 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 771868FC14; Thu, 29 Dec 2011 18:18:37 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so14559660obb.13 for ; Thu, 29 Dec 2011 10:18:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=JKXGOhmoaAm/2W8bEYxFp6W902BZ+ey4kHvJPagxYGU=; b=QLbAYpN0KyoG9bduizeXmcIfi32v57aJfTvaFoI0nvtrXrbaX0NSMp6g1alvVloFhE pmJDb6M6czuMlzUEpJ/CrIvYWsL91WH6oLa6fZzdnq0u45aHc0o+4F/hXoJJL2MvQX++ uofWbOgJfKIANkHhKAgRU+DqQ2E/BHk6hRV7I= MIME-Version: 1.0 Received: by 10.182.187.37 with SMTP id fp5mr7100276obc.21.1325182716762; Thu, 29 Dec 2011 10:18:36 -0800 (PST) Received: by 10.182.152.6 with HTTP; Thu, 29 Dec 2011 10:18:36 -0800 (PST) In-Reply-To: <4EFC5487.3080709@orange.fr> References: <4EFC0127.6030301@FreeBSD.org> <4EFC5487.3080709@orange.fr> Date: Thu, 29 Dec 2011 10:18:36 -0800 Message-ID: From: Garrett Cooper To: Claude Buisson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "Joseph S. Atkinson" , freebsd-current@freebsd.org Subject: Re: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 18:18:37 -0000 On Thu, Dec 29, 2011 at 3:52 AM, Claude Buisson wrote= : > On 12/29/2011 07:41, Garrett Cooper wrote: >> >> On Wed, Dec 28, 2011 at 9:56 PM, Joseph S. Atkinson >> =A0wrote: >>> >>> I am the maintainer of VLC, I have an outstanding PR (ports/162190) on >>> the >>> issue of cdda:// access. >>> >>> I can confirm this issues, but don't know enough about driver access to >>> fix >>> this myself. Doug Barton reports that cdcontrol(1) doesn't work for him= , >>> and >>> mplayer and audactiy also display issues running as non-root. >>> >>> Under 9.0-RC3 r228843, I get these errors on boot with no disc present = in >>> /dev/cd0 at all. >>> >>> (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 >>> 01 >>> 00 >>> (pass1:ahcich2:0:0:0): CAM status: ATA Status Error >>> (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT = ) >>> (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 >>> >>> These ports are fairly popular, but the problems may not lie exclusivel= y >>> with their assumptions about FreeBSD. I am running 10.0 on another >>> machine >>> specifically to test changes under src/sys/cam. >>> >>> I am worried that with the actual 9.0-RELEASE on the horizon, users wil= l >>> find show stopping problems using their disc drives. >> >> >> =A0 =A0 Try having users merge r228808 and r228847. If that works, then = I >> would press re@ produce another RC that fixes this. >> Thanks, >> -Garrett >> >> PS This is coming from a user that was annoyed by this gap with the >> ATA_CAM code. > > > As the submitter of ports/162190, I would firstly ask: > > Is the problem corrected by r228808 and r228847 in 10.0-CURRENT ? > > If not merging to 9.0 is useless. > > If yes I could test. That's why I suggested testing the patches :). Cheers, -Garrett From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 18:21:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85E17106567C; Thu, 29 Dec 2011 18:21:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 452A98FC25; Thu, 29 Dec 2011 18:21:29 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id C058346B1A; Thu, 29 Dec 2011 13:21:28 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5822BB91E; Thu, 29 Dec 2011 13:21:28 -0500 (EST) From: John Baldwin To: Nathan Whitehorn Date: Thu, 29 Dec 2011 12:04:00 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <4EF904F2.4020109@FreeBSD.org> <201112290952.06834.jhb@freebsd.org> <4EFC9745.3050901@freebsd.org> In-Reply-To: <4EFC9745.3050901@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112291204.01019.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 29 Dec 2011 13:21:28 -0500 (EST) Cc: Lawrence Stewart , freebsd-current@freebsd.org, Ron McDowell , Doug Barton Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 18:21:29 -0000 On Thursday, December 29, 2011 11:37:25 am Nathan Whitehorn wrote: > On 12/29/11 06:52, John Baldwin wrote: > > On Tuesday, December 27, 2011 9:32:52 pm Lawrence Stewart wrote: > >> On 12/28/11 06:29, Doug Barton wrote: > >>> On 12/27/2011 03:48, Lawrence Stewart wrote: > >>>> On the topic of Doug's actual question, I see minimal sense in > >>>> resurrecting sysinstall in head now. I would suggest it be done much > >>>> closer to (say, 6 months before) the 10.0 release cycle, if no suitable > >>>> post-installation configuration tool has materialised. > >>> > >>> My concern about that approach is that 9.0 hasn't even been released yet > >>> and we've already seen changes that are going to make it hard to > >>> resurrect sysinstall if that's the decision we come to. Waiting another > >>> year or 2 would make it impossible. > >> > >> Which changes are you referring to? I would have thought a reverse merge > >> to undo the deletion of the sysinstall and old libdialog sources would > >> be very minimal work. We'd also probably need a few extra build system > >> changes to make sure old libdialog is perhaps statically compiled into > >> sysinstall as it would be the only in-tree consumer, but that's not hard > >> either. I may be lacking some imagination, but don't really see why it > >> would become harder the longer we wait. > > > > I think Doug is worried that the list will just get longer, and I agree. > > Bits rot faster once they aren't part of the build. It is easy to delete > > sysinstall or trim it, it is not easy to resurrect it. Personally, the one > > time I used bsdinstall recently I found it to be a bit uneven, and not really > > a step forward for a new user compared to the "standard" install mode of > > sysinstall. It's biggest win is it's ability to do more disk configurations, > > but it seemed less user-friendly in almost every other regard (and even the > > disk editor seemd less user-friendly even if it had more functionality). > > > > I'd appreciate any specific comments you might have, and especially > specific suggestions for improvements. Except from people who are old > hands at sysinstall, I've received almost universally positive comments > on the user experience. Patches would be even more appreciated, since > real life has intervened to steal most of my FreeBSD time. A way to select from available partition types (UFS, boot, swap, ZFS, etc.) rather than requiring the user to remember the 'freebsd-xxx' string would be one improvement. At the time I was more worried about getting my box up and running than taking detailed notes. :) The lack of a /compat link is another issue people have raised. The lack of a shell running on ttyv3 during the install is probably a feature I think many "advanced" users would miss. I missed having the debug output on ttyv1 as well. At work here it would be a deal-killer for my sysadmins to not have ttyv3. We use a custom installer for our boxes that I wrote as a shell script and it still does debug/verbose output on ttyv1. It doesn't start an explicit shell on ttyv3, but I have a login prompt there that they can use and I've thought about even replacing that with an explicit chroot'd shell ala sysinstall. I can't count the number of times I've used the shell on ttyv3 during installs. For new users the ability to browse the packages, etc. I think is important. It certainly was for me back when I first installed FreeBSD back in college. I don't recall seeing that option during the one install I did of 9. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 18:37:43 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E34C61065676 for ; Thu, 29 Dec 2011 18:37:43 +0000 (UTC) (envelope-from pfg@freebsd.org) Received: from nm16-vm5.bullet.mail.ne1.yahoo.com (nm16-vm5.bullet.mail.ne1.yahoo.com [98.138.91.238]) by mx1.freebsd.org (Postfix) with SMTP id 7BF828FC1B for ; Thu, 29 Dec 2011 18:37:43 +0000 (UTC) Received: from [98.138.90.50] by nm16.bullet.mail.ne1.yahoo.com with NNFMP; 29 Dec 2011 18:23:59 -0000 Received: from [98.138.89.245] by tm3.bullet.mail.ne1.yahoo.com with NNFMP; 29 Dec 2011 18:23:59 -0000 Received: from [127.0.0.1] by omp1059.mail.ne1.yahoo.com with NNFMP; 29 Dec 2011 18:23:59 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 841695.53387.bm@omp1059.mail.ne1.yahoo.com Received: (qmail 94062 invoked by uid 60001); 29 Dec 2011 18:23:58 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1325183038; bh=o/NmQVZlTDTkjsv4ej3C2gvxRj81/+F6zS0y6OPN0sw=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=0MccdPYSTHX2JOgmlIQCVm4QjNdPG7cXM2sTTZSR6by/kjUeb3ibGWU4jMm4vaBVAfKyih9vbMl/PMUCr3LZl3jiGBU7dteKntSfNMq1t8hVS6+z0yL90fhbgtNTOt1m77R8UmTv4eU0KtDtFLQ85mZ7+JyikOz/IY/cfQV2+7U= X-YMail-OSG: toH0.IUVM1lhpQdaYs9DvKsdgB.2e1_PYHHzIgbHainFgq9 GvftoSyRn_Hv4hbHX2lPrwixUsX_M3RgPjzEswktrlR9Lf4BLbdVgU2pxdVf JONKJxDI9TToUJPh_7Q0nm6w3AaNmgswoGqX5DFBLeWjtKZCPykzbxRNWm_v UbjtHBMbHuixKNvcX__8ArU9D0ESOKIRX9624xHQQctkbhzYEc9ZSgqgBSk0 Qc0K9N.CdNkfAe5d0wCf4YENivgXBjHu36nID.05kTyhT8rhBGGTnBrP96yl gvqZ.3fNW2whMXmUcKptiT9H0zGMsdZNuHnbyZqzW.QKAgBGzSR7GrvjWviy ecMJ7.cYPnOVntf2tclwNgu06npf9kcow3YgC9MX1n23zT5Mc7_P84_Lgkxe ciWyI9.2oSQs4GpZfzA76Hmrzpbyc78yc.Ln4L5hMcJQwpwZLSMZ.w4Uul3t BfxRd_q5YQGqvhem.U9rF2AwzppXUK0T04lmoWz6ymV1pwpgATnZwhYWP4la nW4Q94ns- Received: from [200.118.157.7] by web113516.mail.gq1.yahoo.com via HTTP; Thu, 29 Dec 2011 10:23:58 PST X-RocketYMMF: giffunip X-Mailer: YahooMailClassic/15.0.4 YahooMailWebService/0.8.115.331698 Message-ID: <1325183038.93200.YahooMailClassic@web113516.mail.gq1.yahoo.com> Date: Thu, 29 Dec 2011 10:23:58 -0800 (PST) From: Pedro Giffuni To: Nathan Whitehorn In-Reply-To: <4EFC9745.3050901@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfg@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 18:37:44 -0000 =0A=0A--- Gio 29/12/11, Nathan Whitehorn ha scritt= o:=0A...=0A> =0A> I'd appreciate any specific comments you might have, and= =0A> especially =0A> specific suggestions for improvements. Except from peo= ple=0A> who are old =0A> hands at sysinstall, I've received almost universa= lly=0A> positive comments =0A> on the user experience. Patches would be eve= n more=0A> appreciated, since =0A> real life has intervened to steal most o= f my FreeBSD time.=0A> -Nathan=0A>=0A=0AFWIW;=0A=0AI have practically given= up on installing FreeBSD lately=0Aand I mostly use PC-BSD. I mainly see tw= o big issues:=0A=0A-X.Org has become very difficult to install. Setting up= =0Ahald and friends, not to mention that you have to choose=0Acarefully you= r hardware previously. It's a nightmare.=0A- I am OK with sysinstall disapp= earing: however it was=0Anice to have all the setup tools in one place. How= am=0AI supposed to install prebuilt packages (and the myriad=0Aof dependen= cies) from now on? Ports are cool but having=0Ato wait to rebuild gcc to be= able to use scilab is a=0Anonsense.=0A=0APC-BSD is not without problems th= ough. In my system=0Ait wants to use "latam" kbd which doesn't even=0Aexist= AFAICT.=0A=0AJust my $0.02, I know writing a replacement for the=0Afull bl= own sysinstall is a rather heroic thing to do.=0A=0ARegards,=0A=0APedro.=0A From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 18:52:36 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F31C8106566C; Thu, 29 Dec 2011 18:52:35 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id AE9038FC16; Thu, 29 Dec 2011 18:52:35 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id pBTIqYNq034730; Thu, 29 Dec 2011 11:52:34 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id pBTIqYh3034727; Thu, 29 Dec 2011 11:52:34 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Thu, 29 Dec 2011 11:52:34 -0700 (MST) From: Warren Block To: John Baldwin In-Reply-To: <201112291204.01019.jhb@freebsd.org> Message-ID: References: <4EF904F2.4020109@FreeBSD.org> <201112290952.06834.jhb@freebsd.org> <4EFC9745.3050901@freebsd.org> <201112291204.01019.jhb@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Thu, 29 Dec 2011 11:52:34 -0700 (MST) Cc: Lawrence Stewart , freebsd-current@freebsd.org, Ron McDowell , Nathan Whitehorn , Doug Barton Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 18:52:36 -0000 On Thu, 29 Dec 2011, John Baldwin wrote: > > A way to select from available partition types (UFS, boot, swap, ZFS, etc.) > rather than requiring the user to remember the 'freebsd-xxx' string would be > one improvement. There are PRs for that and several other common suggestions: http://www.freebsd.org/cgi/query-pr-summary.cgi?&text=bsdinstall From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 19:09:00 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43596106566B for ; Thu, 29 Dec 2011 19:09:00 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id D10D98FC12 for ; Thu, 29 Dec 2011 19:08:59 +0000 (UTC) Received: by werb13 with SMTP id b13so11913139wer.13 for ; Thu, 29 Dec 2011 11:08:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=rdzoyGfTYyOWyqzjxJkTJPRWVEElzyvRuB8AD1a36J0=; b=qDdPBaeymyTxivn+HeceLRQlztPhbqE7TvcizyE5vY1NNWb+UOvV0vKse0dKuPVKIV 3nBmMfLDNvEo7CRzfjsi1RQRi6jW4J1PzrQ1p6NO9ka31HjBpgdQnOKXyGMfWNYUNOvd zl9fTBHxWAULEkN35pdn0yS2AL/30H5D9/4iA= Received: by 10.216.136.232 with SMTP id w82mr20398306wei.46.1325183979162; Thu, 29 Dec 2011 10:39:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.177.68 with HTTP; Thu, 29 Dec 2011 10:39:18 -0800 (PST) In-Reply-To: <4EFC1260.1060503@luddite.com.au> References: <4EFC1260.1060503@luddite.com.au> From: Renato Botelho Date: Thu, 29 Dec 2011 16:39:18 -0200 Message-ID: To: "Peter J. Cherny" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: Apropos Removal of sysinstall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 19:09:00 -0000 On Thu, Dec 29, 2011 at 5:10 AM, Peter J. Cherny wr= ote: > Rather than hijack the previous thread, > it's probably time to make a few comments on the current and future > installation and use of ZFS FreeBSD. > > I've used both Solaris and FreeBSD since nearly day one for both OSs, so > have a deal of familiarity in their use. > > I believe removal of sysinstall exposes the community's blindness to a ma= jor > parts of it's future, ZFS root. > > Other than following arcane recipes, > the only way to create a system with ZFS root is by using Martin Matu=C5= =A1ka's > excellent mfsboot images. IIRC, PCBSD installer can install a regular FreeBSD on ZFS. --=20 Renato Botelho From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 19:12:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51F841065676 for ; Thu, 29 Dec 2011 19:12:32 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 3B2008FC0C for ; Thu, 29 Dec 2011 19:12:32 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1RgLOv-0001tb-Ny; Thu, 29 Dec 2011 19:12:30 +0000 Date: Fri, 30 Dec 2011 04:12:28 +0900 Message-ID: From: Randy Bush To: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= In-Reply-To: <4EFC85AB.8070303@t-hosting.hu> References: <4EFC85AB.8070303@t-hosting.hu> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: FreeBSD Current Subject: Re: grep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 19:12:32 -0000 >> FreeBSD ran.psg.com 10.0-CURRENT FreeBSD 10.0-CURRENT #4: Sat Dec 24 12:33:51 UTC 2011 root@ran.psg.com:/usr/obj/usr/src/sys/RAN amd64 >> >> % echo foo | grep foo >> % > > What about 'grep -V'? Or 'which grep'? turns out that a zero length grep had been installed updated to new sources, rebuilt, and it's all good. randy From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 19:55:16 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4EEF106566B; Thu, 29 Dec 2011 19:55:16 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id 754648FC0A; Thu, 29 Dec 2011 19:55:16 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LWZ00E0IE03XU00@smtpauth3.wiscmail.wisc.edu>; Thu, 29 Dec 2011 13:55:15 -0600 (CST) Received: from wanderer.tachypleus.net ([unknown] [76.210.77.223]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LWZ008C0DZYJ020@smtpauth3.wiscmail.wisc.edu>; Thu, 29 Dec 2011 13:55:11 -0600 (CST) Date: Thu, 29 Dec 2011 11:55:10 -0800 From: Nathan Whitehorn In-reply-to: To: Warren Block Message-id: <4EFCC59E.8050508@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.77.223 X-Spam-PmxInfo: Server=avs-11, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.12.29.194815, SenderIP=76.210.77.223 References: <4EF904F2.4020109@FreeBSD.org> <201112290952.06834.jhb@freebsd.org> <4EFC9745.3050901@freebsd.org> <201112291204.01019.jhb@freebsd.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111213 Thunderbird/8.0 Cc: freebsd-current@freebsd.org Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 19:55:16 -0000 On 12/29/11 10:52, Warren Block wrote: > On Thu, 29 Dec 2011, John Baldwin wrote: >> >> A way to select from available partition types (UFS, boot, swap, ZFS, >> etc.) >> rather than requiring the user to remember the 'freebsd-xxx' string >> would be >> one improvement. > > There are PRs for that and several other common suggestions: > > http://www.freebsd.org/cgi/query-pr-summary.cgi?&text=bsdinstall The problem with, say, a dropdown menu is that libdialog doesn't provide a combination dropdown-and-text-entry window. The only alternative would be to split partition creation into two screens (first a list of types, and later a thing to set it up). That has the disadvantage of requiring two screens, or a third if you want alternate types. The shell on v3 is a good idea, and belongs in /usr/src/release/rc.local, where it already handles some things like this (including figuring out if the console is a serial port, which needs to be taken into account). -Nathan From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 20:03:30 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C9F41065675 for ; Thu, 29 Dec 2011 20:03:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id CF1908FC1B for ; Thu, 29 Dec 2011 20:03:29 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 6E28246B06 for ; Thu, 29 Dec 2011 15:03:29 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D1E47B93F for ; Thu, 29 Dec 2011 15:03:28 -0500 (EST) From: John Baldwin To: current@freebsd.org Date: Thu, 29 Dec 2011 14:48:16 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201112291448.16353.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 29 Dec 2011 15:03:28 -0500 (EST) Cc: Subject: [PATCH] Remove use of bus space tag/handle's from ichwd(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 20:03:30 -0000 This patch updates the ichwd(4) driver to use the built-in bus space tag and handle from the relevent resource objects instead of storing duplicate copies in its softc. Index: dev/ichwd/ichwd.c =================================================================== --- dev/ichwd/ichwd.c (revision 228954) +++ dev/ichwd/ichwd.c (working copy) @@ -198,26 +198,26 @@ static devclass_t ichwd_devclass; #define ichwd_read_tco_1(sc, off) \ - bus_space_read_1((sc)->tco_bst, (sc)->tco_bsh, (off)) + bus_read_1((sc)->tco_res, (off)) #define ichwd_read_tco_2(sc, off) \ - bus_space_read_2((sc)->tco_bst, (sc)->tco_bsh, (off)) + bus_read_2((sc)->tco_res, (off)) #define ichwd_read_tco_4(sc, off) \ - bus_space_read_4((sc)->tco_bst, (sc)->tco_bsh, (off)) + bus_read_4((sc)->tco_res, (off)) #define ichwd_read_smi_4(sc, off) \ - bus_space_read_4((sc)->smi_bst, (sc)->smi_bsh, (off)) + bus_read_4((sc)->smi_res, (off)) #define ichwd_read_gcs_4(sc, off) \ - bus_space_read_4((sc)->gcs_bst, (sc)->gcs_bsh, (off)) + bus_read_4((sc)->gcs_res, (off)) #define ichwd_write_tco_1(sc, off, val) \ - bus_space_write_1((sc)->tco_bst, (sc)->tco_bsh, (off), (val)) + bus_write_1((sc)->tco_res, (off), (val)) #define ichwd_write_tco_2(sc, off, val) \ - bus_space_write_2((sc)->tco_bst, (sc)->tco_bsh, (off), (val)) + bus_write_2((sc)->tco_res, (off), (val)) #define ichwd_write_tco_4(sc, off, val) \ - bus_space_write_4((sc)->tco_bst, (sc)->tco_bsh, (off), (val)) + bus_write_4((sc)->tco_res, (off), (val)) #define ichwd_write_smi_4(sc, off, val) \ - bus_space_write_4((sc)->smi_bst, (sc)->smi_bsh, (off), (val)) + bus_write_4((sc)->smi_res, (off), (val)) #define ichwd_write_gcs_4(sc, off, val) \ - bus_space_write_4((sc)->gcs_bst, (sc)->gcs_bsh, (off), (val)) + bus_write_4((sc)->gcs_res, (off), (val)) #define ichwd_verbose_printf(dev, ...) \ do { \ @@ -519,8 +519,6 @@ device_printf(dev, "unable to reserve SMI registers\n"); goto fail; } - sc->smi_bst = rman_get_bustag(sc->smi_res); - sc->smi_bsh = rman_get_bushandle(sc->smi_res); sc->tco_rid = 1; sc->tco_res = bus_alloc_resource(dev, SYS_RES_IOPORT, &sc->tco_rid, @@ -530,8 +528,6 @@ device_printf(dev, "unable to reserve TCO registers\n"); goto fail; } - sc->tco_bst = rman_get_bustag(sc->tco_res); - sc->tco_bsh = rman_get_bushandle(sc->tco_res); sc->gcs_rid = 0; if (sc->ich_version >= 6) { @@ -541,12 +537,6 @@ device_printf(dev, "unable to reserve GCS registers\n"); goto fail; } - sc->gcs_bst = rman_get_bustag(sc->gcs_res); - sc->gcs_bsh = rman_get_bushandle(sc->gcs_res); - } else { - sc->gcs_res = 0; - sc->gcs_bst = 0; - sc->gcs_bsh = 0; } if (ichwd_clear_noreboot(sc) != 0) Index: dev/ichwd/ichwd.h =================================================================== --- dev/ichwd/ichwd.h (revision 228954) +++ dev/ichwd/ichwd.h (working copy) @@ -48,18 +48,12 @@ int smi_enabled; int smi_rid; struct resource *smi_res; - bus_space_tag_t smi_bst; - bus_space_handle_t smi_bsh; int tco_rid; struct resource *tco_res; - bus_space_tag_t tco_bst; - bus_space_handle_t tco_bsh; int gcs_rid; struct resource *gcs_res; - bus_space_tag_t gcs_bst; - bus_space_handle_t gcs_bsh; eventhandler_tag ev_tag; }; -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 20:21:44 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 202AA106564A; Thu, 29 Dec 2011 20:21:44 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id C08C18FC08; Thu, 29 Dec 2011 20:21:43 +0000 (UTC) Received: by iadj38 with SMTP id j38so30501779iad.13 for ; Thu, 29 Dec 2011 12:21:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=hbzn0H2Y98XxsyvIY7ZfUF62hVR6TVT+CSB2bODVmfk=; b=vUL/k6uS3TE+YqDb+UGHajPOE2ZgAUNML/qGDF5zzn3IW1aHmBvYRlqURhu3WwTuhw dl9xWqeYbiDU1jaK0sErcandILTMeGQVQr0hJM81OHKPzg8CX/7j1pZ8m3iRiQquul0l 1qTPN9HgCQa5IuGd7zmoyDb8JL2D3Gu69QphM= Received: by 10.50.153.135 with SMTP id vg7mr43234582igb.12.1325190103254; Thu, 29 Dec 2011 12:21:43 -0800 (PST) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.207.7 with HTTP; Thu, 29 Dec 2011 12:21:11 -0800 (PST) In-Reply-To: <1325183038.93200.YahooMailClassic@web113516.mail.gq1.yahoo.com> References: <4EFC9745.3050901@freebsd.org> <1325183038.93200.YahooMailClassic@web113516.mail.gq1.yahoo.com> From: Chris Rees Date: Thu, 29 Dec 2011 20:21:11 +0000 X-Google-Sender-Auth: HqJdzCQvx1vvyZno_yleawAaIA4 Message-ID: To: pfg@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org, Nathan Whitehorn Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 20:21:44 -0000 On 29 December 2011 18:23, Pedro Giffuni wrote: > --- Gio 29/12/11, Nathan Whitehorn ha scritto: >> I'd appreciate any specific comments you might have, and >> especially >> specific suggestions for improvements. Except from people >> who are old >> hands at sysinstall, I've received almost universally >> positive comments >> on the user experience. Patches would be even more >> appreciated, since >> real life has intervened to steal most of my FreeBSD time. >> -Nathan >> > > FWIW; > > I have practically given up on installing FreeBSD lately > and I mostly use PC-BSD. I mainly see two big issues: > > -X.Org has become very difficult to install. Setting up > hald and friends, not to mention that you have to choose > carefully your hardware previously. It's a nightmare. I've not found that... installing xorg-drivers with the correct options is hassle-free... have you posted these problems to -x11@? > - I am OK with sysinstall disappearing: however it was > nice to have all the setup tools in one place. How am > I supposed to install prebuilt packages (and the myriad > of dependencies) from now on? Ports are cool but having > to wait to rebuild gcc to be able to use scilab is a > nonsense. Use packages, we do do them! Chris > PC-BSD is not without problems though. In my system > it wants to use "latam" kbd which doesn't even > exist AFAICT. > > Just my $0.02, I know writing a replacement for the > full blown sysinstall is a rather heroic thing to do. > > Regards, > > Pedro. From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 20:26:09 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE595106566B; Thu, 29 Dec 2011 20:26:08 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 5357A8FC14; Thu, 29 Dec 2011 20:26:08 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id 4F61F821; Thu, 29 Dec 2011 21:26:06 +0100 (CET) Date: Thu, 29 Dec 2011 21:25:02 +0100 From: Pawel Jakub Dawidek To: John Baldwin Message-ID: <20111229202501.GA1889@garage.freebsd.pl> References: <20111022084931.GD1697@garage.freebsd.pl> <201112200952.44690.jhb@freebsd.org> <1632420869.20111225180133@yandex.ru> <201112291112.59912.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="y0ulUmNC+osPPQO6" Content-Disposition: inline In-Reply-To: <201112291112.59912.jhb@freebsd.org> X-OS: FreeBSD 9.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Andre Oppermann , freebsd-net@freebsd.org, =?utf-8?B?0JrQvtC90YzQutC+0LIg0JXQstCz0LXQvdC40Lk=?= , freebsd-current@freebsd.org, Kostik Belousov , Lawrence Stewart Subject: Re: 9.0-RC1 panic in tcp_input: negative winow. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 20:26:09 -0000 --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 29, 2011 at 11:12:59AM -0500, John Baldwin wrote: > On Sunday, December 25, 2011 11:01:33 am =D0=9A=D0=BE=D0=BD=D1=8C=D0=BA= =D0=BE=D0=B2 =D0=95=D0=B2=D0=B3=D0=B5=D0=BD=D0=B8=D0=B9 wrote: > > =D0=97=D0=B4=D1=80=D0=B0=D0=B2=D1=81=D1=82=D0=B2=D1=83=D0=B9=D1=82=D0= =B5, John. > >=20 > > =D0=92=D1=8B =D0=BF=D0=B8=D1=81=D0=B0=D0=BB=D0=B8 20 =D0=B4=D0=B5=D0=BA= =D0=B0=D0=B1=D1=80=D1=8F 2011 =D0=B3., 16:52:44: > >=20 > > JB> On Saturday, December 17, 2011 6:21:27 pm Pawel Jakub Dawidek wrote: > > >> On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote: > > >> > An update. I've sent Pawel a testing patch to see if my hypothesi= s is correct > > >> > (www.freebsd.org/~jhb/patches/tcp_negwin_test.patch). If it is th= en I intend > > >> > to commit www.freebsd.org/~jhb/patches/tcp_negwin2.patch as the fi= x. > > >>=20 > > >> Unfortunately it paniced today. Take a look at: > > >>=20 > > >> http://people.freebsd.org/~pjd/misc/tcp_panic.jpg > >=20 > > JB> Ok, the one use case I was worried about is happening regularly bef= ore your > > JB> panic, so that is good. Can you use gdb to figure out which call to > > JB> tcp_output() is actually panic'ing? I wonder if it is this case: > >=20 > > JB> /* > > JB> * Return any desired output. > > JB> */ > > JB> if (needoutput || (tp->t_flags & TF_ACKNOW)) { > > JB> (void) tcp_output(tp); > > JB> /* XXX: Debug */ > > JB> KASSERT(SEQ_GEQ(tp->rcv_adv, tp->rcv_nxt), > > JB> ("tcp_input: negative window after ACK")); > >=20 > > JB> And if 'needoutput' is true, but TF_ACKNOW is not set, and tcp_outp= ut() decides > > JB> to not do anything. I've updated tcp_negwin_test.patch to not pani= c if that call > > JB> to tcp_output() doesn't actually send a packet. Please re-test. > >=20 > >=20 > > # uname -a > > FreeBSD meta-up 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #4: Sat Dec 24 13= :59:20 EET 2011 @:/usr/obj/usr/src/sys/KES_KERN_v10 i386 > >=20 > > rebooting once per day. Now I compile kernel with debug options. > > Can you advice me which and where I find debug info when it will > > reboting next time? so I can help to debug problem >=20 > Are you using the patch at the URL above (tcp_negwin_test.patch)? If not, > can you try applying that patch and seeing if you still get any panics? I applied 1.5 days ago, so far now panics and no other messages. I modified the patch a bit to not panic, but print a message when panic was suppose to happen. This box is too valuable for me to panic it too often. Because there were no debug messages I understand that the scenerio didn't happen yet and not that the problem is fixed, right? --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com --y0ulUmNC+osPPQO6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk78zJ0ACgkQForvXbEpPzR7RACcC+FS4llTUDG0av+6s26iwxl3 OOsAoPTMGfHUwJg+TgWm9gdJb+NXuIB5 =dh23 -----END PGP SIGNATURE----- --y0ulUmNC+osPPQO6-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 20:27:30 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6379B106566C; Thu, 29 Dec 2011 20:27:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 394268FC0A; Thu, 29 Dec 2011 20:27:30 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id E67B446B09; Thu, 29 Dec 2011 15:27:29 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id EFA6FB91E; Thu, 29 Dec 2011 15:27:28 -0500 (EST) From: John Baldwin To: Nathan Whitehorn Date: Thu, 29 Dec 2011 15:04:43 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <4EF904F2.4020109@FreeBSD.org> <4EFCC59E.8050508@freebsd.org> In-Reply-To: <4EFCC59E.8050508@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112291504.43430.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 29 Dec 2011 15:27:29 -0500 (EST) Cc: Warren Block , freebsd-current@freebsd.org Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 20:27:30 -0000 On Thursday, December 29, 2011 2:55:10 pm Nathan Whitehorn wrote: > On 12/29/11 10:52, Warren Block wrote: > > On Thu, 29 Dec 2011, John Baldwin wrote: > >> > >> A way to select from available partition types (UFS, boot, swap, ZFS, > >> etc.) > >> rather than requiring the user to remember the 'freebsd-xxx' string > >> would be > >> one improvement. > > > > There are PRs for that and several other common suggestions: > > > > http://www.freebsd.org/cgi/query-pr-summary.cgi?&text=bsdinstall > > The problem with, say, a dropdown menu is that libdialog doesn't provide > a combination dropdown-and-text-entry window. The only alternative would > be to split partition creation into two screens (first a list of types, > and later a thing to set it up). That has the disadvantage of requiring > two screens, or a third if you want alternate types. sysinstall just popped up a new modal dialog with a menu to pick the partition type. Would something like that work in bsdinstall? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 20:49:26 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1554A1065670 for ; Thu, 29 Dec 2011 20:49:26 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 987F18FC14 for ; Thu, 29 Dec 2011 20:49:25 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 8568BE6226; Thu, 29 Dec 2011 20:49:24 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=4eRYKBCl2/+g dQwodQ/ode9pgBw=; b=tC/VhW9cSwP6CPUTtsYmQkYpxl+cXNHDaAKcqMZvKNCk FzWOOGoFIU8RQ6MZGEScb0tG3voWL+zO9kcLreHf7dWGAK5HpnoZy1u7N4UyM8ZA HF6mjGzbQarFN7zKTDAYZecdI31kq7gvQGyobGHp5ctChJyq5dR4nyJZtHqonho= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=JkiG++ iSqBqgnqFPDwYX1Rpu+9HeRa0H51gMFtJyPYW1rIYcE5ViHcQDjMoCcyJGdcb+n6 Ragw43Vo9+DPbdOn3ZSnmE6gxYIJHCcxldENffcTSAM2CGekKfqgYzCB5xKlNjJ1 gfaIIeoOqI5T8K7JRWwiskYN+PCnFHQXm7W0w= Received: from [192.168.1.69] (188-220-36-32.zone11.bethere.co.uk [188.220.36.32]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 4B9F0E6225; Thu, 29 Dec 2011 20:49:24 +0000 (GMT) Message-ID: <4EFCD252.7080209@cran.org.uk> Date: Thu, 29 Dec 2011 20:49:22 +0000 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Renato Botelho References: <4EFC1260.1060503@luddite.com.au> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, "Peter J. Cherny" Subject: Re: Apropos Removal of sysinstall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 20:49:26 -0000 On 29/12/2011 18:39, Renato Botelho wrote: > IIRC, PCBSD installer can install a regular FreeBSD on ZFS. It can do, but you're left with a /very/ basic installation - the hostname, network interfaces etc. aren't configured, which could be a problem for some people. If I thought there would be any support for it, I'd try and find time to plug in the sade(4) rewrite into sysinstall - it has a rather nice UI and supports ZFS. -- Bruce Cran From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 20:51:39 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C93501065676; Thu, 29 Dec 2011 20:51:39 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 7D6E48FC14; Thu, 29 Dec 2011 20:51:39 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id B1555E6226; Thu, 29 Dec 2011 20:51:38 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=bUXyDGzKX1O9 yIKSbjkdg2JSp9I=; b=txNIqPShzLrL2x+A/WIWe8vt0shySIhnRCDU2YPBKlGF hbIdmsM0mBYctOIBtISKABxlFUSM/EQuHoG+/NscFERe44fZ7OoZt+QFvl1V3Xy+ f2VwfBvUph+9rdK+zsDaIRd9uaQOmtQRI4JaEjP3mt6/NI5pHlzuHvkWJ6Na/Z0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=DK5bCP 51jbYgsGi8qEWjD/gjy7z77YT2dnO7/3b0kZ4Zb6RvEVJY03oaiODgbTX8iKqqIR MN2eG/ArFFb1lR81vhZBT/o4m0yIids07AqxjZ7yzZYYbJgjHeZi67YR77PjHhsI qbabTEHaAAfojfER2ZQ8jhwBvavxZmlqQWvy0= Received: from [192.168.1.69] (188-220-36-32.zone11.bethere.co.uk [188.220.36.32]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 688BBE6225; Thu, 29 Dec 2011 20:51:38 +0000 (GMT) Message-ID: <4EFCD2D8.50505@cran.org.uk> Date: Thu, 29 Dec 2011 20:51:36 +0000 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Nathan Whitehorn References: <4EF904F2.4020109@FreeBSD.org> <4EFA1C9C.60601@FreeBSD.org> <4EFA7FD4.10600@freebsd.org> <201112290952.06834.jhb@freebsd.org> <4EFC9745.3050901@freebsd.org> In-Reply-To: <4EFC9745.3050901@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Lawrence Stewart , freebsd-current@freebsd.org, Ron McDowell , Doug Barton Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 20:51:39 -0000 On 29/12/2011 16:37, Nathan Whitehorn wrote: > I'd appreciate any specific comments you might have, and especially > specific suggestions for improvements. Except from people who are old > hands at sysinstall, I've received almost universally positive > comments on the user experience. Patches would be even more > appreciated, since real life has intervened to steal most of my > FreeBSD time. There was talk in the past that any future installer should be based around the pc-sysinstall backend - has there been any progress towards moving bsdinstall to it? -- Bruce Cran From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 21:21:05 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C5E51065672; Thu, 29 Dec 2011 21:21:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1BAD78FC0C; Thu, 29 Dec 2011 21:21:05 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id ACD4846B0D; Thu, 29 Dec 2011 16:21:04 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 29175B93A; Thu, 29 Dec 2011 16:21:04 -0500 (EST) From: John Baldwin To: Pawel Jakub Dawidek Date: Thu, 29 Dec 2011 16:18:42 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <20111022084931.GD1697@garage.freebsd.pl> <201112291112.59912.jhb@freebsd.org> <20111229202501.GA1889@garage.freebsd.pl> In-Reply-To: <20111229202501.GA1889@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201112291618.43170.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 29 Dec 2011 16:21:04 -0500 (EST) Cc: =?utf-8?q?=D0=9A=D0=BE=D0=BD=D1=8C=D0=BA=D0=BE=D0=B2?=, Andre Oppermann , freebsd-net@freebsd.org, =?utf-8?q?_=D0=95=D0=B2=D0=B3=D0=B5=D0=BD=D0=B8=D0=B9?= , freebsd-current@freebsd.org, Kostik Belousov , Lawrence Stewart Subject: Re: 9.0-RC1 panic in tcp_input: negative winow. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 21:21:05 -0000 On Thursday, December 29, 2011 3:25:02 pm Pawel Jakub Dawidek wrote: > On Thu, Dec 29, 2011 at 11:12:59AM -0500, John Baldwin wrote: > > On Sunday, December 25, 2011 11:01:33 am =D0=9A=D0=BE=D0=BD=D1=8C=D0=BA= =D0=BE=D0=B2 =D0=95=D0=B2=D0=B3=D0=B5=D0=BD=D0=B8=D0=B9 wrote: > > > =D0=97=D0=B4=D1=80=D0=B0=D0=B2=D1=81=D1=82=D0=B2=D1=83=D0=B9=D1=82=D0= =B5, John. > > >=20 > > > =D0=92=D1=8B =D0=BF=D0=B8=D1=81=D0=B0=D0=BB=D0=B8 20 =D0=B4=D0=B5=D0= =BA=D0=B0=D0=B1=D1=80=D1=8F 2011 =D0=B3., 16:52:44: > > >=20 > > > JB> On Saturday, December 17, 2011 6:21:27 pm Pawel Jakub Dawidek wro= te: > > > >> On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote: > > > >> > An update. I've sent Pawel a testing patch to see if my hypothe= sis is correct > > > >> > (www.freebsd.org/~jhb/patches/tcp_negwin_test.patch). If it is = then I intend > > > >> > to commit www.freebsd.org/~jhb/patches/tcp_negwin2.patch as the = fix. > > > >>=20 > > > >> Unfortunately it paniced today. Take a look at: > > > >>=20 > > > >> http://people.freebsd.org/~pjd/misc/tcp_panic.jpg > > >=20 > > > JB> Ok, the one use case I was worried about is happening regularly b= efore your > > > JB> panic, so that is good. Can you use gdb to figure out which call= to > > > JB> tcp_output() is actually panic'ing? I wonder if it is this case: > > >=20 > > > JB> /* > > > JB> * Return any desired output. > > > JB> */ > > > JB> if (needoutput || (tp->t_flags & TF_ACKNOW)) { > > > JB> (void) tcp_output(tp); > > > JB> /* XXX: Debug */ > > > JB> KASSERT(SEQ_GEQ(tp->rcv_adv, tp->rcv_nxt), > > > JB> ("tcp_input: negative window after ACK")); > > >=20 > > > JB> And if 'needoutput' is true, but TF_ACKNOW is not set, and tcp_ou= tput() decides > > > JB> to not do anything. I've updated tcp_negwin_test.patch to not pa= nic if that call > > > JB> to tcp_output() doesn't actually send a packet. Please re-test. > > >=20 > > >=20 > > > # uname -a > > > FreeBSD meta-up 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #4: Sat Dec 24 = 13:59:20 EET 2011 @:/usr/obj/usr/src/sys/KES_KERN_v10 i386 > > >=20 > > > rebooting once per day. Now I compile kernel with debug options. > > > Can you advice me which and where I find debug info when it will > > > reboting next time? so I can help to debug problem > >=20 > > Are you using the patch at the URL above (tcp_negwin_test.patch)? If n= ot, > > can you try applying that patch and seeing if you still get any panics? >=20 > I applied 1.5 days ago, so far now panics and no other messages. > I modified the patch a bit to not panic, but print a message when panic > was suppose to happen. This box is too valuable for me to panic it too > often. Because there were no debug messages I understand that the > scenerio didn't happen yet and not that the problem is fixed, right? Yes. It would be best to see the messages logged to be safe. Thanks. =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 21:30:52 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61E481065696; Thu, 29 Dec 2011 21:30:52 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0F2198FC16; Thu, 29 Dec 2011 21:30:51 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so14813180obb.13 for ; Thu, 29 Dec 2011 13:30:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=UDONJu0Mi77CU12P4GfnbWTkAAYSoHcka8uLLW65hjc=; b=Z6cIVbYqHyvFxJAKhqUZXjzv2f5MuwV+zcte/r9EIAr2XNzUhroPgsA8JOxS2V7DuW +nfG0/EYITMl8ocMIatdgCWib0rOhBIukGcQ5guEgOhYhcJ9x48ive1xLOJup0jAWIOI 1E0RQjxjyM7asvwNnGK1fmYLPAWeKJ17ppwQI= Received: by 10.50.100.164 with SMTP id ez4mr23478839igb.12.1325194251322; Thu, 29 Dec 2011 13:30:51 -0800 (PST) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.207.7 with HTTP; Thu, 29 Dec 2011 13:30:20 -0800 (PST) In-Reply-To: <1325193958.31545.YahooMailClassic@web113520.mail.gq1.yahoo.com> References: <1325193958.31545.YahooMailClassic@web113520.mail.gq1.yahoo.com> From: Chris Rees Date: Thu, 29 Dec 2011 21:30:20 +0000 X-Google-Sender-Auth: Pwl2JLYCjeKOsYRGclXbjCglJP0 Message-ID: To: pfg@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org, Nathan Whitehorn Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 21:30:52 -0000 On 29 December 2011 21:25, Pedro Giffuni wrote: > --- Gio 29/12/11, Chris Rees ha scritto: > >> > FWIW; >> > >> > I have practically given up on installing FreeBSD >> lately >> > and I mostly use PC-BSD. I mainly see two big issues: >> > >> > -X.Org has become very difficult to install. Setting >> up >> > hald and friends, not to mention that you have to >> > choose carefully your hardware previously. It's a >> > nightmare. >> >> I've not found that... installing xorg-drivers with the >> correct options is hassle-free... have you posted these >> problems to -x11@? >> > > Hmm.. I think it was 8.2 and "X.org -configure" didn't > give me a working screen, and then I discovered I had to > be using hald, it was painful and I starting keeping a > copy of my working configuration in a USB mem. TBH the > -x11 guys were really doing their own homework keeping up > with linux and I was able to find out the information on > the net. > > I use the nvidia driver, no idea what people with ATI > cards do. I'm sorry to hear you're having trouble with that, if you ever want to try again and you can't work it out get me off list ;) >> > - I am OK with sysinstall disappearing: however it >> was >> > nice to have all the setup tools in one place. How am >> > I supposed to install prebuilt packages (and the >> myriad >> > of dependencies) from now on? Ports are cool but >> having >> > to wait to rebuild gcc to be able to use scilab is a >> > nonsense. >> >> Use packages, we do do them! >> > > Of course, but no idea how to use them without > sysinstall's post-install configuration screen: it > was just too easy. > > I hope I don't have to start downloading manually all > the prepackaged dependencies (I still do that with > Java and it's not nice). Nah, pkg_add -r works and grabs anything you need. Try it with something monstrous (like gcc...) Chris From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 21:36:35 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BBB41065670; Thu, 29 Dec 2011 21:36:35 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id C4C0E8FC0A; Thu, 29 Dec 2011 21:36:34 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id CA62AE6226; Thu, 29 Dec 2011 21:36:33 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=RZ6375KwremZ 4NWTY+KzGjXnQbs=; b=FMkZbuljvR5WC0wf9uze3b2M1mkDBL/fifFWAQH6IGd6 EXV1dtNhIbBRv9t3Uez6yGSY8FEGOUtptsZxM/bHDjNKyTa2HAAQ/KSqT/CK4U1o 1OvbIkJiqISd4DbcjyzbpMLo+dutMzZpVGjviHMdxGpjcY1k/yEyZm/mi2rZrjQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=S+hkg4 SJS6L+c8PYQJsXQNy1BtK7koBjBZyS3zC4OmOEmu2+raohaYWuy3TgfEjQTnll5F +YeVpUAG23SA86mrWTGw+Lj3DrHJc9LVMgr8fB6oS9gzy8UqrCOqoyQmIgjeoUBI 4stE2mTvyu6ZagAScI2ewRoSA/YQlmm9IU3lo= Received: from [192.168.1.69] (188-220-36-32.zone11.bethere.co.uk [188.220.36.32]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 90595E6225; Thu, 29 Dec 2011 21:36:33 +0000 (GMT) Message-ID: <4EFCDD5F.6000704@cran.org.uk> Date: Thu, 29 Dec 2011 21:36:31 +0000 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Chris Rees References: <1325193958.31545.YahooMailClassic@web113520.mail.gq1.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: pfg@freebsd.org, Nathan Whitehorn , freebsd-current@freebsd.org Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 21:36:35 -0000 On 29/12/2011 21:30, Chris Rees wrote: > Nah, pkg_add -r works and grabs anything you need. Try it with > something monstrous (like gcc...) But then you have to know the exact name of the package, which isn't always obvious. -- Bruce Cran From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 21:38:21 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B638106564A for ; Thu, 29 Dec 2011 21:38:21 +0000 (UTC) (envelope-from pfg@freebsd.org) Received: from nm27-vm0.bullet.mail.sp2.yahoo.com (nm27-vm0.bullet.mail.sp2.yahoo.com [98.139.91.232]) by mx1.freebsd.org (Postfix) with SMTP id 713B68FC0C for ; Thu, 29 Dec 2011 21:38:21 +0000 (UTC) Received: from [98.139.91.67] by nm27.bullet.mail.sp2.yahoo.com with NNFMP; 29 Dec 2011 21:25:59 -0000 Received: from [98.139.91.19] by tm7.bullet.mail.sp2.yahoo.com with NNFMP; 29 Dec 2011 21:25:59 -0000 Received: from [127.0.0.1] by omp1019.mail.sp2.yahoo.com with NNFMP; 29 Dec 2011 21:25:59 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 413486.44281.bm@omp1019.mail.sp2.yahoo.com Received: (qmail 42285 invoked by uid 60001); 29 Dec 2011 21:25:59 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1325193959; bh=+UFRMj8lBQtpNJzCK+ASzRGwTp7ghLO2M7eor/kN0O4=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Q/j6/d4WZ4fu5nacjUSPKMaLH3yjTDkrFKglUXL0HjnS66h9raZkp2aJzd6HQxpTEc4CIagAlXaPCNNiBVNBFG9E7nBjXQee/HIr/OGgwOTE8iP8eYGLKazaf0dqQZGAyveOarjoUOmuYIogqw3DSizYsnd8eN02f7LDQB9XXUc= X-YMail-OSG: pcZjkSkVM1lxHeiAKIZtVDVJWCJ9WdHEDJxxlYp5LS47rEA 91UI4WD2d3dfV5rKimb9A3N56U1Z4KjZT2TcjEWTwvw_AFst4Bj9dF_siWpm J9cD8IrqrpqQXGEyKvc.AhqXc2x35A2LcLPcYhQX52UPV0_J3X3a6ml8.F.I E6RuEx0AlQGcguSF97AUy0XtAnU_aV7O_4emzcEtPTE3toOI4Odx5W9TUujb 3Fjo37ulyO.1o7RHogvwNORcOrf2pflEXRf8uNnnX4LaKdLe28YRE5T5FWel K2vvJ2Y9egn0QvFDXh7Z2l_.L.g7WXD1ueFMEt_I3S5NIJubDDvRntvGgPtK L3jsqayK2o_YIJPX29V4_GacW4iWYMhw4VWrv8HZDlmY2vGlBvr1ghIXk.I6 mS9fd.35iOh57X1fLAtc0cjJWeqVLEs9Y8tC4.Pf5LBLpqqA_lp2HWO2Z2Pt qDP9SsF02SEnAADJBYmfipWJ6u2ga1o4HwD14CKD_40CdxNLYEQx6DIg3tfO VL7vzlYUcu7EU01pr3uPS5Hzg9D1NZNJKy.n6ReFZoDAjldo9Dy7owXGPxfY IXUtzuuU- Received: from [200.118.157.7] by web113520.mail.gq1.yahoo.com via HTTP; Thu, 29 Dec 2011 13:25:58 PST X-RocketYMMF: giffunip X-Mailer: YahooMailClassic/15.0.4 YahooMailWebService/0.8.115.331698 Message-ID: <1325193958.31545.YahooMailClassic@web113520.mail.gq1.yahoo.com> Date: Thu, 29 Dec 2011 13:25:58 -0800 (PST) From: Pedro Giffuni To: Chris Rees In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Nathan Whitehorn Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfg@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 21:38:21 -0000 =0A=0A--- Gio 29/12/11, Chris Rees ha scritto:=0A=0A> >= FWIW;=0A> >=0A> > I have practically given up on installing FreeBSD=0A> la= tely=0A> > and I mostly use PC-BSD. I mainly see two big issues:=0A> >=0A> = > -X.Org has become very difficult to install. Setting=0A> up=0A> > hald an= d friends, not to mention that you have to=0A> > choose carefully your hard= ware previously. It's a=0A> > nightmare.=0A> =0A> I've not found that... in= stalling xorg-drivers with the=0A> correct options is hassle-free... have y= ou posted these=0A> problems to -x11@?=0A>=0A=0AHmm.. I think it was 8.2 an= d "X.org -configure" didn't=0Agive me a working screen, and then I discover= ed I had to=0Abe using hald, it was painful and I starting keeping a=0Acopy= of my working configuration in a USB mem. TBH the=0A-x11 guys were really = doing their own homework keeping up=0Awith linux and I was able to find out= the information on=0Athe net.=0A=0AI use the nvidia driver, no idea what p= eople with ATI=0Acards do.=0A=0A=0A> > - I am OK with sysinstall disappeari= ng: however it=0A> was=0A> > nice to have all the setup tools in one place.= How am=0A> > I supposed to install prebuilt packages (and the=0A> myriad= =0A> > of dependencies) from now on? Ports are cool but=0A> having=0A> > to= wait to rebuild gcc to be able to use scilab is a=0A> > nonsense.=0A> =0A>= Use packages, we do do them!=0A>=0A=0AOf course, but no idea how to use th= em without=0Asysinstall's post-install configuration screen: it=0Awas just = too easy.=0A=0AI hope I don't have to start downloading manually all=0Athe = prepackaged dependencies (I still do that with=0AJava and it's not nice).= =0A=0APedro. From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 21:47:45 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67FD0106564A; Thu, 29 Dec 2011 21:47:45 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 108868FC0A; Thu, 29 Dec 2011 21:47:44 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so14832739obb.13 for ; Thu, 29 Dec 2011 13:47:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=SRHy53/vv9WIrdV9EJI5be/96avmi9JFXA1ie+R3VcY=; b=jrB41uCdnrCCM5WSs/vDiO+FPMkJSAiagkmDSUgPK8G5AZvvO/fwlGMsiV3yjG1on8 kq8gUqYBo+RQRadAb8n5JzMB/LbDKNsAQfTdmo2+fs01duSCtTA48Vr/7F24eL5phEg1 iunY/Af9zO1O03ZaEk1AOjQ1MtNA77lppjiog= MIME-Version: 1.0 Received: by 10.50.153.135 with SMTP id vg7mr43541954igb.12.1325195264154; Thu, 29 Dec 2011 13:47:44 -0800 (PST) Sender: utisoft@gmail.com Received: by 10.231.207.7 with HTTP; Thu, 29 Dec 2011 13:47:43 -0800 (PST) Received: by 10.231.207.7 with HTTP; Thu, 29 Dec 2011 13:47:43 -0800 (PST) In-Reply-To: <4EFCDD5F.6000704@cran.org.uk> References: <1325193958.31545.YahooMailClassic@web113520.mail.gq1.yahoo.com> <4EFCDD5F.6000704@cran.org.uk> Date: Thu, 29 Dec 2011 21:47:43 +0000 X-Google-Sender-Auth: pCmFOffAow-K0ZMCZsBV64YMMLQ Message-ID: From: Chris Rees To: Bruce Cran Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: pfg@freebsd.org, Nathan Whitehorn , freebsd-current@freebsd.org Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 21:47:45 -0000 On 29 Dec 2011 21:36, "Bruce Cran" wrote: > > On 29/12/2011 21:30, Chris Rees wrote: >> >> Nah, pkg_add -r works and grabs anything you need. Try it with something monstrous (like gcc...) > > > But then you have to know the exact name of the package, which isn't always obvious. If an educated guess doesn't work... make -C /usr/ports/category/name -V PKGNAME will get you the package name. Chris From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 21:50:59 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE513106564A for ; Thu, 29 Dec 2011 21:50:59 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id A8AC98FC18 for ; Thu, 29 Dec 2011 21:50:59 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id C75C156172; Thu, 29 Dec 2011 15:50:58 -0600 (CST) Date: Thu, 29 Dec 2011 15:50:58 -0600 From: Mark Linimon To: Pedro Giffuni Message-ID: <20111229215058.GA27847@lonesome.com> References: <4EFC9745.3050901@freebsd.org> <1325183038.93200.YahooMailClassic@web113516.mail.gq1.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1325183038.93200.YahooMailClassic@web113516.mail.gq1.yahoo.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current@freebsd.org, Nathan Whitehorn Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 21:50:59 -0000 On Thu, Dec 29, 2011 at 10:23:58AM -0800, Pedro Giffuni wrote: > How am I supposed to install prebuilt packages (and the myriad of > dependencies) from now on? I strongly recommend using portmaster. The manpage is very dense but to start with, use something like the following (I'm just picking one port at random, pkg_cutleaves, to install): portmaster -PP ports-mgmt/pkg_cutleaves mcl From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 21:59:28 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2ECA6106564A for ; Thu, 29 Dec 2011 21:59:28 +0000 (UTC) (envelope-from pfg@freebsd.org) Received: from nm13-vm1.bullet.mail.ne1.yahoo.com (nm13-vm1.bullet.mail.ne1.yahoo.com [98.138.91.62]) by mx1.freebsd.org (Postfix) with SMTP id DE5A58FC1F for ; Thu, 29 Dec 2011 21:59:27 +0000 (UTC) Received: from [98.138.90.55] by nm13.bullet.mail.ne1.yahoo.com with NNFMP; 29 Dec 2011 21:59:27 -0000 Received: from [98.138.89.234] by tm8.bullet.mail.ne1.yahoo.com with NNFMP; 29 Dec 2011 21:59:27 -0000 Received: from [127.0.0.1] by omp1049.mail.ne1.yahoo.com with NNFMP; 29 Dec 2011 21:59:27 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 158501.64008.bm@omp1049.mail.ne1.yahoo.com Received: (qmail 71281 invoked by uid 60001); 29 Dec 2011 21:59:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1325195966; bh=/fGdOmjolste9XNhXBzPj87l6M9wQNLlAyfcn+Zvvtk=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ABQvaOQLQvRcSraP5yQMCNupLt40VPOpobmFZquOOynCpmE+R1kTccfvSPV+9pNEjJNSZpznNVg73uw+jv6KQD1zTNumNirIZZ62cAVdE3Pc6OP+JRD60suX6NlBnj3+oq7I9hfKOhfZ+CYqKGezTWKPQAL2+A6Rg3kQAK3VbBQ= X-YMail-OSG: x.fbpR0VM1k.5lOWb8.hyFIaYLYm2Br6rXPXRcPHuaOvUfz 50fSUJaP8oPEGiDz0A6HvpLraMpvvW02BsCvfAWFCqDGYkeQ_Lbv_PXWLNj2 7y5KIsKA3xh2LNFNhQjwUFH85M9Nkw17HbwbGlQdKfzYwRloV14uwYi9A5UO unRGo7BCP92jbB6TSjwhjAezQMSMHlXnFQcZJUF_nDkaEc_bnqGzUeyG_d7q Cq4Y8QhQYIX8Yp.mcEiegC8HIvEUXC5M.NS3ZkVeAARZYiGNhuTj.Gg2xAMr JWrJDvp2U3Vj9Elbhh3x21r11VSAyfSrBJF5GmJgXWTwlCNBBT1V_B_znXsZ xWA8qLuw..Mx.ZPrzmWfYZi4b.j3aoUiFBDZOd._puqVEh3xLCixo5JfzXEH OiOOQBVq7AyigSnhQmWcOt6MsSvH9gbaNUAMqDVr3jBLtyEnJpArsxy4y0KH qXH8GD3xSR1CXrASyUXJ_cO4ZxA-- Received: from [200.118.157.7] by web113510.mail.gq1.yahoo.com via HTTP; Thu, 29 Dec 2011 13:59:26 PST X-RocketYMMF: giffunip X-Mailer: YahooMailClassic/15.0.4 YahooMailWebService/0.8.115.331698 Message-ID: <1325195966.54158.YahooMailClassic@web113510.mail.gq1.yahoo.com> Date: Thu, 29 Dec 2011 13:59:26 -0800 (PST) From: Pedro Giffuni To: Chris Rees In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Nathan Whitehorn Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfg@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 21:59:28 -0000 Hello;=0A=0A--- Gio 29/12/11, Chris Rees ha scritto:=0A= =0A> >=0A> > I use the nvidia driver, no idea what people with ATI=0A> > ca= rds do.=0A> =0A> I'm sorry to hear you're having trouble with that, if you= =0A> ever want to try again and you can't work it out get me=0A> off list ;= )=0A>=0A=0AGetting X11 to run on virtualbox from a FreeBSD 9.0 CD=0Ainstall= ation is pretty much a nightmare. Is there something=0Aabout it in the user= s handbook? A wiki page about setting up=0AX11 on FreeBSD would do it too. = Perhaps we should write one.=0A=0A...=0A> > I hope I don't have to start do= wnloading manually all=0A> > the prepackaged dependencies (I still do that = with=0A> > Java and it's not nice).=0A> =0A> Nah, pkg_add -r works and grab= s anything you need. Try it=0A> with something monstrous (like gcc...)=0A> = =0A=0AAha! I guess I just keep doing things the old way then,=0Athe package= browser was still very nice but I guess what=0Ais really missing is docume= ntation. How is someone new=0Ato FreeBSD supposed to know what packages are= available=0Aand how to install them?=0A=0Acheers,=0A=0APedro.=0A=0A=0A> Ch= ris=0A> _______________________________________________=0A> freebsd-current= @freebsd.org=0A> mailing list=0A> http://lists.freebsd.org/mailman/listinfo= /freebsd-current=0A> To unsubscribe, send any mail to "freebsd-current-unsu= bscribe@freebsd.org"=0A> =0A> From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 22:30:10 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C9941065676; Thu, 29 Dec 2011 22:30:10 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id 1C2DA8FC0A; Thu, 29 Dec 2011 22:30:09 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LWZ00604L66DH00@smtpauth2.wiscmail.wisc.edu>; Thu, 29 Dec 2011 16:30:06 -0600 (CST) Received: from wanderer.tachypleus.net ([unknown] [76.210.77.223]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LWZ000BKL62QK10@smtpauth2.wiscmail.wisc.edu>; Thu, 29 Dec 2011 16:30:03 -0600 (CST) Date: Thu, 29 Dec 2011 14:30:02 -0800 From: Nathan Whitehorn In-reply-to: <4EFCD2D8.50505@cran.org.uk> To: Bruce Cran Message-id: <4EFCE9EA.7040900@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.77.223 X-Spam-PmxInfo: Server=avs-13, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.12.29.221516, SenderIP=76.210.77.223 References: <4EF904F2.4020109@FreeBSD.org> <4EFA1C9C.60601@FreeBSD.org> <4EFA7FD4.10600@freebsd.org> <201112290952.06834.jhb@freebsd.org> <4EFC9745.3050901@freebsd.org> <4EFCD2D8.50505@cran.org.uk> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111213 Thunderbird/8.0 Cc: Lawrence Stewart , freebsd-current@freebsd.org, Ron McDowell , Doug Barton Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 22:30:10 -0000 On 12/29/11 12:51, Bruce Cran wrote: > On 29/12/2011 16:37, Nathan Whitehorn wrote: >> I'd appreciate any specific comments you might have, and especially >> specific suggestions for improvements. Except from people who are old >> hands at sysinstall, I've received almost universally positive >> comments on the user experience. Patches would be even more >> appreciated, since real life has intervened to steal most of my >> FreeBSD time. > > There was talk in the past that any future installer should be based > around the pc-sysinstall backend - has there been any progress towards > moving bsdinstall to it? > There has not been much. My free time evaporated, and I haven't had the ability to work on this. I heard from some people at iX a while back, but I don't know what their progress is. There are a relatively small number of relatively major things that would need to be rewritten on both sides (e.g. the pc-sysinstall partition editor is x86-only and the bsdinstall one is premised around letting the kernel do pre-commit staging). There's a relatively bare wiki page at http://wiki.freebsd.org/PCBSDInstallMerge for those interested. -Nathan From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 22:36:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DD71106566B for ; Thu, 29 Dec 2011 22:36:29 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5AB058FC0A for ; Thu, 29 Dec 2011 22:36:29 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so14881341obb.13 for ; Thu, 29 Dec 2011 14:36:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=+E36TqRQXIoUPil0GJjplIukh5uPblRWZnoSbSRBceQ=; b=TkTSvxJvjDP5bVYKZuBSK0ljVSX77DRpM98M4XkzRAMTvN9bGd328SCUjL5OQWRfBx ICKKf43Xkp8GuhR8s7NJi1dk9Lx5Z0WptGbObTc43/ohz9qOxPLgLx2as1UaTnYYvUIl 16b4Gyz5emjWEK45ApT8EAQYA/bkJ4aG+iNe8= MIME-Version: 1.0 Received: by 10.182.2.136 with SMTP id 8mr32616008obu.71.1325198188695; Thu, 29 Dec 2011 14:36:28 -0800 (PST) Received: by 10.182.152.6 with HTTP; Thu, 29 Dec 2011 14:36:28 -0800 (PST) Date: Thu, 29 Dec 2011 14:36:28 -0800 Message-ID: From: Garrett Cooper To: pfg@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Thu, 29 Dec 2011 22:39:13 +0000 Cc: freebsd-x11@freebsd.org Subject: Setting up xorg, the quick and dirty method (was "Removal of sysinstall from HEAD and lack of a post-install configuration tool") X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 22:36:29 -0000 (Splitting off one part of the thread to be relevant to the right group; moving x11 mailing list to BCC) On Thu, Dec 29, 2011 at 1:59 PM, Pedro Giffuni wrote: > Hello; > > --- Gio 29/12/11, Chris Rees ha scritto: > >> > >> > I use the nvidia driver, no idea what people with ATI >> > cards do. >> >> I'm sorry to hear you're having trouble with that, if you >> ever want to try again and you can't work it out get me >> off list ;) >> > > Getting X11 to run on virtualbox from a FreeBSD 9.0 CD > installation is pretty much a nightmare. Is there something > about it in the users handbook? A wiki page about setting up > X11 on FreeBSD would do it too. Perhaps we should write one. There is a chapter in the handbook [1], but what I've learned from the last go-around setting up X11 4 months ago, is that it's smart to do: cd x11/xorg make config-recursive make install # An hour or so passes by on a fast machine echo 'dbus_enable="YES"' >> /etc/rc.conf echo 'hald_enable="YES"' >> /etc/rc.conf service dbus start service hald start startx That's it. Generally no configuration is required for X.org to work on hardware (in fact I'm not using an xorg.conf right now. after I blasted away my packages due to the CURRENT 9 -> 10 major version bump..). You'll need to pimp your install to do non-standard stuff via nvidia-settings, not use hald, etc, but the X.org supplied method seems to work the majority of the time if you have standard hardware, compared to the hoops one needed to go through when setting up XFree86 or earlier versions of X.org. Cheers, -Garrett 1. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 23:02:15 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DDD01065670 for ; Thu, 29 Dec 2011 23:02:15 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: from redundancy.redundancy.org (75-101-96-57.dsl.static.sonic.net [75.101.96.57]) by mx1.freebsd.org (Postfix) with SMTP id 2CA598FC12 for ; Thu, 29 Dec 2011 23:02:14 +0000 (UTC) Received: (qmail 3182 invoked by uid 1001); 29 Dec 2011 23:02:38 -0000 Date: Thu, 29 Dec 2011 15:02:38 -0800 From: David Thiel To: freebsd-current@freebsd.org Message-ID: <20111229230214.GT45484@redundancy.redundancy.org> References: <20111227215330.GI45484@redundancy.redundancy.org> <20111227223638.GK45484@redundancy.redundancy.org> <4EFA4B4E.201@delphij.net> <20111228051404.GL45484@redundancy.redundancy.org> <6F3ACDEE-B656-46D0-AB11-FF1B23E70A27@samsco.org> <20111228073442.GM45484@redundancy.redundancy.org> <9DAD04BE-D330-4DC8-9307-597834EEA2CA@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9DAD04BE-D330-4DC8-9307-597834EEA2CA@samsco.org> X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13 X-OpenPGP-Key-available: http://redundancy.redundancy.org/lx.gpg X-Face: %H~{$1~NOw1y#%mM6{|4:/ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 23:02:15 -0000 On Wed, Dec 28, 2011 at 12:57:31AM -0700, Scott Long wrote: > So, there's an assumption with SUJ+fsck that SU is keeping the filesystem consistent. Maybe that's a bad assumption, and I'm not trying to discredit your report. But the intention with SUJ is to eliminate the need for anything more than a cursory check of the superblocks and a processing of the SUJ intent log. If either of these fails then fsck reverts to a traditional scan. In the same vein, ext3 and most other traditional journaling filesystems assume that the journal is correct and is preserving consistency, and don't do anything more than a cursory data structure scan and journal replay as well, but then revert to a full scan if that fails (zfs seems to be an exception here, with there being no actual fsck available for it). > > As for the 180 day forced scan on ext3, I have no public comment. SU has matured nicely over the last 10+ years, and I'm happy with the progress that SUJ has made in the last 2-3 years. If there are bugs, they need to be exposed and addressed ASAP. That clears things up somewhat - thank you for taking the time to explain all that. I've got results from two other users (Cc'd) with a fsck in single user mode using the journal and not using it. One has geli, one does not, and both were with clean shutdown/boot (correct me if I'm wrong, guys). Any thoughts? ================= Machine 1, with journal: ================= Script started on Thu Dec 29 11:26:29 2011 fsck / ** /dev/ada0.eli USE JOURNAL? [yn] y ** SU+J Recovering /dev/ada0.eli ** Reading 33554432 byte journal from inode 4. RECOVER? [yn] y ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. WRITE CHANGES? [yn] y ** 108 journal records in 49152 bytes for 7.03% utilization ** Freed 9 inodes (0 dirs) 0 blocks, and 1 frags. ***** FILE SYSTEM MARKED CLEAN ***** Script done on Thu Dec 29 11:26:39 2011 ================= Machine 1, without journal: ================= Script started on Thu Dec 29 11:26:49 2011 fsck / ** /dev/ada0.eli USE JOURNAL? [yn] n ** Skipping journal, falling through to full fsck ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=251177 (8 should be 0) CORRECT? [yn] y ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 220435 files, 3945055 used, 3666151 free (17503 frags, 456081 blocks, 0.2% fragmentation) ***** FILE SYSTEM IS CLEAN ***** ***** FILE SYSTEM WAS MODIFIED ***** Script done on Thu Dec 29 11:27:08 2011 ================= Machine 2, with journal: ================= ** /dev/ada0s1a USE JOURNAL? yes ** SU+J Recovering /dev/ada0s1a ** Reading 33554432 byte journal from inode 4. RECOVER? yes ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. WRITE CHANGES? yes ** 131 journal records in 11776 bytes for 35.60% utilization ** Freed 0 inodes (0 dirs) 0 blocks, and 0 frags. ***** FILE SYSTEM MARKED CLEAN ***** ================= Machine 2, without journal: ================= ** /dev/ada0s1a ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? [yn] SUMMARY INFORMATION BAD SALVAGE? [yn] BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] 670213 files, 19118534 used, 54535063 free (158431 frags, 6797079 blocks, 0.2% fragmentation) ***** FILE SYSTEM MARKED CLEAN ***** ***** FILE SYSTEM WAS MODIFIED ***** From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 23:18:18 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 437251065672 for ; Thu, 29 Dec 2011 23:18:18 +0000 (UTC) (envelope-from jsa.bsd@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id EF5C58FC14 for ; Thu, 29 Dec 2011 23:18:17 +0000 (UTC) Received: by qabg14 with SMTP id g14so10747336qab.13 for ; Thu, 29 Dec 2011 15:18:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Ey3z/PPW62GppMRg34/hJzQLYcXfbO6avi9PE05AQXg=; b=vH5CUbgUByP4Dk/Ym9X64vNBWINOUbEDnlgPklSL41A5f3hzS7ni6FCkfiBQbOTq/o bsCSkzsWLGs0eMYlY+Iqyd74LzX+GdUqSeEG+2cxUEArUMgIibtNqeJWmlJF2r8TLt1Z tkLz/Z3CYMISJh/QHJELOvxVDTROIkcn/brcA= Received: by 10.224.44.130 with SMTP id a2mr44774472qaf.59.1325200696919; Thu, 29 Dec 2011 15:18:16 -0800 (PST) Received: from pazuzu.wickedmachine.net ([76.5.150.155]) by mx.google.com with ESMTPS id ev2sm20224629qab.15.2011.12.29.15.18.15 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 29 Dec 2011 15:18:15 -0800 (PST) Sender: "Joseph S. Atkinson" Message-ID: <4EFCF536.2030104@FreeBSD.org> Date: Thu, 29 Dec 2011 18:18:14 -0500 From: "Joseph S. Atkinson" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111224 Thunderbird/9.0 MIME-Version: 1.0 To: Garrett Cooper , freebsd-current@freebsd.org References: <4EFC0127.6030301@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 23:18:18 -0000 On 12/29/2011 01:41, Garrett Cooper wrote: > On Wed, Dec 28, 2011 at 9:56 PM, Joseph S. Atkinson wrote: >> I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the >> issue of cdda:// access. >> >> I can confirm this issues, but don't know enough about driver access to fix >> this myself. Doug Barton reports that cdcontrol(1) doesn't work for him, and >> mplayer and audactiy also display issues running as non-root. >> >> Under 9.0-RC3 r228843, I get these errors on boot with no disc present in >> /dev/cd0 at all. >> >> (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 >> 00 >> (pass1:ahcich2:0:0:0): CAM status: ATA Status Error >> (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) >> (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 >> >> These ports are fairly popular, but the problems may not lie exclusively >> with their assumptions about FreeBSD. I am running 10.0 on another machine >> specifically to test changes under src/sys/cam. >> >> I am worried that with the actual 9.0-RELEASE on the horizon, users will >> find show stopping problems using their disc drives. > > Try having users merge r228808 and r228847. If that works, then I > would press re@ produce another RC that fixes this. > Thanks, > -Garrett > My desktop is 10.0-CURRENT r228926. I am running 9.0-RC3 on my laptop. I mention RC3 because the problem there is about to become a RELEASE problem. Neither machine can read CDs. I also cannot eject CDs on the laptop after the failed attempts to read it because it doesn't seem to stop trying to read it. > PS This is coming from a user that was annoyed by this gap with the > ATA_CAM code. If pre-RELEASE is any indication, this is going to flood GNATS. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Dec 29 23:23:23 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 8F3D7106566C; Thu, 29 Dec 2011 23:23:23 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 32D4714E625; Thu, 29 Dec 2011 23:23:23 +0000 (UTC) Message-ID: <4EFCF66A.1020308@FreeBSD.org> Date: Thu, 29 Dec 2011 15:23:22 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: "Joseph S. Atkinson" References: <4EFC0127.6030301@FreeBSD.org> In-Reply-To: <4EFC0127.6030301@FreeBSD.org> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2011 23:23:23 -0000 Just to clarify some things that I passed on to Joseph in haste ... On 12/28/2011 21:56, Joseph S. Atkinson wrote: > Doug Barton reports that cdcontrol(1) doesn't work for him, Some of the functions work, but I can't play audio CDs with it, even as root. > and mplayer > and audactiy also display issues running as non-root. These 2 will play audio CDs when run as root due to a labyrinth of permissions issues in /dev, in spite of my having my unprivileged user in the 'operator' group. vlc doesn't work at all, even as root. I'm happy to provide more details, testing, etc. Doug -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 01:41:25 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00FF11065675 for ; Fri, 30 Dec 2011 01:41:25 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: from redundancy.redundancy.org (75-101-96-57.dsl.static.sonic.net [75.101.96.57]) by mx1.freebsd.org (Postfix) with SMTP id B7C8D8FC16 for ; Fri, 30 Dec 2011 01:41:24 +0000 (UTC) Received: (qmail 6416 invoked by uid 1001); 30 Dec 2011 01:41:48 -0000 Date: Thu, 29 Dec 2011 17:41:48 -0800 From: David Thiel To: freebsd-current@freebsd.org Message-ID: <20111230014123.GU45484@redundancy.redundancy.org> References: <20111227215330.GI45484@redundancy.redundancy.org> <20111227223638.GK45484@redundancy.redundancy.org> <4EFA4B4E.201@delphij.net> <20111228051404.GL45484@redundancy.redundancy.org> <6F3ACDEE-B656-46D0-AB11-FF1B23E70A27@samsco.org> <20111228073442.GM45484@redundancy.redundancy.org> <9DAD04BE-D330-4DC8-9307-597834EEA2CA@samsco.org> <20111229230214.GT45484@redundancy.redundancy.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111229230214.GT45484@redundancy.redundancy.org> X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13 X-OpenPGP-Key-available: http://redundancy.redundancy.org/lx.gpg X-Face: %H~{$1~NOw1y#%mM6{|4:/ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 01:41:25 -0000 On Thu, Dec 29, 2011 at 03:02:14PM -0800, David Thiel wrote: > ================= > Machine 1, with journal: > ================= > > Script started on Thu Dec 29 11:26:29 2011 > fsck / > ** /dev/ada0.eli Correction - machine 1 had an unclean shutdown. Will get additional logs soon. From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 07:06:01 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 123841065670 for ; Fri, 30 Dec 2011 07:06:01 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id D6D0F8FC12 for ; Fri, 30 Dec 2011 07:06:00 +0000 (UTC) Received: from [127.0.0.1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.5/8.14.5) with ESMTP id pBU75vDi057262; Fri, 30 Dec 2011 00:05:57 -0700 (MST) (envelope-from scottl@samsco.org) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: Scott Long In-Reply-To: <20111229230214.GT45484@redundancy.redundancy.org> Date: Fri, 30 Dec 2011 00:05:57 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <07D71DC4-0C3F-4995-A75A-AEBAF3EEA318@samsco.org> References: <20111227215330.GI45484@redundancy.redundancy.org> <20111227223638.GK45484@redundancy.redundancy.org> <4EFA4B4E.201@delphij.net> <20111228051404.GL45484@redundancy.redundancy.org> <6F3ACDEE-B656-46D0-AB11-FF1B23E70A27@samsco.org> <20111228073442.GM45484@redundancy.redundancy.org> <9DAD04BE-D330-4DC8-9307-597834EEA2CA@samsco.org> <20111229230214.GT45484@redundancy.redundancy.org> To: David Thiel X-Mailer: Apple Mail (2.1251.1) X-Spam-Status: No, score=-50.0 required=3.8 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org Cc: jsa@FreeBSD.org, boris@nyi.net, freebsd-current@FreeBSD.org Subject: Re: SU+J systems do not fsck themselves X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 07:06:01 -0000 On Dec 29, 2011, at 4:02 PM, David Thiel wrote: > On Wed, Dec 28, 2011 at 12:57:31AM -0700, Scott Long wrote: >> So, there's an assumption with SUJ+fsck that SU is keeping the = filesystem consistent. Maybe that's a bad assumption, and I'm not = trying to discredit your report. But the intention with SUJ is to = eliminate the need for anything more than a cursory check of the = superblocks and a processing of the SUJ intent log. If either of these = fails then fsck reverts to a traditional scan. In the same vein, ext3 = and most other traditional journaling filesystems assume that the = journal is correct and is preserving consistency, and don't do anything = more than a cursory data structure scan and journal replay as well, but = then revert to a full scan if that fails (zfs seems to be an exception = here, with there being no actual fsck available for it). >>=20 >> As for the 180 day forced scan on ext3, I have no public comment. SU = has matured nicely over the last 10+ years, and I'm happy with the = progress that SUJ has made in the last 2-3 years. If there are bugs, = they need to be exposed and addressed ASAP. >=20 > That clears things up somewhat - thank you for taking the time to=20 > explain all that. I've got results from two other users (Cc'd) with a=20= > fsck in single user mode using the journal and not using it. One has=20= > geli, one does not, and both were with clean shutdown/boot (correct me=20= > if I'm wrong, guys). Any thoughts? Below is the transcript of my simple experiment with an intentional = unclean shutdown with an unlinked file held open. The machine was idle = with nothing of any significance installed (it is a driver development = box). I created a file and opened in it vi, meanwhile I deleted it from = another vty and then did a power cycle. Everything looks as correct and = normal as I would expect. The /usr and /var filesystems also checked = out normal. My system sources are from mid-November, maybe earlier. # fsck / ** /dev/ada0p2 USE JOURNAL? [yn] y ** SU+J Recovering /dev/ada0p2 ** Reading 8388608 byte journal from inode 4. RECOVER? [yn] y ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. WRITE CHANGES? [yn] y ** 5 journal records in 2048 bytes for 7.81% utilization ** Freed 1 inodes (0 dirs) 0 blocks, and 0 frags. ***** FILE SYSTEM MARKED CLEAN ***** # fsck / ** /dev/ada0p2 USE JOURNAL? [yn] n ** Skipping journal, falling through to full fsck ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 676 files, 41820 used, 216107 free (787 frags, 26915 blocks, 0.3% = fragmentation) ***** FILE SYSTEM IS CLEAN ***** ***** FILE SYSTEM WAS MODIFIED ***** #=20 From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 08:53:54 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB0C8106566C for ; Fri, 30 Dec 2011 08:53:54 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 636838FC08 for ; Fri, 30 Dec 2011 08:53:53 +0000 (UTC) Received: by eaaf13 with SMTP id f13so17691513eaa.13 for ; Fri, 30 Dec 2011 00:53:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; bh=vuPrXrftfJGNEWQD8X/LjydUhpdU9kvAiExun6Ysqkg=; b=Ktwwt6dVoXHIohAwSpHXRIRKdVaSvCPvF0V/II4USkHHa32JLRTFWBaifuOGLHtNU4 M9Lt97D3dgWG562/ouauYQL/llEPKPYJFNMo+3WoQo26337pwQSrVOW68ymcQ8TZGoyw ZAbZbQz90UTbmsdGlPZa5g0E9aqR5aXpiENCs= Received: by 10.213.7.9 with SMTP id b9mr7885511ebb.30.1325235232778; Fri, 30 Dec 2011 00:53:52 -0800 (PST) Received: from ernst.jennejohn.org (p578E2AC3.dip.t-dialin.net. [87.142.42.195]) by mx.google.com with ESMTPS id a60sm145026998eeb.4.2011.12.30.00.53.51 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 30 Dec 2011 00:53:52 -0800 (PST) Date: Fri, 30 Dec 2011 09:53:49 +0100 From: Gary Jennejohn To: Doug Barton Message-ID: <20111230095349.347989ed@ernst.jennejohn.org> In-Reply-To: <4EFCF66A.1020308@FreeBSD.org> References: <4EFC0127.6030301@FreeBSD.org> <4EFCF66A.1020308@FreeBSD.org> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "Joseph S. Atkinson" , freebsd-current@FreeBSD.org Subject: Re: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 08:53:54 -0000 On Thu, 29 Dec 2011 15:23:22 -0800 Doug Barton wrote: > Just to clarify some things that I passed on to Joseph in haste ... > > On 12/28/2011 21:56, Joseph S. Atkinson wrote: > > Doug Barton reports that cdcontrol(1) doesn't work for him, > > Some of the functions work, but I can't play audio CDs with it, even as > root. > > > and mplayer > > and audactiy also display issues running as non-root. > > These 2 will play audio CDs when run as root due to a labyrinth of > permissions issues in /dev, in spite of my having my unprivileged user > in the 'operator' group. vlc doesn't work at all, even as root. > > I'm happy to provide more details, testing, etc. > I'm running 10.0-CURRENT r228926 and have no problem watching DVDs with vlc and mplayer as an unpriviledged user in the operator group. I can even rip movies using dvdrip. I have this in /etc/devfs.conf perm cd0 0660 perm xpt0 0660 perm pass0 0660 perm pass1 0660 perm pass2 0660 perm pass3 0660 Haven't tried listening to audio CDs, but I can rip them with no problem. -- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 08:56:55 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id A25B51065670; Fri, 30 Dec 2011 08:56:53 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 717FF150D19; Fri, 30 Dec 2011 08:56:53 +0000 (UTC) Message-ID: <4EFD7CD5.9010703@FreeBSD.org> Date: Fri, 30 Dec 2011 00:56:53 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: gljennjohn@googlemail.com References: <4EFC0127.6030301@FreeBSD.org> <4EFCF66A.1020308@FreeBSD.org> <20111230095349.347989ed@ernst.jennejohn.org> In-Reply-To: <20111230095349.347989ed@ernst.jennejohn.org> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Joseph S. Atkinson" , freebsd-current@FreeBSD.org Subject: Re: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 08:56:55 -0000 On 12/30/2011 00:53, Gary Jennejohn wrote: > I'm running 10.0-CURRENT r228926 and have no problem watching DVDs with > vlc Completely different category of access. DVDs work for me too. -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 09:07:47 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7252F106566B for ; Fri, 30 Dec 2011 09:07:47 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 41BB78FC0A for ; Fri, 30 Dec 2011 09:07:47 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 7C5B856172; Fri, 30 Dec 2011 03:07:46 -0600 (CST) Date: Fri, 30 Dec 2011 03:07:46 -0600 From: Mark Linimon To: "O. Hartmann" Message-ID: <20111230090746.GA3992@lonesome.com> References: <4EF25468.9040204@gmail.com> <4EF2C613.3020609@digsys.bg> <4EF3D68C.2060803@zedat.fu-berlin.de> <20111223074706.1afe4d26@zelda.sugioarto.com> <4EF4474B.3050203@digsys.bg> <20111223114424.GA60815@freebsd.org> <4EF5E9FF.2020300@mail.zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EF5E9FF.2020300@mail.zedat.fu-berlin.de> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Alexander Best , freebsd-current@freebsd.org Subject: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 09:07:47 -0000 On Sat, Dec 24, 2011 at 04:04:31PM +0100, O. Hartmann wrote: > There maybe serious reasons having the Linuxulator, i do not know. But > if not, why spending rare developer resources on that? This is a classical misunderstanding of the FreeBSD development model. There is no "staff" standing around waiting for assignments, as with a commercial company. When committers join the project, they usually (almost always) already have a long list of things that they want to work on. And then they go work on them. Neither the core team, nor the FreeBSD Foundation, "direct" the project and its course of development. Some of the members of each do post emails, or stand up in front of conferences, and say "you know, I think it would be really neat if someone did xyz." Sometimes this leads to results, sometimes not. As for the companies that have their own FreeBSD-derived products, often their goals are tightly focused, e.g. "improve the number of packets we can pass" or "support our specialized hardware". Some, but not all, of the resultant work makes it back into FreeBSD. We get to say "it would be really neat if ..."; and, in addition, point to possible future minimization of merging and duplication of effort as a way to save costs long-term. But with these exceptions, development is primarily driven from the bottom-up (individual committers find something they are interested in working on, and then go work on it), and not the top-down as in "real" companies. This is the way the overwhelming majority (90+%?) of the work on FreeBSD gets done. So, there's no one "assigned" the tasks of closing PRs, nor working on coordinating code with the other BSDs, nor working on the Linuxolator, nor even supporting high-performance computing. It's a cooperative anarchy, not a hierarchy. mcl From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 10:50:18 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98C4F106566B for ; Fri, 30 Dec 2011 10:50:18 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.freebsd.org (Postfix) with ESMTP id 1C1F88FC17 for ; Fri, 30 Dec 2011 10:50:17 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail27.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id pBUAo1lX032284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Dec 2011 21:50:02 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.5/8.14.4) with ESMTP id pBUAnxHj048739; Fri, 30 Dec 2011 21:49:59 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.5/8.14.4/Submit) id pBUAnwvs048738; Fri, 30 Dec 2011 21:49:58 +1100 (EST) (envelope-from peter) Date: Fri, 30 Dec 2011 21:49:57 +1100 From: Peter Jeremy To: "O. Hartmann" Message-ID: <20111230104957.GE55604@server.vk2pj.dyndns.org> References: <4EF25468.9040204@gmail.com> <4EF2C613.3020609@digsys.bg> <4EF3D68C.2060803@zedat.fu-berlin.de> <20111223074706.1afe4d26@zelda.sugioarto.com> <4EF45C85.9010709@mail.zedat.fu-berlin.de> <4EF46829.6010508@digsys.bg> <4EF5E65C.3060405@mail.zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TakKZr9L6Hm6aLOc" Content-Disposition: inline In-Reply-To: <4EF5E65C.3060405@mail.zedat.fu-berlin.de> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-performance@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, Daniel Kalchev Subject: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 10:50:18 -0000 --TakKZr9L6Hm6aLOc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Dec-24 15:49:00 +0100, "O. Hartmann" wrote: >On 12/23/11 12:38, Daniel Kalchev wrote: >> Here is now it works: >>=20 >> If you see an problem and have a solution: go fix it. Many will be >> grateful. >> If you can't fix it, but have an idea how to fix it, share it. May will >> be grateful. >> If you can't fix it and don't have any idea, just say "there is a >> problem" and stop there. There are many, many, many like you who just >> hold their breath. >>=20 >> We all learn, every day. >>=20 >> Daniel > >Sorry, but your crap is simply breathtaking. That was completely uncalled for. You have spent the last month or so whinging about FreeBSD but I have yet to see you provide any constructive input. Instead of whinging about ULE not doing what you want, how about you either fix it yourself or offer to fund someone to fix it for you. --=20 Peter Jeremy --TakKZr9L6Hm6aLOc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk79l1UACgkQ/opHv/APuIf5SACglo/bMd73JAGSaZQp1Kmdl7uv EEsAnRtfpln8yjVKPdNdkahL+KB41qoy =6dle -----END PGP SIGNATURE----- --TakKZr9L6Hm6aLOc-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 11:17:53 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C419106564A; Fri, 30 Dec 2011 11:17:53 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 029DD8FC21; Fri, 30 Dec 2011 11:17:52 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.4) with ESMTP id pBUBHqwo022421; Fri, 30 Dec 2011 06:17:52 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.4/Submit) id pBUBHpoM022390; Fri, 30 Dec 2011 11:17:51 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 30 Dec 2011 11:17:51 GMT Message-Id: <201112301117.pBUBHpoM022390@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on arm/arm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 11:17:53 -0000 TB --- 2011-12-30 09:40:00 - tinderbox 2.8 running on freebsd-current.sentex.ca TB --- 2011-12-30 09:40:00 - starting HEAD tinderbox run for arm/arm TB --- 2011-12-30 09:40:00 - cleaning the object tree TB --- 2011-12-30 09:40:33 - cvsupping the source tree TB --- 2011-12-30 09:40:33 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2011-12-30 09:41:01 - building world TB --- 2011-12-30 09:41:01 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 09:41:01 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 09:41:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 09:41:01 - SRCCONF=/dev/null TB --- 2011-12-30 09:41:01 - TARGET=arm TB --- 2011-12-30 09:41:01 - TARGET_ARCH=arm TB --- 2011-12-30 09:41:01 - TZ=UTC TB --- 2011-12-30 09:41:01 - __MAKE_CONF=/dev/null TB --- 2011-12-30 09:41:01 - cd /src TB --- 2011-12-30 09:41:01 - /usr/bin/make -B buildworld >>> World build started on Fri Dec 30 09:41:02 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 Dec 30 10:36:35 UTC 2011 TB --- 2011-12-30 10:36:35 - cd /src/sys/arm/conf TB --- 2011-12-30 10:36:35 - /usr/sbin/config -m AVILA TB --- 2011-12-30 10:36:35 - building AVILA kernel TB --- 2011-12-30 10:36:35 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 10:36:35 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 10:36:35 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 10:36:35 - SRCCONF=/dev/null TB --- 2011-12-30 10:36:35 - TARGET=arm TB --- 2011-12-30 10:36:35 - TARGET_ARCH=arm TB --- 2011-12-30 10:36:35 - TZ=UTC TB --- 2011-12-30 10:36:35 - __MAKE_CONF=/dev/null TB --- 2011-12-30 10:36:35 - cd /src TB --- 2011-12-30 10:36:35 - /usr/bin/make -B buildkernel KERNCONF=AVILA >>> Kernel build for AVILA started on Fri Dec 30 10:36: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 AVILA completed on Fri Dec 30 10:39:39 UTC 2011 TB --- 2011-12-30 10:39:39 - cd /src/sys/arm/conf TB --- 2011-12-30 10:39:39 - /usr/sbin/config -m BWCT TB --- 2011-12-30 10:39:39 - building BWCT kernel TB --- 2011-12-30 10:39:39 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 10:39:39 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 10:39:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 10:39:39 - SRCCONF=/dev/null TB --- 2011-12-30 10:39:39 - TARGET=arm TB --- 2011-12-30 10:39:39 - TARGET_ARCH=arm TB --- 2011-12-30 10:39:39 - TZ=UTC TB --- 2011-12-30 10:39:39 - __MAKE_CONF=/dev/null TB --- 2011-12-30 10:39:39 - cd /src TB --- 2011-12-30 10:39:39 - /usr/bin/make -B buildkernel KERNCONF=BWCT >>> Kernel build for BWCT started on Fri Dec 30 10:39:40 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 Dec 30 10:41:49 UTC 2011 TB --- 2011-12-30 10:41:49 - cd /src/sys/arm/conf TB --- 2011-12-30 10:41:49 - /usr/sbin/config -m CAMBRIA TB --- 2011-12-30 10:41:49 - building CAMBRIA kernel TB --- 2011-12-30 10:41:49 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 10:41:49 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 10:41:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 10:41:49 - SRCCONF=/dev/null TB --- 2011-12-30 10:41:49 - TARGET=arm TB --- 2011-12-30 10:41:49 - TARGET_ARCH=arm TB --- 2011-12-30 10:41:49 - TZ=UTC TB --- 2011-12-30 10:41:49 - __MAKE_CONF=/dev/null TB --- 2011-12-30 10:41:49 - cd /src TB --- 2011-12-30 10:41:49 - /usr/bin/make -B buildkernel KERNCONF=CAMBRIA >>> Kernel build for CAMBRIA started on Fri Dec 30 10:41:49 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 Fri Dec 30 10:45:17 UTC 2011 TB --- 2011-12-30 10:45:17 - cd /src/sys/arm/conf TB --- 2011-12-30 10:45:17 - /usr/sbin/config -m CNS11XXNAS TB --- 2011-12-30 10:45:18 - building CNS11XXNAS kernel TB --- 2011-12-30 10:45:18 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 10:45:18 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 10:45:18 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 10:45:18 - SRCCONF=/dev/null TB --- 2011-12-30 10:45:18 - TARGET=arm TB --- 2011-12-30 10:45:18 - TARGET_ARCH=arm TB --- 2011-12-30 10:45:18 - TZ=UTC TB --- 2011-12-30 10:45:18 - __MAKE_CONF=/dev/null TB --- 2011-12-30 10:45:18 - cd /src TB --- 2011-12-30 10:45:18 - /usr/bin/make -B buildkernel KERNCONF=CNS11XXNAS >>> Kernel build for CNS11XXNAS started on Fri Dec 30 10:45:18 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 CNS11XXNAS completed on Fri Dec 30 10:47:48 UTC 2011 TB --- 2011-12-30 10:47:48 - cd /src/sys/arm/conf TB --- 2011-12-30 10:47:48 - /usr/sbin/config -m CRB TB --- 2011-12-30 10:47:48 - building CRB kernel TB --- 2011-12-30 10:47:48 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 10:47:48 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 10:47:48 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 10:47:48 - SRCCONF=/dev/null TB --- 2011-12-30 10:47:48 - TARGET=arm TB --- 2011-12-30 10:47:48 - TARGET_ARCH=arm TB --- 2011-12-30 10:47:48 - TZ=UTC TB --- 2011-12-30 10:47:48 - __MAKE_CONF=/dev/null TB --- 2011-12-30 10:47:48 - cd /src TB --- 2011-12-30 10:47:48 - /usr/bin/make -B buildkernel KERNCONF=CRB >>> Kernel build for CRB started on Fri Dec 30 10:47:48 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 CRB completed on Fri Dec 30 10:51:10 UTC 2011 TB --- 2011-12-30 10:51:10 - cd /src/sys/arm/conf TB --- 2011-12-30 10:51:10 - /usr/sbin/config -m DB-78XXX TB --- 2011-12-30 10:51:11 - building DB-78XXX kernel TB --- 2011-12-30 10:51:11 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 10:51:11 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 10:51:11 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 10:51:11 - SRCCONF=/dev/null TB --- 2011-12-30 10:51:11 - TARGET=arm TB --- 2011-12-30 10:51:11 - TARGET_ARCH=arm TB --- 2011-12-30 10:51:11 - TZ=UTC TB --- 2011-12-30 10:51:11 - __MAKE_CONF=/dev/null TB --- 2011-12-30 10:51:11 - cd /src TB --- 2011-12-30 10:51:11 - /usr/bin/make -B buildkernel KERNCONF=DB-78XXX >>> Kernel build for DB-78XXX started on Fri Dec 30 10:51:11 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 DB-78XXX completed on Fri Dec 30 10:54:20 UTC 2011 TB --- 2011-12-30 10:54:20 - cd /src/sys/arm/conf TB --- 2011-12-30 10:54:20 - /usr/sbin/config -m DB-88F5XXX TB --- 2011-12-30 10:54:20 - building DB-88F5XXX kernel TB --- 2011-12-30 10:54:20 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 10:54:20 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 10:54:20 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 10:54:20 - SRCCONF=/dev/null TB --- 2011-12-30 10:54:20 - TARGET=arm TB --- 2011-12-30 10:54:20 - TARGET_ARCH=arm TB --- 2011-12-30 10:54:20 - TZ=UTC TB --- 2011-12-30 10:54:20 - __MAKE_CONF=/dev/null TB --- 2011-12-30 10:54:20 - cd /src TB --- 2011-12-30 10:54:20 - /usr/bin/make -B buildkernel KERNCONF=DB-88F5XXX >>> Kernel build for DB-88F5XXX started on Fri Dec 30 10:54:20 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 DB-88F5XXX completed on Fri Dec 30 10:57:01 UTC 2011 TB --- 2011-12-30 10:57:01 - cd /src/sys/arm/conf TB --- 2011-12-30 10:57:01 - /usr/sbin/config -m DB-88F6XXX TB --- 2011-12-30 10:57:01 - building DB-88F6XXX kernel TB --- 2011-12-30 10:57:01 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 10:57:01 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 10:57:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 10:57:01 - SRCCONF=/dev/null TB --- 2011-12-30 10:57:01 - TARGET=arm TB --- 2011-12-30 10:57:01 - TARGET_ARCH=arm TB --- 2011-12-30 10:57:01 - TZ=UTC TB --- 2011-12-30 10:57:01 - __MAKE_CONF=/dev/null TB --- 2011-12-30 10:57:01 - cd /src TB --- 2011-12-30 10:57:01 - /usr/bin/make -B buildkernel KERNCONF=DB-88F6XXX >>> Kernel build for DB-88F6XXX started on Fri Dec 30 10:57:01 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 DB-88F6XXX completed on Fri Dec 30 10:59:47 UTC 2011 TB --- 2011-12-30 10:59:47 - cd /src/sys/arm/conf TB --- 2011-12-30 10:59:47 - /usr/sbin/config -m DOCKSTAR TB --- 2011-12-30 10:59:47 - building DOCKSTAR kernel TB --- 2011-12-30 10:59:47 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 10:59:47 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 10:59:47 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 10:59:47 - SRCCONF=/dev/null TB --- 2011-12-30 10:59:47 - TARGET=arm TB --- 2011-12-30 10:59:47 - TARGET_ARCH=arm TB --- 2011-12-30 10:59:47 - TZ=UTC TB --- 2011-12-30 10:59:47 - __MAKE_CONF=/dev/null TB --- 2011-12-30 10:59:47 - cd /src TB --- 2011-12-30 10:59:47 - /usr/bin/make -B buildkernel KERNCONF=DOCKSTAR >>> Kernel build for DOCKSTAR started on Fri Dec 30 10:59:47 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 DOCKSTAR completed on Fri Dec 30 11:02:51 UTC 2011 TB --- 2011-12-30 11:02:51 - cd /src/sys/arm/conf TB --- 2011-12-30 11:02:51 - /usr/sbin/config -m EP80219 TB --- 2011-12-30 11:02:52 - building EP80219 kernel TB --- 2011-12-30 11:02:52 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 11:02:52 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 11:02:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 11:02:52 - SRCCONF=/dev/null TB --- 2011-12-30 11:02:52 - TARGET=arm TB --- 2011-12-30 11:02:52 - TARGET_ARCH=arm TB --- 2011-12-30 11:02:52 - TZ=UTC TB --- 2011-12-30 11:02:52 - __MAKE_CONF=/dev/null TB --- 2011-12-30 11:02:52 - cd /src TB --- 2011-12-30 11:02:52 - /usr/bin/make -B buildkernel KERNCONF=EP80219 >>> Kernel build for EP80219 started on Fri Dec 30 11:02:52 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 EP80219 completed on Fri Dec 30 11:05:46 UTC 2011 TB --- 2011-12-30 11:05:46 - WARNING: no kernel config for GENERIC TB --- 2011-12-30 11:05:46 - cd /src/sys/arm/conf TB --- 2011-12-30 11:05:46 - /usr/sbin/config -m GUMSTIX TB --- 2011-12-30 11:05:46 - building GUMSTIX kernel TB --- 2011-12-30 11:05:46 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 11:05:46 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 11:05:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 11:05:46 - SRCCONF=/dev/null TB --- 2011-12-30 11:05:46 - TARGET=arm TB --- 2011-12-30 11:05:46 - TARGET_ARCH=arm TB --- 2011-12-30 11:05:46 - TZ=UTC TB --- 2011-12-30 11:05:46 - __MAKE_CONF=/dev/null TB --- 2011-12-30 11:05:46 - cd /src TB --- 2011-12-30 11:05:46 - /usr/bin/make -B buildkernel KERNCONF=GUMSTIX >>> Kernel build for GUMSTIX started on Fri Dec 30 11:05:46 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 GUMSTIX completed on Fri Dec 30 11:08:07 UTC 2011 TB --- 2011-12-30 11:08:07 - cd /src/sys/arm/conf TB --- 2011-12-30 11:08:07 - /usr/sbin/config -m HL200 TB --- 2011-12-30 11:08:07 - building HL200 kernel TB --- 2011-12-30 11:08:07 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 11:08:07 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 11:08:07 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 11:08:07 - SRCCONF=/dev/null TB --- 2011-12-30 11:08:07 - TARGET=arm TB --- 2011-12-30 11:08:07 - TARGET_ARCH=arm TB --- 2011-12-30 11:08:07 - TZ=UTC TB --- 2011-12-30 11:08:07 - __MAKE_CONF=/dev/null TB --- 2011-12-30 11:08:07 - cd /src TB --- 2011-12-30 11:08:07 - /usr/bin/make -B buildkernel KERNCONF=HL200 >>> Kernel build for HL200 started on Fri Dec 30 11:08:07 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 HL200 completed on Fri Dec 30 11:10:46 UTC 2011 TB --- 2011-12-30 11:10:46 - cd /src/sys/arm/conf TB --- 2011-12-30 11:10:46 - /usr/sbin/config -m HL201 TB --- 2011-12-30 11:10:47 - building HL201 kernel TB --- 2011-12-30 11:10:47 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 11:10:47 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 11:10:47 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 11:10:47 - SRCCONF=/dev/null TB --- 2011-12-30 11:10:47 - TARGET=arm TB --- 2011-12-30 11:10:47 - TARGET_ARCH=arm TB --- 2011-12-30 11:10:47 - TZ=UTC TB --- 2011-12-30 11:10:47 - __MAKE_CONF=/dev/null TB --- 2011-12-30 11:10:47 - cd /src TB --- 2011-12-30 11:10:47 - /usr/bin/make -B buildkernel KERNCONF=HL201 >>> Kernel build for HL201 started on Fri Dec 30 11:10:47 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 HL201 completed on Fri Dec 30 11:13:36 UTC 2011 TB --- 2011-12-30 11:13:36 - cd /src/sys/arm/conf TB --- 2011-12-30 11:13:36 - /usr/sbin/config -m IQ31244 TB --- 2011-12-30 11:13:37 - building IQ31244 kernel TB --- 2011-12-30 11:13:37 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 11:13:37 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 11:13:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 11:13:37 - SRCCONF=/dev/null TB --- 2011-12-30 11:13:37 - TARGET=arm TB --- 2011-12-30 11:13:37 - TARGET_ARCH=arm TB --- 2011-12-30 11:13:37 - TZ=UTC TB --- 2011-12-30 11:13:37 - __MAKE_CONF=/dev/null TB --- 2011-12-30 11:13:37 - cd /src TB --- 2011-12-30 11:13:37 - /usr/bin/make -B buildkernel KERNCONF=IQ31244 >>> Kernel build for IQ31244 started on Fri Dec 30 11:13:37 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 IQ31244 completed on Fri Dec 30 11:16:54 UTC 2011 TB --- 2011-12-30 11:16:54 - cd /src/sys/arm/conf TB --- 2011-12-30 11:16:54 - /usr/sbin/config -m KB920X TB --- 2011-12-30 11:16:54 - building KB920X kernel TB --- 2011-12-30 11:16:54 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 11:16:54 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 11:16:54 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 11:16:54 - SRCCONF=/dev/null TB --- 2011-12-30 11:16:54 - TARGET=arm TB --- 2011-12-30 11:16:54 - TARGET_ARCH=arm TB --- 2011-12-30 11:16:54 - TZ=UTC TB --- 2011-12-30 11:16:54 - __MAKE_CONF=/dev/null TB --- 2011-12-30 11:16:54 - cd /src TB --- 2011-12-30 11:16:54 - /usr/bin/make -B buildkernel KERNCONF=KB920X >>> Kernel build for KB920X started on Fri Dec 30 11:16:54 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 [...] awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/kern/device_if.m -h echo "#define CFI_SUPPORT_STRATAFLASH 1" > opt_cfi.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/obj/arm.arm/src/sys/KB920X -std=iso9899:1999 /src/sys/modules/cfi/../../dev/cfi/cfi_bus_fdt.c /src/sys/modules/cfi/../../dev/cfi/cfi_bus_ixp4xx.c /src/sys/modules/cfi/../../dev/cfi/cfi_core.c /src/sys/modules/cfi/../../dev/cfi/cfi_dev.c In file included from /src/sys/modules/cfi/../../dev/cfi/cfi_bus_fdt.c:43: @/dev/ofw/ofw_bus.h:36:24: error: ofw_bus_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /src/sys/modules/cfi. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/arm.arm/src/sys/KB920X. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-12-30 11:17:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-12-30 11:17:51 - ERROR: failed to build KB920X kernel TB --- 2011-12-30 11:17:51 - 4393.92 user 1077.57 system 5870.73 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 11:49:13 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4ED16106564A; Fri, 30 Dec 2011 11:49:13 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id ED53B8FC0A; Fri, 30 Dec 2011 11:49:12 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1RgaxT-0002yR-IJ>; Fri, 30 Dec 2011 12:49:11 +0100 Received: from e178010071.adsl.alicedsl.de ([85.178.10.71] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1RgaxT-0001N1-D7>; Fri, 30 Dec 2011 12:49:11 +0100 Message-ID: <4EFDA536.4010101@zedat.fu-berlin.de> Date: Fri, 30 Dec 2011 12:49:10 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Mark Linimon References: <4EF25468.9040204@gmail.com> <4EF2C613.3020609@digsys.bg> <4EF3D68C.2060803@zedat.fu-berlin.de> <20111223074706.1afe4d26@zelda.sugioarto.com> <4EF4474B.3050203@digsys.bg> <20111223114424.GA60815@freebsd.org> <4EF5E9FF.2020300@mail.zedat.fu-berlin.de> <20111230090746.GA3992@lonesome.com> In-Reply-To: <20111230090746.GA3992@lonesome.com> X-Enigmail-Version: undefined Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig06372F211F050191E1A075C6" X-Originating-IP: 85.178.10.71 Cc: Alexander Best , "O. Hartmann" , freebsd-current@freebsd.org Subject: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 11:49:13 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig06372F211F050191E1A075C6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 12/30/11 10:07, schrieb Mark Linimon: > On Sat, Dec 24, 2011 at 04:04:31PM +0100, O. Hartmann wrote: >> There maybe serious reasons having the Linuxulator, i do not know. But= >> if not, why spending rare developer resources on that? >=20 > This is a classical misunderstanding of the FreeBSD development model. >=20 > There is no "staff" standing around waiting for assignments, as with > a commercial company. When committers join the project, they usually > (almost always) already have a long list of things that they want to > work on. And then they go work on them. >=20 > Neither the core team, nor the FreeBSD Foundation, "direct" the project= > and its course of development. Some of the members of each do post > emails, or stand up in front of conferences, and say "you know, I think= > it would be really neat if someone did xyz." Sometimes this leads to > results, sometimes not. >=20 > As for the companies that have their own FreeBSD-derived products, > often their goals are tightly focused, e.g. "improve the number of > packets we can pass" or "support our specialized hardware". Some, > but not all, of the resultant work makes it back into FreeBSD. We > get to say "it would be really neat if ..."; and, in addition, point > to possible future minimization of merging and duplication of effort > as a way to save costs long-term. >=20 > But with these exceptions, development is primarily driven from the > bottom-up (individual committers find something they are interested in > working on, and then go work on it), and not the top-down as in "real" > companies. This is the way the overwhelming majority (90+%?) of the > work on FreeBSD gets done. >=20 > So, there's no one "assigned" the tasks of closing PRs, nor working on > coordinating code with the other BSDs, nor working on the Linuxolator, > nor even supporting high-performance computing. >=20 > It's a cooperative anarchy, not a hierarchy. >=20 > mcl By no maen is this what I said or intended to say. oliver --------------enig06372F211F050191E1A075C6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJO/aU2AAoJEOgBcD7A/5N8WMYIAM/NQj1jolKrUBvNlQqLiWIn FCbkP3OoEZxEZ0h+g3Rvnw2HueHiH5NFPUGj5Aegel4RvhQzSefn8bWkX2xFUO6O bEQ21Zom0hjM2/FmJHAple8mbitb2Ev4pCSltaqYBImrXZPD7c90c34F6IH99SVa rjpFfd4vCAnZi7CFVbb0J7FfU6iKddNMxNzJDAlXLHn9R0loEsy8coID97Vd0f28 GDlJDYK1Rv0GOEfkGONgw3YrmlU5hL1kk7BPwei1hhWw1Jk65TF83EEcG63XvTJi AcmWE5GgHfJWCMPkEQjKkKgIaRF0kKenO0iIHwzsWFEvhV6FLKtOtIO7pAKdP+o= =bJIq -----END PGP SIGNATURE----- --------------enig06372F211F050191E1A075C6-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 13:00:46 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EA211065670; Fri, 30 Dec 2011 13:00:46 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 695AE8FC13; Fri, 30 Dec 2011 13:00:42 +0000 (UTC) Received: by iadj38 with SMTP id j38so32027808iad.13 for ; Fri, 30 Dec 2011 05:00:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0MbvcyFA/f147B/kHGo2/BAPi+i0zkXzPLSL7QEsM3Y=; b=A+X8QZhyG860yFpWZejNAwqGcawr//1A4oNQtrRvL49tSrYuuyynTQbTbSP6d8lcpH +W47ZHJVcdyZ44zNqD57XnX/tHYumu/Pq9GK3EKgu7i+zuHCGgWF7hXYFjYdlqxgxcFz zFPYqDLo2TPFJa8+0vdHnxTR4e3RO8RLyf2jU= MIME-Version: 1.0 Received: by 10.50.153.135 with SMTP id vg7mr46231063igb.12.1325250041965; Fri, 30 Dec 2011 05:00:41 -0800 (PST) Received: by 10.231.207.7 with HTTP; Fri, 30 Dec 2011 05:00:39 -0800 (PST) Received: by 10.231.207.7 with HTTP; Fri, 30 Dec 2011 05:00:39 -0800 (PST) In-Reply-To: <4EF45C85.9010709@mail.zedat.fu-berlin.de> References: <4EF25468.9040204@gmail.com> <4EF2C613.3020609@digsys.bg> <4EF3D68C.2060803@zedat.fu-berlin.de> <20111223074706.1afe4d26@zelda.sugioarto.com> <4EF45C85.9010709@mail.zedat.fu-berlin.de> Date: Fri, 30 Dec 2011 13:00:39 +0000 Message-ID: From: Chris Rees To: "O. Hartmann" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Martin Sugioarto , freebsd-current@freebsd.org, Igor Mozolevsky , Kalchev , freebsd-performance@freebsd.org, "O. Hartmann" , Daniel@freebsd.org Subject: Re: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 13:00:46 -0000 On 23 Dec 2011 12:25, "O. Hartmann" wrote: > > Look at Steve Kargls problem. He investigated a SCHED_ULE problem in a > way that is far beyond enough! He gave tests, insights of his setup, bad > performance compared to SCHED_4BSD and what happend? We are still stuck > with this problem and more and more people realise, that FreeBSD does > have somewhere a problem and this seems to be a nasty problem not easy > to find or investigate. But look at how Steve has been silenced in the > past ... > Benchmarks, especially published ones, reveal those pits and soemone > could look into it. > Another problem is this very elite-feeling closed club. Once you managed > it getting into the club of committers or core team members, you'll > probably fight for your seat ... You are aware that Steve is part of the 'elite club', right? Many of us rarely use our @FreeBSD.org addresses; you'd probably be surprised at the names in the Developers list. Just being a committer gives your opinions very little weight; everyone has to make their case in the same way. There's really, really no eliteism here! Chris From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 13:06:50 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D70E1065672; Fri, 30 Dec 2011 13:06:50 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 092498FC13; Fri, 30 Dec 2011 13:06:50 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:408b:3bdd:8466:f24f] (unknown [IPv6:2001:7b8:3a7:0:408b:3bdd:8466:f24f]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 48BF75C37; Fri, 30 Dec 2011 14:06:49 +0100 (CET) Message-ID: <4EFDB76C.1030901@FreeBSD.org> Date: Fri, 30 Dec 2011 14:06:52 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Alexander Best References: <20111226101040.GA6361@freebsd.org> In-Reply-To: <20111226101040.GA6361@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-toolchain@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 13:06:50 -0000 On 2011-12-26 11:10, Alexander Best wrote: > that's why i'd like to propose the following patch. i ran a full tinderbox run > against r228878 and it suceeded. Did you also try this with clang? For example the xfs module alone gets a whole slew of warnings, which would be fatal if WERROR= was removed: sys/gnu/fs/xfs/xfs_dir2_block.c:1149:17: warning: array index of '1' indexes past the end of an array (that contains 1 element) [-Warray-bounds] dep->name[0] = dep->name[1] = '.'; ^ ~ sys/gnu/fs/xfs/xfs_dir2_data.h:90:2: note: array 'name' declared here __uint8_t name[1]; /* name bytes, no null */ ^ 1 warning generated. sys/gnu/fs/xfs/xfs_dir2_sf.c:117:27: warning: array index of '1' indexes past the end of an array (that contains 1 element) [-Warray-bounds] dep->name[0] == '.' && dep->name[1] == '.'; ^ ~ sys/gnu/fs/xfs/xfs_dir2_data.h:90:2: note: array 'name' declared here __uint8_t name[1]; /* name bytes, no null */ ^ sys/gnu/fs/xfs/xfs_dir2_sf.c:237:28: warning: array index of '1' indexes past the end of an array (that contains 1 element) [-Warray-bounds] dep->name[0] == '.' && dep->name[1] == '.') ^ ~ sys/gnu/fs/xfs/xfs_dir2_data.h:90:2: note: array 'name' declared here __uint8_t name[1]; /* name bytes, no null */ ^ 2 warnings generated. sys/gnu/fs/xfs/xfs_vfsops.c:1958:19: warning: format string is not a string literal (potentially insecure) [-Wformat-security] sbuf_printf(m, xfs_infop->str); ^~~~~~~~~~~~~~ 1 warning generated. sys/gnu/fs/xfs/FreeBSD/xfs_super.c:257:9: warning: format string is not a string literal (potentially insecure) [-Wformat-security] printf(message); ^~~~~~~ 1 warning generated. sys/gnu/fs/xfs/FreeBSD/xfs_stats.c:68:32: warning: format string is not a string literal (potentially insecure) [-Wformat-security] len += sprintf(buffer + len, xstats[i].desc); ^~~~~~~~~~~~~~ sys/gnu/fs/xfs/FreeBSD/xfs_stats.c:99:33: warning: if statement has empty body [-Wempty-body] if (&xfs_read_xfsstats != NULL); ^ 2 warnings generated. sys/gnu/fs/xfs/FreeBSD/xfs_ioctl.c:1252:10: warning: explicitly assigning a variable of type 'int' to itself [-Wself-assign] error = error; ~~~~~ ^ ~~~~~ sys/gnu/fs/xfs/FreeBSD/xfs_ioctl.c:1290:9: warning: explicitly assigning a variable of type 'int' to itself [-Wself-assign] error = error; ~~~~~ ^ ~~~~~ sys/gnu/fs/xfs/FreeBSD/xfs_ioctl.c:1299:10: warning: explicitly assigning a variable of type 'int' to itself [-Wself-assign] error = error; ~~~~~ ^ ~~~~~ sys/gnu/fs/xfs/FreeBSD/xfs_ioctl.c:1350:9: warning: explicitly assigning a variable of type 'int' to itself [-Wself-assign] error = error; ~~~~~ ^ ~~~~~ 4 warnings generated. Most of the warnings should probably be fixed, but as this is mainly contrib code, and GPL to boot, it makes not much sense to do so. From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 13:25:47 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65998106564A for ; Fri, 30 Dec 2011 13:25:47 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1EFFB8FC12 for ; Fri, 30 Dec 2011 13:25:46 +0000 (UTC) Received: by yenl9 with SMTP id l9so9186948yen.13 for ; Fri, 30 Dec 2011 05:25:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=9b+nxi5xvEeJLt2v11v9WViApgGT5+JSGh6SmXWOalo=; b=bah3dGvvlelzBF6W12XpWsJj5Pu/4aAWESlMtOr6GXrurGvHGw65gRNNozlxyuNsLL kjMwxdhAzOCzhNpbfVXw+XfYNPIR5p4hTRv9sJI/crgICD6KPZs0DPYaCHWSQHr2OPIb w+szHm0CHB77K4QGwG0pLV8uWP6DTLIbQZ0V0= Received: by 10.236.195.73 with SMTP id o49mr2605661yhn.71.1325251546498; Fri, 30 Dec 2011 05:25:46 -0800 (PST) Received: from [192.168.4.106] (c-98-230-64-224.hsd1.al.comcast.net. [98.230.64.224]) by mx.google.com with ESMTPS id j11sm32188808anl.8.2011.12.30.05.25.45 (version=SSLv3 cipher=OTHER); Fri, 30 Dec 2011 05:25:45 -0800 (PST) Message-ID: <4EFDBBDB.4090506@gmail.com> Date: Fri, 30 Dec 2011 07:25:47 -0600 From: Chuck Burns User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20111226101040.GA6361@freebsd.org> <4EFDB76C.1030901@FreeBSD.org> In-Reply-To: <4EFDB76C.1030901@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 13:25:47 -0000 On 12/30/2011 7:06 AM, Dimitry Andric wrote: > On 2011-12-26 11:10, Alexander Best wrote: >> that's why i'd like to propose the following patch. i ran a full >> tinderbox run >> against r228878 and it suceeded. > > Did you also try this with clang? For example the xfs module alone gets > a whole slew of warnings, which would be fatal if WERROR= was removed: > > sys/gnu/fs/xfs/xfs_dir2_block.c:1149:17: warning: array index of '1' > indexes past the end of an array (that contains 1 element) [-Warray-bounds] > dep->name[0] = dep->name[1] = '.'; > ^ ~ > sys/gnu/fs/xfs/xfs_dir2_data.h:90:2: note: array 'name' declared here > __uint8_t name[1]; /* name bytes, no null */ > ^ > 1 warning generated. just as an aside, the XFS module didn't seem to work when I last attempted to use it, so it may be worth just removing it? -- Chuck Burns The Southern Libertarian http://www.thesouthernlibertarian.com/ From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 13:43:40 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FF2E106566B; Fri, 30 Dec 2011 13:43:40 +0000 (UTC) (envelope-from tijl@coosemans.org) Received: from mailrelay009.isp.belgacom.be (mailrelay009.isp.belgacom.be [195.238.6.176]) by mx1.freebsd.org (Postfix) with ESMTP id 5C92D8FC17; Fri, 30 Dec 2011 13:43:38 +0000 (UTC) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAB+4/U5bsQ3b/2dsb2JhbABDrE6BBoFyAQEFJy8jEAsYLjkeGYd8thaDfYR4gxoEiASGIpkR Received: from 219.13-177-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.177.13.219]) by relay.skynet.be with ESMTP; 30 Dec 2011 14:13:36 +0100 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.14.5/8.14.5) with ESMTP id pBUDDZ24001806; Fri, 30 Dec 2011 14:13:35 +0100 (CET) (envelope-from tijl@coosemans.org) From: Tijl Coosemans To: freebsd-current@freebsd.org Date: Fri, 30 Dec 2011 14:13:25 +0100 User-Agent: KMail/1.13.7 (FreeBSD/10.0-CURRENT; KDE/4.7.3; i386; ; ) References: <4EFC0127.6030301@FreeBSD.org> <4EFC5487.3080709@orange.fr> In-Reply-To: <4EFC5487.3080709@orange.fr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6025371.nWztoTEdQX"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201112301413.32750.tijl@coosemans.org> Cc: "Joseph S. Atkinson" , Alexander Motin Subject: Re: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 13:43:40 -0000 --nextPart6025371.nWztoTEdQX Content-Type: multipart/mixed; boundary="Boundary-01=_2jb/ONakLCsTfGs" Content-Transfer-Encoding: 7bit --Boundary-01=_2jb/ONakLCsTfGs Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 29 December 2011 12:52:39 Claude Buisson wrote: > On 12/29/2011 07:41, Garrett Cooper wrote: >> On Wed, Dec 28, 2011 at 9:56 PM, Joseph S. Atkinson wr= ote: >>> I am the maintainer of VLC, I have an outstanding PR (ports/162190) on = the >>> issue of cdda:// access. >>> >>> I can confirm this issues, but don't know enough about driver access to= fix >>> this myself. Doug Barton reports that cdcontrol(1) doesn't work for him= , and >>> mplayer and audactiy also display issues running as non-root. >>> >>> Under 9.0-RC3 r228843, I get these errors on boot with no disc present = in >>> /dev/cd0 at all. >>> >>> (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00= 01 >>> 00 >>> (pass1:ahcich2:0:0:0): CAM status: ATA Status Error >>> (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) >>> (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 >>> >>> These ports are fairly popular, but the problems may not lie exclusively >>> with their assumptions about FreeBSD. I am running 10.0 on another mach= ine >>> specifically to test changes under src/sys/cam. >>> >>> I am worried that with the actual 9.0-RELEASE on the horizon, users will >>> find show stopping problems using their disc drives. >> >> Try having users merge r228808 and r228847. If that works, then I >> would press re@ produce another RC that fixes this. >> Thanks, >> -Garrett >> >> PS This is coming from a user that was annoyed by this gap with the >> ATA_CAM code. >=20 > As the submitter of ports/162190, I would firstly ask: >=20 > Is the problem corrected by r228808 and r228847 in 10.0-CURRENT ? >=20 > If not merging to 9.0 is useless. >=20 > If yes I could test. There are 3 methods to access audio CDs. =2D if your drive is connected to your sound card you can use the drive's built-in audio support (if present). (used by cdcontrol) =2D read raw audio data via the CAM layer. (used by cdparanoia) =2D read raw audio data via the cd(4) driver. (used by vlc, libcdio?) The first two should work. The last one has now been fixed in CURRENT, but programs using that method also seem to use CDRIOCSETBLOCKSIZE ioctl that cd doesn't implement. The driver already knows the correct block size though, so it seems safe to ignore the error. With the attached patch vlc works for me. --Boundary-01=_2jb/ONakLCsTfGs Content-Type: text/plain; charset="iso-8859-1"; name="patch-modules__access__vcd__cdrom.c" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="patch-modules__access__vcd__cdrom.c" =2D-- modules/access/vcd/cdrom.c.orig +++ modules/access/vcd/cdrom.c @@ -553,9 +553,6 @@ if( ioctl( p_vcddev->i_device_handle, CDRIOCSETBLOCKSIZE, &i_size ) =3D=3D -1 ) { =2D msg_Err( p_this, "Could not set block size" ); =2D if( i_type =3D=3D VCD_TYPE ) free( p_block ); =2D return( -1 ); } =20 if( lseek( p_vcddev->i_device_handle, --Boundary-01=_2jb/ONakLCsTfGs-- --nextPart6025371.nWztoTEdQX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iF4EABEIAAYFAk79uPwACgkQfoCS2CCgtiuDnQD9GzveJJ0ciCHqUjlwEKFhNrTj uVFbkipqZ831iu9v4vgA/A/SqAZQhCayrbJkXV56g0jLWtQEYBn3Tpber0mGH01r =yETJ -----END PGP SIGNATURE----- --nextPart6025371.nWztoTEdQX-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 14:08:35 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5270106564A; Fri, 30 Dec 2011 14:08:35 +0000 (UTC) (envelope-from theraven@theravensnest.org) Received: from theravensnest.org (theravensnest.org [109.169.23.128]) by mx1.freebsd.org (Postfix) with ESMTP id 7C5F08FC0C; Fri, 30 Dec 2011 14:08:35 +0000 (UTC) Received: from [192.168.0.2] (cpc2-cwma5-0-0-cust875.7-3.cable.virginmedia.com [86.11.39.108]) (authenticated bits=0) by theravensnest.org (8.14.4/8.14.4) with ESMTP id pBUDSpdF032333 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Fri, 30 Dec 2011 13:28:51 GMT (envelope-from theraven@theravensnest.org) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: David Chisnall In-Reply-To: <4EFDB76C.1030901@FreeBSD.org> Date: Fri, 30 Dec 2011 13:28:51 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20111226101040.GA6361@freebsd.org> <4EFDB76C.1030901@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.1251.1) X-Mailman-Approved-At: Fri, 30 Dec 2011 14:40:57 +0000 Cc: Alexander Best , freebsd-toolchain@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 14:08:36 -0000 On 30 Dec 2011, at 13:06, Dimitry Andric wrote: > sys/gnu/fs/xfs/xfs_dir2_block.c:1149:17: warning: array index of '1' = indexes past the end of an array (that contains 1 element) = [-Warray-bounds] I recall some discussion of this warning on the clang list a few months = ago, and I believe that it should now only appear if you are compiling = in a C99 or C11 dialect mode (the rationale is that any variable-length = structures in C99 should be using a zero-sized array as the final = element, while C89 lacked any ability to do this). =20 I suspect a lot of similar warnings are caused by the difference in = default dialects between clang and gcc. Adding an explicit -std=3Dc89 = to the cflags any modules that are using an archaic dialect of C may = silence a lot of these... David= From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 16:11:22 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5707106564A for ; Fri, 30 Dec 2011 16:11:22 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) by mx1.freebsd.org (Postfix) with ESMTP id 2CFD58FC17 for ; Fri, 30 Dec 2011 16:11:21 +0000 (UTC) Received: from localhost ([92.156.99.49]) by mwinf5d62 with ME id FUBJ1i00F13w9uc03UBJUH; Fri, 30 Dec 2011 17:11:20 +0100 Message-ID: <4EFDE2A5.4060007@orange.fr> Date: Fri, 30 Dec 2011 17:11:17 +0100 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.25) Gecko/20111228 Thunderbird/3.1.17 MIME-Version: 1.0 To: Tijl Coosemans References: <4EFC0127.6030301@FreeBSD.org> <4EFC5487.3080709@orange.fr> <201112301413.32750.tijl@coosemans.org> In-Reply-To: <201112301413.32750.tijl@coosemans.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Joseph S. Atkinson" , Alexander Motin , freebsd-current@freebsd.org Subject: Re: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 16:11:22 -0000 On 12/30/2011 14:13, Tijl Coosemans wrote: > On Thursday 29 December 2011 12:52:39 Claude Buisson wrote: >> On 12/29/2011 07:41, Garrett Cooper wrote: >>> On Wed, Dec 28, 2011 at 9:56 PM, Joseph S. Atkinson wrote: >>>> I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the >>>> issue of cdda:// access. >>>> >>>> I can confirm this issues, but don't know enough about driver access to fix >>>> this myself. Doug Barton reports that cdcontrol(1) doesn't work for him, and >>>> mplayer and audactiy also display issues running as non-root. >>>> >>>> Under 9.0-RC3 r228843, I get these errors on boot with no disc present in >>>> /dev/cd0 at all. >>>> >>>> (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 >>>> 00 >>>> (pass1:ahcich2:0:0:0): CAM status: ATA Status Error >>>> (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) >>>> (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 >>>> >>>> These ports are fairly popular, but the problems may not lie exclusively >>>> with their assumptions about FreeBSD. I am running 10.0 on another machine >>>> specifically to test changes under src/sys/cam. >>>> >>>> I am worried that with the actual 9.0-RELEASE on the horizon, users will >>>> find show stopping problems using their disc drives. >>> >>> Try having users merge r228808 and r228847. If that works, then I >>> would press re@ produce another RC that fixes this. >>> Thanks, >>> -Garrett >>> >>> PS This is coming from a user that was annoyed by this gap with the >>> ATA_CAM code. >> >> As the submitter of ports/162190, I would firstly ask: >> >> Is the problem corrected by r228808 and r228847 in 10.0-CURRENT ? >> >> If not merging to 9.0 is useless. >> >> If yes I could test. > > There are 3 methods to access audio CDs. > - if your drive is connected to your sound card you can use the drive's > built-in audio support (if present). (used by cdcontrol) > - read raw audio data via the CAM layer. (used by cdparanoia) > - read raw audio data via the cd(4) driver. (used by vlc, libcdio?) > > The first two should work. The last one has now been fixed in CURRENT, > but programs using that method also seem to use CDRIOCSETBLOCKSIZE > ioctl that cd doesn't implement. The driver already knows the correct > block size though, so it seems safe to ignore the error. With the > attached patch vlc works for me. I just made the jump, and applied r228808 and r228847 to my sources (stable/9 dated 11/11/27 = svn r228043), and rebuilt vlc with your patch. Conclusion: IT WORKS !! and I am currently playing an audio CD as I type this message. I will make a followup to ports/162190, and hope that the cam patches will be MFCed before the release. Thanks CBu From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 16:18:38 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81698106564A; Fri, 30 Dec 2011 16:18:38 +0000 (UTC) (envelope-from hyama99@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id E2BCE8FC1D; Fri, 30 Dec 2011 16:18:37 +0000 (UTC) Received: by eekc50 with SMTP id c50so16547259eek.13 for ; Fri, 30 Dec 2011 08:18:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=L5/0wQavAhPfTJbRz4TGx7aibIMQPHIKBsCWAExr8Ho=; b=X5pLrnjYqWSIx3zJeLAnC4PUQdHGhCJl4DvDp12D7UfyNN+99iovGXjqSYf60BLdn6 gaQs8E4hFdlodG6LBzqLhOucjsf1tA5hEQZ84o1pVeJPXAF471CSOllML6qDXEY1lqPX Jxvh+OTr7C0TPLrDiDEw/+Jfg5gAPB27AdY8g= MIME-Version: 1.0 Received: by 10.213.19.68 with SMTP id z4mr9719028eba.116.1325260220724; Fri, 30 Dec 2011 07:50:20 -0800 (PST) Received: by 10.213.102.14 with HTTP; Fri, 30 Dec 2011 07:50:20 -0800 (PST) In-Reply-To: <20111019.163054.907132735733393734.hrs@allbsd.org> References: <20111019.070718.1020945298589023580.hrs@allbsd.org> <4E9DFD46.1040306@delphij.net> <20111019.163054.907132735733393734.hrs@allbsd.org> Date: Sat, 31 Dec 2011 00:50:20 +0900 Message-ID: From: Hideki Yamamoto To: Hiroki Sato Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: delphij@delphij.net, freebsd-current@freebsd.org, d@delphij.net Subject: Re: About FreeBSD 9.0 release note X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 16:18:38 -0000 Hi all; I happen to find the 9.0-Current release notes page, but I could not find my requested text there. Are there another text for 9.0-RELEASE? http://www.freebsd.org/relnotes/CURRENT/relnotes/index.html If yes, would someone please inform me of the URL? Best regards, Hideki Yamamoto 2011/10/19 Hiroki Sato : > Xin LI wrote > =A0in <4E9DFD46.1040306@delphij.net>: > > de> -----BEGIN PGP SIGNED MESSAGE----- > de> Hash: SHA256 > de> > de> On 10/18/11 15:07, Hiroki Sato wrote: > de> > Hideki Yamamoto wrote in > de> > : > de> > > de> > =A0hy> Hi, hy> hy> Does someone know where is the draft of FreeBSD > de> > 9.0 release note? hy> I would like to check if there is a > de> > description about new functions hy> about MLDv2 is included or > de> > not. hy> I think the below feature should be included in the > de> > release note as hy> IPv6 network is getting popular. hy> hy> > de> > --------------------------------- hy> MFC r200871: hy> =A0Use > de> > ALLOW_NEW_SOURCES and BLOCK_OLD_SOURCES to signal a join or leave > de> > hy> =A0with SSM MLDv2 by default. hy> =A0This is current practice a= nd > de> > complies with RFC 4604, as well as being hy> =A0required by > de> > production IPv6 networks in Japan. hy> =A0The behaviour may be > de> > disabled by setting the net.inet6.mld.use_allow hy> =A0sysctl/tunab= le > de> > to 0. hy> ------------------------------------- > de> > > de> > I am already working on the relnotes and the above will be > de> > included as an improvement of the IPv6 stack. > de> > de> Can we have it somewhere (in the CVS or wiki) so we can work together > de> on that? =A0This way also makes translation easier... > > =A0Yes, I will put it to some shared workspace as soon as possible. =A0I > =A0know I should have taken an action more quickly, but I couldn't make > =A0it. =A0Sorry. > > -- Hiroki From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 17:04:58 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D0E51065670; Fri, 30 Dec 2011 17:04:58 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 283728FC19; Fri, 30 Dec 2011 17:04:58 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:408b:3bdd:8466:f24f] (unknown [IPv6:2001:7b8:3a7:0:408b:3bdd:8466:f24f]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id F0C3C5C37; Fri, 30 Dec 2011 18:04:56 +0100 (CET) Message-ID: <4EFDEF3B.4090200@FreeBSD.org> Date: Fri, 30 Dec 2011 18:04:59 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: David Chisnall References: <20111226101040.GA6361@freebsd.org> <4EFDB76C.1030901@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Best , freebsd-toolchain@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [rfc] removing/conditionalising WERROR= in Makefiles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 17:04:58 -0000 On 2011-12-30 14:28, David Chisnall wrote: > On 30 Dec 2011, at 13:06, Dimitry Andric wrote: > >> sys/gnu/fs/xfs/xfs_dir2_block.c:1149:17: warning: array index of '1' indexes past the end of an array (that contains 1 element) [-Warray-bounds] > > I recall some discussion of this warning on the clang list a few months ago, and I believe that it should now only appear if you are compiling in a C99 or C11 dialect mode (the rationale is that any variable-length structures in C99 should be using a zero-sized array as the final element, while C89 lacked any ability to do this). Yes, that is perfectly fine, but the xfs code defines the struct in question as follows: /* * Active entry in a data block. Aligned to 8 bytes. * Tag appears as the last 2 bytes. */ typedef struct xfs_dir2_data_entry { xfs_ino_t inumber; /* inode number */ __uint8_t namelen; /* name length */ __uint8_t name[1]; /* name bytes, no null */ /* variable offset */ xfs_dir2_data_off_t tag; /* starting offset of us */ } xfs_dir2_data_entry_t; E.g there *is* an overrun, but maybe it was really supposed to be like that. Meanwhile, upstream has apparently caught on: http://oss.sgi.com/archives/xfs/2011-07/msg00024.html From owner-freebsd-current@FreeBSD.ORG Fri Dec 30 18:38:46 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08F25106566B; Fri, 30 Dec 2011 18:38:46 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id AF3368FC0A; Fri, 30 Dec 2011 18:38:45 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.4) with ESMTP id pBUIcijM023652; Fri, 30 Dec 2011 13:38:44 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.4/Submit) id pBUIciP0023599; Fri, 30 Dec 2011 18:38:44 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 30 Dec 2011 18:38:44 GMT Message-Id: <201112301838.pBUIciP0023599@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on arm/arm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2011 18:38:46 -0000 TB --- 2011-12-30 17:00:01 - tinderbox 2.8 running on freebsd-current.sentex.ca TB --- 2011-12-30 17:00:01 - starting HEAD tinderbox run for arm/arm TB --- 2011-12-30 17:00:01 - cleaning the object tree TB --- 2011-12-30 17:00:25 - cvsupping the source tree TB --- 2011-12-30 17:00:25 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2011-12-30 17:00:43 - building world TB --- 2011-12-30 17:00:43 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 17:00:43 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 17:00:43 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 17:00:43 - SRCCONF=/dev/null TB --- 2011-12-30 17:00:43 - TARGET=arm TB --- 2011-12-30 17:00:43 - TARGET_ARCH=arm TB --- 2011-12-30 17:00:43 - TZ=UTC TB --- 2011-12-30 17:00:43 - __MAKE_CONF=/dev/null TB --- 2011-12-30 17:00:43 - cd /src TB --- 2011-12-30 17:00:43 - /usr/bin/make -B buildworld >>> World build started on Fri Dec 30 17:00:45 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 Dec 30 17:57:38 UTC 2011 TB --- 2011-12-30 17:57:38 - cd /src/sys/arm/conf TB --- 2011-12-30 17:57:38 - /usr/sbin/config -m AVILA TB --- 2011-12-30 17:57:38 - building AVILA kernel TB --- 2011-12-30 17:57:38 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 17:57:38 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 17:57:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 17:57:38 - SRCCONF=/dev/null TB --- 2011-12-30 17:57:38 - TARGET=arm TB --- 2011-12-30 17:57:38 - TARGET_ARCH=arm TB --- 2011-12-30 17:57:38 - TZ=UTC TB --- 2011-12-30 17:57:38 - __MAKE_CONF=/dev/null TB --- 2011-12-30 17:57:38 - cd /src TB --- 2011-12-30 17:57:38 - /usr/bin/make -B buildkernel KERNCONF=AVILA >>> Kernel build for AVILA started on Fri Dec 30 17:57:38 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 Dec 30 18:00:46 UTC 2011 TB --- 2011-12-30 18:00:46 - cd /src/sys/arm/conf TB --- 2011-12-30 18:00:46 - /usr/sbin/config -m BWCT TB --- 2011-12-30 18:00:46 - building BWCT kernel TB --- 2011-12-30 18:00:46 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:00:46 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:00:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:00:46 - SRCCONF=/dev/null TB --- 2011-12-30 18:00:46 - TARGET=arm TB --- 2011-12-30 18:00:46 - TARGET_ARCH=arm TB --- 2011-12-30 18:00:46 - TZ=UTC TB --- 2011-12-30 18:00:46 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:00:46 - cd /src TB --- 2011-12-30 18:00:46 - /usr/bin/make -B buildkernel KERNCONF=BWCT >>> Kernel build for BWCT started on Fri Dec 30 18:00:46 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 Dec 30 18:03:23 UTC 2011 TB --- 2011-12-30 18:03:23 - cd /src/sys/arm/conf TB --- 2011-12-30 18:03:23 - /usr/sbin/config -m CAMBRIA TB --- 2011-12-30 18:03:23 - building CAMBRIA kernel TB --- 2011-12-30 18:03:23 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:03:23 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:03:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:03:23 - SRCCONF=/dev/null TB --- 2011-12-30 18:03:23 - TARGET=arm TB --- 2011-12-30 18:03:23 - TARGET_ARCH=arm TB --- 2011-12-30 18:03:23 - TZ=UTC TB --- 2011-12-30 18:03:23 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:03:23 - cd /src TB --- 2011-12-30 18:03:23 - /usr/bin/make -B buildkernel KERNCONF=CAMBRIA >>> Kernel build for CAMBRIA started on Fri Dec 30 18:03:23 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 Fri Dec 30 18:06:19 UTC 2011 TB --- 2011-12-30 18:06:19 - cd /src/sys/arm/conf TB --- 2011-12-30 18:06:19 - /usr/sbin/config -m CNS11XXNAS TB --- 2011-12-30 18:06:19 - building CNS11XXNAS kernel TB --- 2011-12-30 18:06:19 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:06:19 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:06:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:06:19 - SRCCONF=/dev/null TB --- 2011-12-30 18:06:19 - TARGET=arm TB --- 2011-12-30 18:06:19 - TARGET_ARCH=arm TB --- 2011-12-30 18:06:19 - TZ=UTC TB --- 2011-12-30 18:06:19 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:06:19 - cd /src TB --- 2011-12-30 18:06:19 - /usr/bin/make -B buildkernel KERNCONF=CNS11XXNAS >>> Kernel build for CNS11XXNAS started on Fri Dec 30 18:06:19 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 CNS11XXNAS completed on Fri Dec 30 18:08:52 UTC 2011 TB --- 2011-12-30 18:08:52 - cd /src/sys/arm/conf TB --- 2011-12-30 18:08:52 - /usr/sbin/config -m CRB TB --- 2011-12-30 18:08:52 - building CRB kernel TB --- 2011-12-30 18:08:52 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:08:52 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:08:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:08:52 - SRCCONF=/dev/null TB --- 2011-12-30 18:08:52 - TARGET=arm TB --- 2011-12-30 18:08:52 - TARGET_ARCH=arm TB --- 2011-12-30 18:08:52 - TZ=UTC TB --- 2011-12-30 18:08:52 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:08:52 - cd /src TB --- 2011-12-30 18:08:52 - /usr/bin/make -B buildkernel KERNCONF=CRB >>> Kernel build for CRB started on Fri Dec 30 18:08:52 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 CRB completed on Fri Dec 30 18:12:46 UTC 2011 TB --- 2011-12-30 18:12:46 - cd /src/sys/arm/conf TB --- 2011-12-30 18:12:46 - /usr/sbin/config -m DB-78XXX TB --- 2011-12-30 18:12:46 - building DB-78XXX kernel TB --- 2011-12-30 18:12:46 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:12:46 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:12:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:12:46 - SRCCONF=/dev/null TB --- 2011-12-30 18:12:46 - TARGET=arm TB --- 2011-12-30 18:12:46 - TARGET_ARCH=arm TB --- 2011-12-30 18:12:46 - TZ=UTC TB --- 2011-12-30 18:12:46 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:12:46 - cd /src TB --- 2011-12-30 18:12:46 - /usr/bin/make -B buildkernel KERNCONF=DB-78XXX >>> Kernel build for DB-78XXX started on Fri Dec 30 18:12:46 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 DB-78XXX completed on Fri Dec 30 18:15:27 UTC 2011 TB --- 2011-12-30 18:15:27 - cd /src/sys/arm/conf TB --- 2011-12-30 18:15:27 - /usr/sbin/config -m DB-88F5XXX TB --- 2011-12-30 18:15:27 - building DB-88F5XXX kernel TB --- 2011-12-30 18:15:27 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:15:27 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:15:27 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:15:27 - SRCCONF=/dev/null TB --- 2011-12-30 18:15:27 - TARGET=arm TB --- 2011-12-30 18:15:27 - TARGET_ARCH=arm TB --- 2011-12-30 18:15:27 - TZ=UTC TB --- 2011-12-30 18:15:27 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:15:27 - cd /src TB --- 2011-12-30 18:15:27 - /usr/bin/make -B buildkernel KERNCONF=DB-88F5XXX >>> Kernel build for DB-88F5XXX started on Fri Dec 30 18:15:27 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 DB-88F5XXX completed on Fri Dec 30 18:18:05 UTC 2011 TB --- 2011-12-30 18:18:05 - cd /src/sys/arm/conf TB --- 2011-12-30 18:18:05 - /usr/sbin/config -m DB-88F6XXX TB --- 2011-12-30 18:18:05 - building DB-88F6XXX kernel TB --- 2011-12-30 18:18:05 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:18:05 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:18:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:18:05 - SRCCONF=/dev/null TB --- 2011-12-30 18:18:05 - TARGET=arm TB --- 2011-12-30 18:18:05 - TARGET_ARCH=arm TB --- 2011-12-30 18:18:05 - TZ=UTC TB --- 2011-12-30 18:18:05 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:18:05 - cd /src TB --- 2011-12-30 18:18:05 - /usr/bin/make -B buildkernel KERNCONF=DB-88F6XXX >>> Kernel build for DB-88F6XXX started on Fri Dec 30 18:18: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 DB-88F6XXX completed on Fri Dec 30 18:21:19 UTC 2011 TB --- 2011-12-30 18:21:19 - cd /src/sys/arm/conf TB --- 2011-12-30 18:21:19 - /usr/sbin/config -m DOCKSTAR TB --- 2011-12-30 18:21:19 - building DOCKSTAR kernel TB --- 2011-12-30 18:21:19 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:21:19 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:21:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:21:19 - SRCCONF=/dev/null TB --- 2011-12-30 18:21:19 - TARGET=arm TB --- 2011-12-30 18:21:19 - TARGET_ARCH=arm TB --- 2011-12-30 18:21:19 - TZ=UTC TB --- 2011-12-30 18:21:19 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:21:19 - cd /src TB --- 2011-12-30 18:21:19 - /usr/bin/make -B buildkernel KERNCONF=DOCKSTAR >>> Kernel build for DOCKSTAR started on Fri Dec 30 18:21:19 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 DOCKSTAR completed on Fri Dec 30 18:23:54 UTC 2011 TB --- 2011-12-30 18:23:54 - cd /src/sys/arm/conf TB --- 2011-12-30 18:23:54 - /usr/sbin/config -m EP80219 TB --- 2011-12-30 18:23:54 - building EP80219 kernel TB --- 2011-12-30 18:23:54 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:23:54 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:23:54 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:23:54 - SRCCONF=/dev/null TB --- 2011-12-30 18:23:54 - TARGET=arm TB --- 2011-12-30 18:23:54 - TARGET_ARCH=arm TB --- 2011-12-30 18:23:54 - TZ=UTC TB --- 2011-12-30 18:23:54 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:23:54 - cd /src TB --- 2011-12-30 18:23:54 - /usr/bin/make -B buildkernel KERNCONF=EP80219 >>> Kernel build for EP80219 started on Fri Dec 30 18:23:54 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 EP80219 completed on Fri Dec 30 18:26:48 UTC 2011 TB --- 2011-12-30 18:26:48 - WARNING: no kernel config for GENERIC TB --- 2011-12-30 18:26:48 - cd /src/sys/arm/conf TB --- 2011-12-30 18:26:48 - /usr/sbin/config -m GUMSTIX TB --- 2011-12-30 18:26:48 - building GUMSTIX kernel TB --- 2011-12-30 18:26:48 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:26:48 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:26:48 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:26:48 - SRCCONF=/dev/null TB --- 2011-12-30 18:26:48 - TARGET=arm TB --- 2011-12-30 18:26:48 - TARGET_ARCH=arm TB --- 2011-12-30 18:26:48 - TZ=UTC TB --- 2011-12-30 18:26:48 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:26:48 - cd /src TB --- 2011-12-30 18:26:48 - /usr/bin/make -B buildkernel KERNCONF=GUMSTIX >>> Kernel build for GUMSTIX started on Fri Dec 30 18:26:48 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 GUMSTIX completed on Fri Dec 30 18:29:36 UTC 2011 TB --- 2011-12-30 18:29:36 - cd /src/sys/arm/conf TB --- 2011-12-30 18:29:36 - /usr/sbin/config -m HL200 TB --- 2011-12-30 18:29:37 - building HL200 kernel TB --- 2011-12-30 18:29:37 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:29:37 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:29:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:29:37 - SRCCONF=/dev/null TB --- 2011-12-30 18:29:37 - TARGET=arm TB --- 2011-12-30 18:29:37 - TARGET_ARCH=arm TB --- 2011-12-30 18:29:37 - TZ=UTC TB --- 2011-12-30 18:29:37 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:29:37 - cd /src TB --- 2011-12-30 18:29:37 - /usr/bin/make -B buildkernel KERNCONF=HL200 >>> Kernel build for HL200 started on Fri Dec 30 18:29:37 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 HL200 completed on Fri Dec 30 18:32:19 UTC 2011 TB --- 2011-12-30 18:32:19 - cd /src/sys/arm/conf TB --- 2011-12-30 18:32:19 - /usr/sbin/config -m HL201 TB --- 2011-12-30 18:32:19 - building HL201 kernel TB --- 2011-12-30 18:32:19 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:32:19 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:32:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:32:19 - SRCCONF=/dev/null TB --- 2011-12-30 18:32:19 - TARGET=arm TB --- 2011-12-30 18:32:19 - TARGET_ARCH=arm TB --- 2011-12-30 18:32:19 - TZ=UTC TB --- 2011-12-30 18:32:19 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:32:19 - cd /src TB --- 2011-12-30 18:32:19 - /usr/bin/make -B buildkernel KERNCONF=HL201 >>> Kernel build for HL201 started on Fri Dec 30 18:32:19 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 HL201 completed on Fri Dec 30 18:34:34 UTC 2011 TB --- 2011-12-30 18:34:34 - cd /src/sys/arm/conf TB --- 2011-12-30 18:34:34 - /usr/sbin/config -m IQ31244 TB --- 2011-12-30 18:34:34 - building IQ31244 kernel TB --- 2011-12-30 18:34:34 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:34:34 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:34:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:34:34 - SRCCONF=/dev/null TB --- 2011-12-30 18:34:34 - TARGET=arm TB --- 2011-12-30 18:34:34 - TARGET_ARCH=arm TB --- 2011-12-30 18:34:34 - TZ=UTC TB --- 2011-12-30 18:34:34 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:34:34 - cd /src TB --- 2011-12-30 18:34:34 - /usr/bin/make -B buildkernel KERNCONF=IQ31244 >>> Kernel build for IQ31244 started on Fri Dec 30 18:34: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 IQ31244 completed on Fri Dec 30 18:37:49 UTC 2011 TB --- 2011-12-30 18:37:49 - cd /src/sys/arm/conf TB --- 2011-12-30 18:37:49 - /usr/sbin/config -m KB920X TB --- 2011-12-30 18:37:49 - building KB920X kernel TB --- 2011-12-30 18:37:49 - CROSS_BUILD_TESTING=YES TB --- 2011-12-30 18:37:49 - MAKEOBJDIRPREFIX=/obj TB --- 2011-12-30 18:37:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-12-30 18:37:49 - SRCCONF=/dev/null TB --- 2011-12-30 18:37:49 - TARGET=arm TB --- 2011-12-30 18:37:49 - TARGET_ARCH=arm TB --- 2011-12-30 18:37:49 - TZ=UTC TB --- 2011-12-30 18:37:49 - __MAKE_CONF=/dev/null TB --- 2011-12-30 18:37:49 - cd /src TB --- 2011-12-30 18:37:49 - /usr/bin/make -B buildkernel KERNCONF=KB920X >>> Kernel build for KB920X started on Fri Dec 30 18:37:49 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 [...] awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/kern/device_if.m -h echo "#define CFI_SUPPORT_STRATAFLASH 1" > opt_cfi.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/obj/arm.arm/src/sys/KB920X -std=iso9899:1999 /src/sys/modules/cfi/../../dev/cfi/cfi_bus_fdt.c /src/sys/modules/cfi/../../dev/cfi/cfi_bus_ixp4xx.c /src/sys/modules/cfi/../../dev/cfi/cfi_core.c /src/sys/modules/cfi/../../dev/cfi/cfi_dev.c In file included from /src/sys/modules/cfi/../../dev/cfi/cfi_bus_fdt.c:43: @/dev/ofw/ofw_bus.h:36:24: error: ofw_bus_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /src/sys/modules/cfi. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/arm.arm/src/sys/KB920X. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-12-30 18:38:43 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-12-30 18:38:43 - ERROR: failed to build KB920X kernel TB --- 2011-12-30 18:38:43 - 4426.73 user 1081.31 system 5922.80 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 01:00:10 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 642861065673; Sat, 31 Dec 2011 01:00:10 +0000 (UTC) (envelope-from jsa.bsd@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id EE0958FC0A; Sat, 31 Dec 2011 01:00:09 +0000 (UTC) Received: by qabg14 with SMTP id g14so11310884qab.13 for ; Fri, 30 Dec 2011 17:00:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=LOczgU8iCsvby9iRHVqVCoetZQhA6vt2PqgpgLtQ/gQ=; b=LPRiBp+O8u0imWdXwCWnhzROTPG/AFEK+R0fBTZQyWsigCiMSMuFb2Ygwx1hbYZ27z ijX84znySPF8UkMsAwL+5TRpRDdPsp9pkpoMmzKHfvnt//PHc7Hg1S9g3scLAISrb1QW sZm3jCtqtbJhYqUkQubRl6kyfyLeAb/U8N63I= Received: by 10.224.205.134 with SMTP id fq6mr48931973qab.99.1325293208981; Fri, 30 Dec 2011 17:00:08 -0800 (PST) Received: from pazuzu.wickedmachine.net ([76.5.145.121]) by mx.google.com with ESMTPS id cf18sm24628626qab.9.2011.12.30.17.00.07 (version=SSLv3 cipher=OTHER); Fri, 30 Dec 2011 17:00:07 -0800 (PST) Sender: "Joseph S. Atkinson" Message-ID: <4EFE5E96.6080202@FreeBSD.org> Date: Fri, 30 Dec 2011 20:00:06 -0500 From: "Joseph S. Atkinson" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111224 Thunderbird/9.0 MIME-Version: 1.0 To: Tijl Coosemans References: <4EFC0127.6030301@FreeBSD.org> <4EFC5487.3080709@orange.fr> <201112301413.32750.tijl@coosemans.org> In-Reply-To: <201112301413.32750.tijl@coosemans.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Alexander Motin , freebsd-current@freebsd.org Subject: Re: CD Access in 9.x and -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 01:00:10 -0000 On 12/30/2011 08:13, Tijl Coosemans wrote: > On Thursday 29 December 2011 12:52:39 Claude Buisson wrote: >> On 12/29/2011 07:41, Garrett Cooper wrote: >>> On Wed, Dec 28, 2011 at 9:56 PM, Joseph S. Atkinson wrote: >>>> I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the >>>> issue of cdda:// access. >>>> >>>> I can confirm this issues, but don't know enough about driver access to fix >>>> this myself. Doug Barton reports that cdcontrol(1) doesn't work for him, and >>>> mplayer and audactiy also display issues running as non-root. >>>> >>>> Under 9.0-RC3 r228843, I get these errors on boot with no disc present in >>>> /dev/cd0 at all. >>>> >>>> (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 >>>> 00 >>>> (pass1:ahcich2:0:0:0): CAM status: ATA Status Error >>>> (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) >>>> (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 >>>> >>>> These ports are fairly popular, but the problems may not lie exclusively >>>> with their assumptions about FreeBSD. I am running 10.0 on another machine >>>> specifically to test changes under src/sys/cam. >>>> >>>> I am worried that with the actual 9.0-RELEASE on the horizon, users will >>>> find show stopping problems using their disc drives. >>> >>> Try having users merge r228808 and r228847. If that works, then I >>> would press re@ produce another RC that fixes this. >>> Thanks, >>> -Garrett >>> >>> PS This is coming from a user that was annoyed by this gap with the >>> ATA_CAM code. >> >> As the submitter of ports/162190, I would firstly ask: >> >> Is the problem corrected by r228808 and r228847 in 10.0-CURRENT ? >> >> If not merging to 9.0 is useless. >> >> If yes I could test. > > There are 3 methods to access audio CDs. > - if your drive is connected to your sound card you can use the drive's > built-in audio support (if present). (used by cdcontrol) > - read raw audio data via the CAM layer. (used by cdparanoia) > - read raw audio data via the cd(4) driver. (used by vlc, libcdio?) > > The first two should work. The last one has now been fixed in CURRENT, > but programs using that method also seem to use CDRIOCSETBLOCKSIZE > ioctl that cd doesn't implement. The driver already knows the correct > block size though, so it seems safe to ignore the error. With the > attached patch vlc works for me. You sir, are a godsend. Tested this on 10.0-CURRENT and it worked. Now to get some form of this into VLC 1.2.0. It's likely too late to get the MFC needed, so possibly errata. From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 02:24:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8174106566C; Sat, 31 Dec 2011 02:24:03 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id 891998FC17; Sat, 31 Dec 2011 02:24:03 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LX100700QO23400@smtpauth2.wiscmail.wisc.edu>; Fri, 30 Dec 2011 20:24:02 -0600 (CST) Received: from comporellon.tachypleus.net ([unknown] [76.210.61.211]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LX100KM3QO1M210@smtpauth2.wiscmail.wisc.edu>; Fri, 30 Dec 2011 20:24:02 -0600 (CST) Date: Fri, 30 Dec 2011 20:24:00 -0600 From: Nathan Whitehorn In-reply-to: <201112291504.43430.jhb@freebsd.org> To: John Baldwin Message-id: <4EFE7240.1030602@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.61.211 X-Spam-PmxInfo: Server=avs-11, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.12.31.21217, SenderIP=76.210.61.211 References: <4EF904F2.4020109@FreeBSD.org> <4EFCC59E.8050508@freebsd.org> <201112291504.43430.jhb@freebsd.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111113 Thunderbird/8.0 Cc: Warren Block , freebsd-current@freebsd.org Subject: Re: Removal of sysinstall from HEAD and lack of a post-install configuration tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 02:24:03 -0000 On 12/29/11 14:04, John Baldwin wrote: > On Thursday, December 29, 2011 2:55:10 pm Nathan Whitehorn wrote: >> On 12/29/11 10:52, Warren Block wrote: >>> On Thu, 29 Dec 2011, John Baldwin wrote: >>>> A way to select from available partition types (UFS, boot, swap, ZFS, >>>> etc.) >>>> rather than requiring the user to remember the 'freebsd-xxx' string >>>> would be >>>> one improvement. >>> There are PRs for that and several other common suggestions: >>> >>> http://www.freebsd.org/cgi/query-pr-summary.cgi?&text=bsdinstall >> The problem with, say, a dropdown menu is that libdialog doesn't provide >> a combination dropdown-and-text-entry window. The only alternative would >> be to split partition creation into two screens (first a list of types, >> and later a thing to set it up). That has the disadvantage of requiring >> two screens, or a third if you want alternate types. > sysinstall just popped up a new modal dialog with a menu to pick the partition > type. Would something like that work in bsdinstall? > It would. I was hoping to avoid extra dialogs and keystrokes, but it's easy to do. -Nathan From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 08:18:54 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A191D1065672 for ; Sat, 31 Dec 2011 08:18:54 +0000 (UTC) (envelope-from aconnolly08@yahoo.co.jp) Received: from web100409.mail.kks.yahoo.co.jp (web100409.mail.kks.yahoo.co.jp [183.79.28.111]) by mx1.freebsd.org (Postfix) with SMTP id 24FBB8FC1D for ; Sat, 31 Dec 2011 08:18:53 +0000 (UTC) Received: (qmail 60513 invoked by uid 60001); 31 Dec 2011 07:52:12 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.jp; s=yj20110701; t=1325317932; bh=shXv76qkzq/HRiz8Jo8EfnZUZa6pX5QNlOyjnieIank=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=vx0OuCVOIVBXZVt0Dcvmjf3QQS14gBw5iayb1OC7BFPFDyRf8P6RDLEL4QgQt2lG9txNw+FWsFP/rOXndbf+lD5FbuLkxeqwL4A7tCR2ul+/DpxXAeucPJJs+l1erGabMhFeW9A4gpmswHBQ5Z7aAS7v0ueSWw5AcTWbE80wsp4= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=rEx972s3zxNReh/njyiuvi7sZlvsGSz/5BHzP/H0uALJt3l1vMAEE9IFk4wU4mzg7GivqfPtsXHLW+ElYfsKulfcewE3TDG7Xyuv+KKB1kikwEbTapYww7gUt0wxdLle+FsbStWXW12qD1dCC76z5TovZUjSgxRE20RgoAvUwXc=; Message-ID: <519544.57923.qm@web100409.mail.kks.yahoo.co.jp> X-YMail-OSG: Thsq.gcVM1m.BQvX9okdw2l0pw1GpRw5BQW5Cot_LoKCamIlGGXcEKWWqZgfR.APjYbrpiLaBXOXLvuJ_mp09j5PLzaTqMWev5BEhY5wJipUrUV89plQVEjvpvBlMwG.b1.AQWv0ewC2EVEGZw9XWjzDBfFfzQ5EJeu.yw1IGzDPbmB9PJCVzLOch3Cwlqk3m26GaI2i6EY_Nxb7fLoYYbPm7uPT_PHliygtEmJjTxn2YEfZnGnGQDBwF5DE3Ds9eKBCpT.fUUT7YQ-- Received: from [220.208.243.194] by web100409.mail.kks.yahoo.co.jp via HTTP; Sat, 31 Dec 2011 16:52:12 JST X-Mailer: YahooMailClassic/6.0.19_42 YahooMailWebService/0.7.289.12_42 Date: Sat, 31 Dec 2011 16:52:12 +0900 (JST) From: To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: atkbdc broken on current ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 08:18:54 -0000 I've installed 9.0-RC3 on an Acer Aspir One net book and with acpi enabled = atkbdc (and atkbd) are not loaded at all. I can use a usb keyboard with no = problems, but once I've selected my boot options the integrated keyboard st= ops responding. The fix mentioned in this thread does not address my proble= m. =20 Any suggestions as to what steps I should try next? From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 12:00:40 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22A7C10657B1 for ; Sat, 31 Dec 2011 12:00:40 +0000 (UTC) (envelope-from coco@executive-computing.de) Received: from mail.moehre.org (mail.moehre.org [195.96.35.7]) by mx1.freebsd.org (Postfix) with ESMTP id C6EE88FC0A for ; Sat, 31 Dec 2011 12:00:39 +0000 (UTC) Received: from mail.moehre.org (unknown [195.96.35.7]) by mail.moehre.org (Postfix) with ESMTP id AB1708B1423 for ; Sat, 31 Dec 2011 12:44:27 +0100 (CET) X-Spam-Flag: NO X-Spam-Score: -100.964 X-Spam-Level: X-Spam-Status: No, score=-100.964 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, AWL=0.036, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mail.moehre.org ([195.96.35.7]) by mail.moehre.org (mail.moehre.org [195.96.35.7]) (amavisd-new, port 10024) with ESMTP id WU2LcSenYGbz for ; Sat, 31 Dec 2011 12:44:26 +0100 (CET) Received: from [192.168.100.30] (p54B0C0C1.dip.t-dialin.net [84.176.192.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: coco@executive-computing.de) by mail.moehre.org (Postfix) with ESMTPSA id ED9068B141C for ; Sat, 31 Dec 2011 12:44:25 +0100 (CET) Message-ID: <4EFEF589.2030304@executive-computing.de> Date: Sat, 31 Dec 2011 12:44:09 +0100 From: Marco Steinbach User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="------------010203070200050604080102" Subject: [cft] Small patch for calendar(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 12:00:40 -0000 This is a multi-part message in MIME format. --------------010203070200050604080102 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Hi, for a while now, calendar(1) seems to have forgotten how to handle what the man page describes as: 'A month without a day matches the first of that month.' A notable result of this is, that the output of 'calendar -f /usr/share/calendar/calendar.all' is always headed by 'Unprocessed' error messages. The attached patch tries to help calendar(1) remember how to do this as is described in the man page. Since I'm not an avid calendar(1) user, I'd very much like others to review and try out the patch, before I go pester commiters by opening a PR. MfG CoCo --------------010203070200050604080102 Content-Type: text/plain; name="calendar.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="calendar.patch" --- src/usr.bin/calendar/parsedata.c.orig 2011-12-31 11:36:40.000000000 +0100 +++ src/usr.bin/calendar/parsedata.c 2011-12-31 11:57:55.000000000 +0100 @@ -174,11 +174,22 @@ } if (isonlydigits(date, 1)) { /* Assume month number only */ - *flags |= F_MONTH; + *flags |= (F_MONTH | F_DAYOFMONTH); + *idayofmonth = 1; *imonth = (int)strtol(date, (char **)NULL, 10); strcpy(month, getmonthname(*imonth)); return(1); } + if ((checkmonth(date, &len, &offset, &pmonth) != 0)) { + /* Assume month name only */ + *flags |= (F_MONTH | F_DAYOFMONTH); + *idayofmonth = 1; + *imonth = offset; + strcpy(month, getmonthname(*imonth)); + return(1); + } + + return (0); } } --------------010203070200050604080102-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 12:50:22 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 580C11065672 for ; Sat, 31 Dec 2011 12:50:22 +0000 (UTC) (envelope-from martin@sugioarto.com) Received: from mailserv.regfish.com (mailserv.regfish.com [79.140.61.33]) by mx1.freebsd.org (Postfix) with ESMTP id A0C7C8FC0A for ; Sat, 31 Dec 2011 12:50:21 +0000 (UTC) Received: (qmail 15816 invoked from network); 31 Dec 2011 12:50:20 -0000 Received: from pd9ec0bd9.dip0.t-ipconnect.de (HELO yuni.sugioarto.com) (46959-0001@[217.236.11.217]) (envelope-sender ) by mailserv.regfish.com (qmail-ldap-1.03) with SMTP for ; 31 Dec 2011 12:50:20 -0000 Received: from zelda.sugioarto.com (zelda.sugioarto.com [192.168.0.12]) by yuni.sugioarto.com (Postfix) with ESMTP id 0B4E71BAC57; Sat, 31 Dec 2011 13:50:19 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sugioarto.com; s=mail; t=1325335819; bh=p3CFmrtnAg7i32kpjmuOjVDEGtb7yuWmZ5t2eIMoOdA=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: Mime-Version:Content-Type; b=WgztZNQhYUI7zX+EYZk+H2KfPHl1Pa+tWnuaZL5TqIGNEH66aCHSxpZtHoAjB0geK QskO6uoLboyt3gfN+TNa6Tg24HXva2ZjAtCoiIjGu0lbwDtvoRlaFck/gS+85oN+uU I9WHwEATczpqmFf5oVh5BdHDkvvSUoxNci/cTDU4= Date: Sat, 31 Dec 2011 13:50:14 +0100 From: Martin Sugioarto To: mckusick@FreeBSD.org Message-ID: <20111231135014.6708e678@zelda.sugioarto.com> In-Reply-To: <20110911105417.073a5300@zelda.sugioarto.com> References: <20110911105417.073a5300@zelda.sugioarto.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/ngR6W1+UOI9g.+6BPZR3sYB"; protocol="application/pgp-signature" Cc: freebsd-current@freebsd.org Subject: Re: dump cannot do incremental backups when device name is too long X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 12:50:22 -0000 --Sig_/ngR6W1+UOI9g.+6BPZR3sYB Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sun, 11 Sep 2011 10:54:17 +0200 schrieb Martin Sugioarto : > Synopsis: [patch] dump(8) cannot do incremental backups when device > name is too long >=20 > State-Changed-From-To: open->patched > State-Changed-By: mckusick > State-Changed-When: Fri Oct 21 22:49:35 UTC 2011 > State-Changed-Why:=20 > A patch has been applied to head. > It will be MFC'ed after appropriate burnin time. >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D160678 Hi all, can someone add this patch (not my version, but the one Mr McKusick posted) to the future release branch? I tested it for a long time now and didn't have any problems. Thank you. -- Martin --Sig_/ngR6W1+UOI9g.+6BPZR3sYB Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQIcBAEBAgAGBQJO/wUKAAoJEF8wvLx/5p/7hKsP/2SDV+YWhfikgJni4BZhL2Hj 21FdjxSjSiyNpuCwtFsEf0GFsODr8Gvu7+Ua6t/hwO+ERgarPr+4TkPCHiEmMh3k VcgohgjiLgktCuEUUVHEE9PO33e3qUkSqiK/oNjachBksC9u7MbNb1J5+ahTPkF3 +Hl+VmzgJQGp8VoRM/2N45iUMx6WkUQt96pGqBQJhtbwzuIRjoLAjcK8A1GEAlIT XHjF9YTCMuHojexrQ9YSH9R/rf0ONjCHg63uRMAauL2kPf0ju41vMrLQRTxQTt1F BDvGuxCjcfo+BLN46g8aIfKSYLHQ2AbppgVoh3MjL+kxcSiD1a+Ot6PSSFlZJSGt bjxXo0MaF17+Afp4EteqLnEUFWrUEhlEFr3UU9v/wlQlq4/2NC/N41RaYYqV49lK mTyHAZyLNonp/Q34wPefrYzrjLRiVcs+V6gx+wrY8+L7u4Q7FQT78hA1Ah5XBphJ zLaMn1RslmxX2koterym6ztEk+31ZscgKbzMSfH2P6XZMsf5t7Z5WLbte6Bz1M4V HfP2F20b67IYTigYLhR8f/12Ql2ok1RxGoYhH84DSMapzy9NN1L9a41Cn2upDABB B95aaxeI6rKwMZ+6RCUURJ0nxs9esygeuZF27/5mlUeMfTPNMEK7w/eO65tgK2Pb 1I30TBlpLUKMh1WBQyNV =rR0V -----END PGP SIGNATURE----- --Sig_/ngR6W1+UOI9g.+6BPZR3sYB-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 17:29:47 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4599A106566B for ; Sat, 31 Dec 2011 17:29:47 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) by mx1.freebsd.org (Postfix) with ESMTP id 07BBF8FC0A for ; Sat, 31 Dec 2011 17:29:44 +0000 (UTC) Received: (qmail 15825 invoked by uid 89); 31 Dec 2011 17:05:29 -0000 Received: from unknown (HELO ?192.168.0.18?) (danallen46@airwired.net@66.29.174.6) by mail.utahbroadband.com with ESMTPA; 31 Dec 2011 17:05:29 -0000 From: Dan Allen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sat, 31 Dec 2011 10:03:02 -0700 Message-Id: <038588ED-E0E0-46F6-8E28-1926FBE28825@airwired.net> To: freebsd-current@freebsd.org Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) X-Mailman-Approved-At: Sat, 31 Dec 2011 17:47:02 +0000 Subject: ACPI broke going from 8 to 9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 17:29:47 -0000 I just upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9. The = machine no longer boots. However, if I put hint.acpi.0.disabled=3D1 in /boot/loader.conf then the machine runs fine. With RELENG_8 the = machine had no loader.conf, and the power button worked on my desktop = machine. Now with ACPI disabled my power button does not work. I have = found that the machine hangs at boot during a scan of the PCI bus, but = if I disable that (hw.acpi.disable=3Dpci) then the machine cannot find a = boot drive. So I have lost functionality that worked fine in BSD 8. Thoughts? Suggestions? Thanks, Dan Allen From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 18:40:17 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6027E106564A for ; Sat, 31 Dec 2011 18:40:17 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 26E4D8FC12 for ; Sat, 31 Dec 2011 18:40:17 +0000 (UTC) Received: by mail-tul01m020-f182.google.com with SMTP id wd18so16593762obb.13 for ; Sat, 31 Dec 2011 10:40:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=a60fW/wMGIARBe9bTTZpfTaxTFt/Y7VhpATGPC+TgWI=; b=QdeHsJVqw0wIo2DZ4Bhg/Gd5SMu7gOhpdlh0UymOD/HISv/XgolXA7c2/Vnv3he64k D+35oBIKNCtc3Xzfmrz5klALarguiVvyh8Hoas0DBo8PMdaGYLaZaZ5bFSNTrUXIdFaY 8gwBkXu36mmWI6vhjPp0bw2oftLYyX4e7S3R0= MIME-Version: 1.0 Received: by 10.182.159.70 with SMTP id xa6mr37582885obb.1.1325356817034; Sat, 31 Dec 2011 10:40:17 -0800 (PST) Received: by 10.182.152.6 with HTTP; Sat, 31 Dec 2011 10:40:17 -0800 (PST) In-Reply-To: <038588ED-E0E0-46F6-8E28-1926FBE28825@airwired.net> References: <038588ED-E0E0-46F6-8E28-1926FBE28825@airwired.net> Date: Sat, 31 Dec 2011 10:40:17 -0800 Message-ID: From: Garrett Cooper To: Dan Allen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: ACPI broke going from 8 to 9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 18:40:17 -0000 On Sat, Dec 31, 2011 at 9:03 AM, Dan Allen wrote: > I just upgraded my Dell OptiPlex GX270 from RELENG_8 to RELENG_9. =A0The = machine no longer boots. =A0However, if I put > > =A0hint.acpi.0.disabled=3D1 > > in /boot/loader.conf then the machine runs fine. =A0With RELENG_8 the mac= hine had no loader.conf, and the power button worked on my desktop machine.= =A0Now with ACPI disabled my power button does not work. =A0I have found t= hat the machine hangs at boot during a scan of the PCI bus, but if I disabl= e that (hw.acpi.disable=3Dpci) then the machine cannot find a boot drive. > > So I have lost functionality that worked fine in BSD 8. > > Thoughts? =A0Suggestions? Is your Optiplex running the latest BIOS firmware? Thanks! -Garrett From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 19:16:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D01A106566B for ; Sat, 31 Dec 2011 19:16:29 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id C63468FC0A for ; Sat, 31 Dec 2011 19:16:28 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so16607892obb.13 for ; Sat, 31 Dec 2011 11:16:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=J8xDeSwboaXxjFANJmyid02IBeHQ+/B87/+ld4BQPJg=; b=B8WNVpb20O/TT+zWLk+J+0CvwMNw8YOx5AKDpxPLepUyHCbqK2Ozfa5+NywBTXz0hf gPWhImlQuYbznZzG5fuceZUqwKZXgyj8sS9ZxG8B4xF+IES/psqaE/kBe2XWpcjKg919 cnO9wJKtbv91wfqgS3vRvrd89akBB+LPsbF1A= MIME-Version: 1.0 Received: by 10.182.193.99 with SMTP id hn3mr37260873obc.61.1325358988255; Sat, 31 Dec 2011 11:16:28 -0800 (PST) Received: by 10.182.152.6 with HTTP; Sat, 31 Dec 2011 11:16:28 -0800 (PST) In-Reply-To: <70F3E6A6-762E-4C4F-B517-C386304DF85F@airwired.net> References: <038588ED-E0E0-46F6-8E28-1926FBE28825@airwired.net> <70F3E6A6-762E-4C4F-B517-C386304DF85F@airwired.net> Date: Sat, 31 Dec 2011 11:16:28 -0800 Message-ID: From: Garrett Cooper To: Dan Allen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: ACPI broke going from 8 to 9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 19:16:29 -0000 On Sat, Dec 31, 2011 at 10:56 AM, Dan Allen wrote= : > > On 31 Dec 2011, at 11:40 AM, Garrett Cooper wrote: > >> Is your Optiplex running the latest BIOS firmware? > > My Dell OptiPlex GX270 was running BIOS A06, but I found that there was a= n A07. =A0So I installed A07 hoping that would do the trick, but it still p= rints: > > =A0pci0: on pcib0 > > and then hangs. Ok. The GX270 is pretty old, so this is probably a stretch but is there an ACPI toggle / 'conformance' option in the BIOS? My guess is that the machine is 1.0/1.1 spec, not 2.0 spec. -Garrett From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 18:56:56 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84424106566B for ; Sat, 31 Dec 2011 18:56:56 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) by mx1.freebsd.org (Postfix) with ESMTP id 459FA8FC16 for ; Sat, 31 Dec 2011 18:56:56 +0000 (UTC) Received: (qmail 5039 invoked by uid 89); 31 Dec 2011 18:59:22 -0000 Received: from unknown (HELO ?192.168.0.18?) (danallen46@airwired.net@66.29.174.6) by mail.utahbroadband.com with ESMTPA; 31 Dec 2011 18:59:22 -0000 Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: Dan Allen In-Reply-To: Date: Sat, 31 Dec 2011 11:56:53 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <70F3E6A6-762E-4C4F-B517-C386304DF85F@airwired.net> References: <038588ED-E0E0-46F6-8E28-1926FBE28825@airwired.net> To: Garrett Cooper X-Mailer: Apple Mail (2.1251.1) X-Mailman-Approved-At: Sat, 31 Dec 2011 19:18:10 +0000 Cc: freebsd-current@freebsd.org Subject: Re: ACPI broke going from 8 to 9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 18:56:56 -0000 On 31 Dec 2011, at 11:40 AM, Garrett Cooper wrote: > Is your Optiplex running the latest BIOS firmware? My Dell OptiPlex GX270 was running BIOS A06, but I found that there was = an A07. So I installed A07 hoping that would do the trick, but it still = prints: pci0: on pcib0 and then hangs. Dan From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 19:25:53 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 601C2106564A for ; Sat, 31 Dec 2011 19:25:53 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id E8B408FC13 for ; Sat, 31 Dec 2011 19:25:52 +0000 (UTC) Received: by wibhr1 with SMTP id hr1so13993804wib.13 for ; Sat, 31 Dec 2011 11:25:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=A02mTfJ/Ccdz7VU0ICXwuOx6DYOhlMJF1cGiA22+zDk=; b=T6Oh97EFz9VFbgZZJVH4HesdTMpi/5qi7G3nfi9F/TOfE/N+s4SI/gAjC08QZuZ4iw q8Tj9+7hOy50kMY0gHoBacLUJJeVHo1XeDfu6R0krv5FtwlXJz89FJ3flQId3uwU9xQA vdVuBQrgBRPA18QsH8YIN6QsOtBdhGrHmSgS0= MIME-Version: 1.0 Received: by 10.216.209.99 with SMTP id r77mr23904306weo.25.1325359552012; Sat, 31 Dec 2011 11:25:52 -0800 (PST) Received: by 10.180.84.105 with HTTP; Sat, 31 Dec 2011 11:25:51 -0800 (PST) In-Reply-To: <201112292137.33189.olevole@olevole.ru> References: <201112292137.33189.olevole@olevole.ru> Date: Sat, 31 Dec 2011 14:25:51 -0500 Message-ID: From: Ryan Stone To: Oleg Ginzburg Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: segfault from php/freebsd/dtrace X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 19:25:53 -0000 On Thu, Dec 29, 2011 at 12:37 PM, Oleg Ginzburg wrote: > Hi maillist, > > I try to use dtrace + php/dtrace on the freebsd. In certain cases ive get > Segmentation fault and don't understand what of subsystem has a problem. Yes, Userland DTrace is unfortunately still very experimental at this point. I've got a list of at least 10 outstanding bugs that I hope to start addressing early in the new year. In your case, dtrace(1) and/or libproc does not clean up after itself properly in the case of an error. I'm not entirely sure what is causing the segfault in php, though. Which version are you running? The output of uname -a would be helpful. From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 19:25:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB351106566C for ; Sat, 31 Dec 2011 19:25:03 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) by mx1.freebsd.org (Postfix) with ESMTP id 9352B8FC0C for ; Sat, 31 Dec 2011 19:25:03 +0000 (UTC) Received: (qmail 18677 invoked by uid 89); 31 Dec 2011 19:27:30 -0000 Received: from unknown (HELO ?192.168.0.18?) (danallen46@airwired.net@66.29.174.6) by mail.utahbroadband.com with ESMTPA; 31 Dec 2011 19:27:30 -0000 Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: Dan Allen In-Reply-To: Date: Sat, 31 Dec 2011 12:25:01 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <8DF650FE-CE0D-4DA4-901C-B19269464F9C@airwired.net> References: <038588ED-E0E0-46F6-8E28-1926FBE28825@airwired.net> <70F3E6A6-762E-4C4F-B517-C386304DF85F@airwired.net> To: Garrett Cooper X-Mailer: Apple Mail (2.1251.1) X-Mailman-Approved-At: Sat, 31 Dec 2011 19:33:05 +0000 Cc: freebsd-current@freebsd.org Subject: Re: ACPI broke going from 8 to 9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 19:25:03 -0000 On 31 Dec 2011, at 12:16 PM, Garrett Cooper wrote: > Ok. The GX270 is pretty old, so this is probably a stretch but is > there an ACPI toggle / 'conformance' option in the BIOS? My guess is > that the machine is 1.0/1.1 spec, not 2.0 spec. > -Garrett No, there is no such option. I have been through all of the settings in = the new BIOS and tried a variety of things, but nothing seems to work. Thanks for your help. It sounds like I am out of luck. Dan From owner-freebsd-current@FreeBSD.ORG Sat Dec 31 19:34:22 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D9BB106564A for ; Sat, 31 Dec 2011 19:34:22 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 012908FC1B for ; Sat, 31 Dec 2011 19:34:21 +0000 (UTC) Received: by obbwd18 with SMTP id wd18so16614587obb.13 for ; Sat, 31 Dec 2011 11:34:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=g2WMIKBrIExXXXMJb1txCrXIs/+B/AhQC+vuKYPGZBU=; b=bxKZrVrOVmkDhfp5psFZZxojA5hI1LGrak63fsCpbFWAPGpba8fCCVpMjFqPmCwsID KsmVrpXXZEaLInkRuwwuXe+OI1FzzI+71AHIwNWtUrp+izdOIEwxYKYAo7WlC+H+qJLw J9mcdySMWaoDlKCpX4+MO0SOUC4NCq4yu2ifw= MIME-Version: 1.0 Received: by 10.182.159.70 with SMTP id xa6mr37670039obb.1.1325360061245; Sat, 31 Dec 2011 11:34:21 -0800 (PST) Received: by 10.182.152.6 with HTTP; Sat, 31 Dec 2011 11:34:21 -0800 (PST) In-Reply-To: <8DF650FE-CE0D-4DA4-901C-B19269464F9C@airwired.net> References: <038588ED-E0E0-46F6-8E28-1926FBE28825@airwired.net> <70F3E6A6-762E-4C4F-B517-C386304DF85F@airwired.net> <8DF650FE-CE0D-4DA4-901C-B19269464F9C@airwired.net> Date: Sat, 31 Dec 2011 11:34:21 -0800 Message-ID: From: Garrett Cooper To: Dan Allen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: ACPI broke going from 8 to 9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 19:34:22 -0000 On Sat, Dec 31, 2011 at 11:25 AM, Dan Allen wrote= : > > On 31 Dec 2011, at 12:16 PM, Garrett Cooper wrote: > >> Ok. The GX270 is pretty old, so this is probably a stretch but is >> there an ACPI toggle / 'conformance' option in the BIOS? My guess is >> that the machine is 1.0/1.1 spec, not 2.0 spec. >> -Garrett > > No, there is no such option. =A0I have been through all of the settings i= n the new BIOS and tried a variety of things, but nothing seems to work. > > Thanks for your help. =A0It sounds like I am out of luck. Not yet. Add 'nooptions NEW_PCIB' to your KERNCONF, recompile, and try booting the new kernel. See if this works. Thanks! -Garrett