From owner-freebsd-arch@FreeBSD.ORG Sun May 20 21:23:22 2012 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66469106566C; Sun, 20 May 2012 21:23:22 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id A8B968FC0A; Sun, 20 May 2012 21:23:20 +0000 (UTC) Received: from rack1.digiware.nl (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 374B7153434; Sun, 20 May 2012 23:23:19 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYAuxt_kkDkO; Sun, 20 May 2012 23:23:18 +0200 (CEST) Received: from [192.168.10.10] (vaio [192.168.10.10]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.digiware.nl (Postfix) with ESMTPSA id B7373153433; Sun, 20 May 2012 23:23:18 +0200 (CEST) Message-ID: <4FB960CC.4090607@digiware.nl> Date: Sun, 20 May 2012 23:23:24 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Warner Losh References: <20120513220646.GA12826@stack.nl> <4FB0CF88.5010309@FreeBSD.org> <3D895644-0BA5-44F7-AC8F-07323729C1AA@bsdimp.com> <88BE52F2-E8CC-455D-B7AF-CB1F876D48B7@bsdimp.com> In-Reply-To: <88BE52F2-E8CC-455D-B7AF-CB1F876D48B7@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Doug Barton , Jilles Tjoelker , freebsd-arch@FreeBSD.org Subject: Re: [patch] halt/reboot/shutdown cleanup X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2012 21:23:22 -0000 On 14-5-2012 16:52, Warner Losh wrote: > The distaste for extra, useless messages, I'll admit, is a > personality quirk that I share with many people. Well count me as one. Although my strongest peave withs this is in the periodical scripts which are too talkative for my taste. eg. I haven't used dump in 10 years, but still my reports have dump lines in them. --WjW From owner-freebsd-arch@FreeBSD.ORG Mon May 21 10:45:28 2012 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 68AA0106566B for ; Mon, 21 May 2012 10:45:28 +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 0026F8FC15 for ; Mon, 21 May 2012 10:45:27 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q4LAjK6R044780 for ; Mon, 21 May 2012 13:45:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5) with ESMTP id q4LAjItl014291 for ; Mon, 21 May 2012 13:45:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q4LAjIbv014290 for arch@freebsd.org; Mon, 21 May 2012 13:45:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 21 May 2012 13:45:18 +0300 From: Konstantin Belousov To: arch@freebsd.org Message-ID: <20120521104518.GU2358@deviant.kiev.zoral.com.ua> References: <20120203193719.GB3283@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i6eMXvFBn1dR7Tww" Content-Disposition: inline In-Reply-To: <20120203193719.GB3283@deviant.kiev.zoral.com.ua> 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=-4.0 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: Subject: Re: Prefaulting for i/o buffers X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 10:45:28 -0000 --i6eMXvFBn1dR7Tww Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 03, 2012 at 09:37:19PM +0200, Konstantin Belousov wrote: > FreeBSD I/O infrastructure has well known issue with deadlock caused > by vnode lock order reversal when buffers supplied to read(2) or > write(2) syscalls are backed by mmaped file. >=20 > I previously published the patches to convert i/o path to use VMIO, > based on the Jeff Roberson proposal, see > http://wiki.freebsd.org/VM6. As a side effect, the VM6 fixed the > deadlock. Since that work is very intrusive and did not got any > follow-up, it get stalled. >=20 > Below is very lightweight patch which only goal is to fix deadlock in > the least intrusive way. This is possible after FreeBSD got the > vm_fault_quick_hold_pages(9) and vm_fault_disable_pagefaults(9) KPIs. > http://people.freebsd.org/~kib/misc/vm1.3.patch >=20 > Theory of operation is described in the patched sys/kern/vfs_vnops.c, > see preamble comment for vn_io_fault(). The patch borrows the > rangelocks implementation from VM6, which was discussed and improved > together with Attilio Rao. >=20 > I was not able to reproduce the deadlock in the targeted test running > for several hours, while stock HEAD deadlocks in the first iteration. >=20 > Below is the benchmark for the worst-case situation for the patched > system, reading 1 byte from a file in a loop. The value is the time in > seconds to execute read(2) for single byte and lseek back to the start > of the file. The loop is executed 100,000,000 times. Machine has > 3.4Ghz Core i7 2600K and used HEAD@230866 with debugging options > turned off. >=20 > As you see, the rangelock overhead for the worst (but uncontented) > case is less then 10%. >=20 > x stock-1-byte.txt > + vm1-1-byte.txt > +------------------------------------------------------------------------= --+ > |xx = ++| > |xxx += ++| > ||A |= A|| > +------------------------------------------------------------------------= --+ > N Min Max Median Avg Stdd= ev > x 5 1.063206e-06 1.065569e-06 1.064172e-06 1.064109e-06 9.8031959e-= 10 > + 5 1.167145e-06 1.170244e-06 1.168939e-06 1.1690444e-06 1.2477022e-= 09 > Difference at 95.0% confidence > 1.04935e-07 +/- 1.63638e-09 > 9.86134% +/- 0.153779% > (Student's t, pooled s =3D 1.122e-09) >=20 I am reviving the thread. Since the original publication of the patch, it got quite intensive reviews and testing from several people, which I appreciate very much. The tagline for the commit would include Reviewed by: attilio, mdf, pjd, rmacklem (nfs client bits) Tested by: pho, flo, Gustau P?rez The latest version of the patch is at http://people.freebsd.org/~kib/misc/vm1.13.patch The main change comparing with the previous publically discussed version is the handling of the user buffers after vm_fault_quick_hold_pages(). I did uiomove() over the region in the previous patch, but apparently VM does not guarantee that corresponding pte entries are not removed, or writeable access is kept. So new version of the patch uses uiomove_fromphys() to avoid touching the usermode buffer, and operates on the hold pages. I shall note that the issue was never observed in real life. This requires trivial modifications of the filesystem code, namely the replacement of uiomove() with new helper function vn_io_fault_uiomove() which handles the details for hold pages access transparently for the filesystem. Again, comments and testers are welcomed. I consider the patch ready to be committed. --i6eMXvFBn1dR7Tww Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk+6HL4ACgkQC3+MBN1Mb4ihsACgxmsOVO9aLgH8r3xG2VjhD7dm 70EAoNs9r6LPmsatQ1wLOa3BfYsPB/3a =Sfef -----END PGP SIGNATURE----- --i6eMXvFBn1dR7Tww-- From owner-freebsd-arch@FreeBSD.ORG Mon May 21 20:58:13 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 46FFA1065675 for ; Mon, 21 May 2012 20:58:13 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id AFB1D8FC18 for ; Mon, 21 May 2012 20:58:11 +0000 (UTC) Received: from aspire.rulingia.com (12.58.233.220.static.exetel.com.au [220.233.58.12]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q4LKrjMm077829 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 May 2012 06:53:52 +1000 (EST) (envelope-from peter@rulingia.com) Received: from aspire.rulingia.com (localhost [127.0.0.1]) by aspire.rulingia.com (8.14.5/8.14.5) with ESMTP id q4LKrUCk019400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 May 2012 06:53:33 +1000 (EST) (envelope-from peter@aspire.rulingia.com) Received: (from peter@localhost) by aspire.rulingia.com (8.14.5/8.14.5/Submit) id q4LKrSSv019399; Tue, 22 May 2012 06:53:28 +1000 (EST) (envelope-from peter) Date: Tue, 22 May 2012 06:53:26 +1000 From: Peter Jeremy To: Willem Jan Withagen Message-ID: <20120521205326.GA2675@aspire.rulingia.com> References: <20120513220646.GA12826@stack.nl> <4FB0CF88.5010309@FreeBSD.org> <3D895644-0BA5-44F7-AC8F-07323729C1AA@bsdimp.com> <88BE52F2-E8CC-455D-B7AF-CB1F876D48B7@bsdimp.com> <4FB960CC.4090607@digiware.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <4FB960CC.4090607@digiware.nl> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-arch@freebsd.org Subject: Re: [patch] halt/reboot/shutdown cleanup X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 20:58:13 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [My vote on the halt/reboot/shutdown issue is that halt(8) & reboot(8) should just be wrappers around reboot(2) and shutdown(8) should clean up and run the rc.d shutdown scripts - but maybe I'm showing my age] On 2012-May-20 23:23:24 +0200, Willem Jan Withagen wrote: >Although my strongest peave withs this is in the periodical scripts >which are too talkative for my taste. You can control much of that via /etc/periodic.conf - see /etc/defaults/periodic.conf for details. >eg. I haven't used dump in 10 years, but still my reports have dump >lines in them. You probably still have a non-empty /etc/dumpdates. Unfortunately, you can't separately control the "df -h" and "dump W" output[1] but an empty /etc/dumpdates will reduce it to one line. [1] I think we're getting to the point where 400.status-disks should be split into 2. dump(8) is becoming increasingly less relevant. --=20 Peter Jeremy --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk+6q0YACgkQ/opHv/APuIfu5gCeNCUOuk1NwF11epfxzq0TJcou vwMAn2Ct9UxvIT+jO7TRL7rVqTZq2KG1 =YP0w -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From owner-freebsd-arch@FreeBSD.ORG Tue May 22 14:50:09 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 72CA21065672 for ; Tue, 22 May 2012 14:50:09 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id 044138FC0A for ; Tue, 22 May 2012 14:50:08 +0000 (UTC) Received: from rack1.digiware.nl (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id D2E5D153434; Tue, 22 May 2012 16:50:07 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NRH7ZYfEPaZa; Tue, 22 May 2012 16:50:07 +0200 (CEST) Received: from [192.168.10.67] (opteron [192.168.10.67]) by mail.digiware.nl (Postfix) with ESMTP id 10455153436; Tue, 22 May 2012 16:50:07 +0200 (CEST) Message-ID: <4FBBA79E.4020303@digiware.nl> Date: Tue, 22 May 2012 16:50:06 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Peter Jeremy References: <20120513220646.GA12826@stack.nl> <4FB0CF88.5010309@FreeBSD.org> <3D895644-0BA5-44F7-AC8F-07323729C1AA@bsdimp.com> <88BE52F2-E8CC-455D-B7AF-CB1F876D48B7@bsdimp.com> <4FB960CC.4090607@digiware.nl> <20120521205326.GA2675@aspire.rulingia.com> In-Reply-To: <20120521205326.GA2675@aspire.rulingia.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: [patch] halt/reboot/shutdown cleanup X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2012 14:50:09 -0000 On 2012-05-21 22:53, Peter Jeremy wrote: > [My vote on the halt/reboot/shutdown issue is that halt(8) & reboot(8) > should just be wrappers around reboot(2) and shutdown(8) should clean > up and run the rc.d shutdown scripts - but maybe I'm showing my age] > > On 2012-May-20 23:23:24 +0200, Willem Jan Withagen wrote: >> Although my strongest peave withs this is in the periodical scripts >> which are too talkative for my taste. > > You can control much of that via /etc/periodic.conf - see > /etc/defaults/periodic.conf for details. > >> eg. I haven't used dump in 10 years, but still my reports have dump >> lines in them. > > You probably still have a non-empty /etc/dumpdates. Unfortunately, > you can't separately control the "df -h" and "dump W" output[1] but > an empty /etc/dumpdates will reduce it to one line. > > [1] I think we're getting to the point where 400.status-disks should > be split into 2. dump(8) is becoming increasingly less relevant. > I used these as obvious examples, but there are much more.... But that would be stealing the thread. --WjW From owner-freebsd-arch@FreeBSD.ORG Fri May 25 16:02:47 2012 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6439D1065674 for ; Fri, 25 May 2012 16:02:47 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) by mx1.freebsd.org (Postfix) with ESMTP id 34B808FC19 for ; Fri, 25 May 2012 16:02:47 +0000 (UTC) Received: from [209.249.190.124] (port=52208 helo=punk.neville-neil.com.neville-neil.com) by vps.hungerhost.com with esmtpa (Exim 4.77) (envelope-from ) id 1SXwyR-0008T5-Te for arch@freebsd.org; Fri, 25 May 2012 12:02:44 -0400 Date: Fri, 25 May 2012 12:03:40 -0400 Message-ID: <86wr40tfhf.wl%gnn@neville-neil.com> From: gnn@freebsd.org To: arch@freebsd.org User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/23.4 (amd64-portbld-freebsd10.0) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com Cc: Subject: RFC: A trial io provider for DTrace... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2012 16:02:47 -0000 Howdy, I have just put up the first patch that can give you something similar to the io provider in DTrace. The patch is against HEAD of about a week ago. You can find the patch here: freebsd.org: http://people.freebsd.org/~gnn/dtio_provider.diff Note that you need to create a src/sys/modules/dtrace/dtio/ directory for this patch, since patch doesn't seem to create directories for me. The arguments are not exactly the same as in Solaris, for instance I don't yet support the fileinfo_t, but, you can get to the devstat and bio structures via args[0] and args[1] respectively. Here is an example of it working: dtrace -n 'io:::start /args[0] != 0/{ trace(args[0]->bio_bcount)}' Remember you need to be root to use DTrace. I need to clean this up and get the translators working properly before I can check this in. Also, note that this patch doesn't catch all I/O, but should get most of it, as it's hooked into the devstat system. I will be adding manual pages for the internals of DTrace to our section 9, as well as, hopefully, writing up a wiki page on how to add your own kernel providers. Comments welcome. Best, George From owner-freebsd-arch@FreeBSD.ORG Sat May 26 23:55:15 2012 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E4C6106564A for ; Sat, 26 May 2012 23:55:15 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 835428FC14 for ; Sat, 26 May 2012 23:55:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q4QNtFqI093995 for ; Sat, 26 May 2012 23:55:15 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q4QNtFua093994 for arch@freebsd.org; Sat, 26 May 2012 23:55:15 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Sun, 27 May 2012 01:55:10 +0200 From: Baptiste Daroussin To: arch@FreeBSD.org Message-ID: <20120526235510.GB90668@ithaqua.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4bRzO86E/ozDv8r1" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: switch tounconditionnal boostrapping while to build the tree X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 May 2012 23:55:15 -0000 --4bRzO86E/ozDv8r1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi After I replace yacc(1) by byacc(1) on current, we discovered than now it is impossible to build 9 on current, because byacc(1) is not 100% backward compatible with our yacc(1). this is because building a boostrap yacc(1) is conditionned on the version of the host that is building world. Looking at Makefile.inc1 I can see that lots of tools are conditionned like this. I think if we want to go to be able to cross build the tree (I rememb= er =66rom EuroBSDcon that this is something we want to do) then we need to rem= ove the conditions and always boostrap any tool necessary to be able to build the t= ree. so if no one care I'll remove the condition to boostrap at least yacc(1) and lex(1) on current, 9, 8 and 7. Would be great imho to do the same for any tools needed by the build system. regards, Bapt --4bRzO86E/ozDv8r1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk/BbV4ACgkQ8kTtMUmk6EyPtgCgiMeuxylDDQp2GcJmLcqf/ggb 3fUAn2wbcQd0UjB/rthSiH47n8zrl1XP =tBDi -----END PGP SIGNATURE----- --4bRzO86E/ozDv8r1--