Date: Mon, 6 Apr 2009 21:11:43 +0200 From: Peter Schuller <peter.schuller@infidyne.com> To: Vasil Dimov <vd@FreeBSD.ORG>, Coleman Kane <cokane@FreeBSD.ORG>, svn-src-head@FreeBSD.ORG, svn-src-all@FreeBSD.ORG, Sam Leffler <sam@FreeBSD.ORG>, src-committers@FreeBSD.ORG Subject: Re: svn commit: r189828 - in head: include sys/sys Message-ID: <20090406191142.GA79888@hyperion.scode.org> In-Reply-To: <20090406182419.GA62997@zim.MIT.EDU> References: <200903142010.n2EKAESF006945@svn.freebsd.org> <20090320140015.GA17645@hub.freebsd.org> <20090320153405.GA62675@zim.MIT.EDU> <49C3BCD4.4030605@freebsd.org> <1237567495.1993.2.camel@localhost> <20090327063251.GA95057@polejan.hw.v5d.org> <20090406164853.GA75904@hyperion.scode.org> <20090406182419.GA62997@zim.MIT.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
--vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > > I'm not the most knowledgable about the various POSIX/XSI > > compatibility defines and their expected results, but it seems pretty > > dangerous to me to flat-out #undef it. Who knows what else depends on > > those being set properly in any given application. > >=20 > > How about only doing it for a new enough OS release to at least avoid > > breaking older releases, and then communicate the problem upstream and > > hope for a better fix? >=20 > As I mentioned in an email to vd@ two weeks ago, the problem is > that GNU pth *already* has a bunch of insidious kludges to try to > prevent systems headers on various operating systems from > declaring symbols it wants to clobber. In particular, it defines > _PTHREAD_H, which hides pthread_kill() when pthread_kill() is > defined in pthread.h, but not when it is defined in signal.h. >=20 > The options are to either add yet another insidious kludge to GNU > pth such as the one you suggest, or to add a kludge to FreeBSD > specifically to support GNU pth in all its brokenness. I agreed to > try the latter if the former proved to be impractical. To be clear I'm not suggesting the kludge, but tested what vd@ asked for and suggested limiting the potential negative impact by limiting it to >=3D 8. I understand that it's an ugly solution either way, but I can't suggest one that isn't... Would it make sense to invent a kludge that is at least somewhat general in nature (__PTHREADS_INVISIBLE or something) which could possibly be adopted by other OS:es and decrease OS-specific hacks in pth? --=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@infidyne.com>' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAknaU+4ACgkQDNor2+l1i333lgCfQNyHDa47VRmirK3IuoAKZg+i B48AoKVx3lGi6H15ceTqf0VCNxdGQiBH =FcTB -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090406191142.GA79888>