Re: Fixing -pthreads (Re: ports and -current)

On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote:
> OK, here's what we can do to fix this:
> 
> 1) Put back -pthread in -current so all the ports don't fail
> 
> 2) I will build a full set of -current packages with the -pthread
> error still in place, to determine the list of packages that need to
> be fixed (in fact I already have this, see
> http://dosirak.kr.freebsd.org/errorlogs).
> 
> 3) You, John Birrell, and whoever else is interested in fixing these
> ports can work on them at your own pace without disrupting life for
> the rest of the users.  Once they're all fixed, we can turn the error
> back on or make it a NOP or do whatever else is decided to be
> appropriate.
> 
> 4) It is likely that steps 2 and 3 will need to be iterated several
> times, because there are dozens of ports that need to be fixed, and
> many of them are hiding other ports that depend on them and also need
> to be fixed.

I don't know if there is much point to #1 at this point since
it's been gone for about 2 weeks now.  #2/3/4 sounds fine to me.

In the meantime KF is working on a patch to properly support
PTHREAD_LIBS in KDE's configure scripts.  We plan to commit it
when the freeze lifts, pending PR #55325.

I suggest that people not build ports on -CURRENT for a few weeks
until things get sorted out, unless they're going to fix the
problems with specific ports.

Regards,
-- 
wca