[JunkMail] RE: Fixing -pthreads (Re: ports and -current)
Mark Woodson
mwoodson at sricrm.com
Tue Sep 23 13:41:38 PDT 2003
On Tuesday 23 September 2003 01:25 pm, Dan Naumov wrote:
> On Tue, 2003-09-23 at 23:13, Daniel Eischen wrote:
> > I understand that folks want to wave their hands and say "just
> > make -pthread work and do whatever it needs to".
>
> I am one of those folks as well. As an end-user, I am not
> interested in hacking around the source of 3rd-party applications
> that use -pthread when compiling them from source myself. Not in
> the slightest. This is BAD BAD BAD for usability.
I have to admit here that I know about -pthread only what I've been
following in this ongoing thread.
I'm an end user that's run into the recent changes in pthreads causing
breakage in ports (well one particular port, clamav). I was able to
figure out how to disable pthreads and hack the port to get it
compiled and running, but it was rather annoying. And having
followed questions for a few years, I can easily imagine the kind of
traffic that this behaviour will generate. While the notion of
knowlegeable folks being able to link in the thread library of choice
sounds nice, does it really make sense to break what will be expected
behaviour?
-Mark
More information about the freebsd-current
mailing list