> > 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. > > > > 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? > > 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. > > 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 >= 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? -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schul...@infidyne.com>' Key retrieval: Send an E-Mail to getpgp...@scode.org E-Mail: peter.schul...@infidyne.com Web: http://www.scode.org
pgpQFGtCh6McW.pgp
Description: PGP signature
