From owner-svn-src-head@FreeBSD.ORG Sun Apr 12 11:46:57 2009 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E9B3106564A; Sun, 12 Apr 2009 11:46:57 +0000 (UTC) (envelope-from rse@engelschall.com) Received: from visp1.engelschall.com (visp1.engelschall.com [194.97.152.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1D5548FC12; Sun, 12 Apr 2009 11:46:57 +0000 (UTC) (envelope-from rse@engelschall.com) Received: by visp1.engelschall.com (Postfix, from userid 21100) id B253F19818; Sun, 12 Apr 2009 13:30:07 +0200 (CEST) Received: by en1.engelschall.com (Postfix, from userid 10000) id 11CC66DC0C; Sun, 12 Apr 2009 13:22:07 +0200 (CEST) Date: Sun, 12 Apr 2009 13:22:07 +0200 From: "Ralf S. Engelschall" To: David Schultz Message-ID: <20090412112207.GA45902@engelschall.com> References: <200904111657.n3BGvpsC092703@svn.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200904111657.n3BGvpsC092703@svn.freebsd.org> Organization: FreeBSD User-Agent: Mutt/1.5.19 OpenPKG/CURRENT (2009-01-05) Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r190943 - head/include X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ralf S. Engelschall" List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2009 11:46:57 -0000 On Sat, Apr 11, 2009, David Schultz wrote: > [...] > GNU Pth has some fragile kludges that were broken by r189828. > I've discussed this with the Pth maintainer and no clear solution > has emerged on the ports side of things, so for now, hack around > the issue in signal.h. > [...] We really should not apply any special workarounds in our FreeBSD code base for third-party libraries like GNU Pth. I've personally still not investigated on this issue of the GNU Pth port, but I'm sure the problem _can_ be solved from within the ports tree or even in my own upstream GNU Pth code base. We at least certainly don't need any hacks in the FreeBSD . I recommend to backout this change. I will check the GNU Pth ports issue we have here and perhaps even apply a workaround upstream... -- rse@FreeBSD.org Ralf S. Engelschall FreeBSD.org/~rse rse@engelschall.com FreeBSD committer www.engelschall.com