HEADSUP: some new port breakages on 5.x (but not 6.x and 7.x)

[Mark Linimon]

Sometime in late July or early August, something changed in the
infrastructure that broke installation of these 4 ports -- but only
on 5.x.  The cause is still under investigation.  If anyone has any
ideas, please let me know.

mcl

----------  Forwarded Message  ----------

Subject: cvs commit: ports/databases/virtuoso Makefile 
ports/security/squidclam Makefile ports/www/havp Makefile 
ports/x11-drivers/xf86-video-openchrome Makefile
Date: Saturday 24 November 2007
From: Mark Linimon <linimon at freebsd.org>
To: ports-committers at freebsd.org, cvs-ports at freebsd.org, 
cvs-all at freebsd.org

linimon     2007-11-25 01:24:13 UTC

  FreeBSD ports repository

  Modified files:
    databases/virtuoso   Makefile 
    security/squidclam   Makefile 
    www/havp             Makefile 
    x11-drivers/xf86-video-openchrome Makefile 
  Log:
  Mark as broken on 5.x: fails to find pthread.h.
  
  Something in the infrastructure changed in the late July timeframe 
that
  actually caused this problem.  The only major thing at that time was 
the
  autoconf/libtool change, but I can't see how that could have caused 
this
  failure mode.  It only happens on 5.x; 6.x and 7.x are fine.
  
  Approved by:    portmgr (self)
  
  Revision  Changes    Path
  1.9       +7 -2      ports/databases/virtuoso/Makefile
  1.5       +5 -0      ports/security/squidclam/Makefile
  1.8       +4 -0      ports/www/havp/Makefile
  1.3       +1 -1      ports/x11-drivers/xf86-video-openchrome/Makefile

-------------------------------------------------------
-------------- next part --------------
linimon     2007-11-25 01:24:13 UTC

  FreeBSD ports repository

  Modified files:
    databases/virtuoso   Makefile 
    security/squidclam   Makefile 
    www/havp             Makefile 
    x11-drivers/xf86-video-openchrome Makefile 
  Log:
  Mark as broken on 5.x: fails to find pthread.h.
  
  Something in the infrastructure changed in the late July timeframe that
  actually caused this problem.  The only major thing at that time was the
  autoconf/libtool change, but I can't see how that could have caused this
  failure mode.  It only happens on 5.x; 6.x and 7.x are fine.
  
  Approved by:    portmgr (self)
  
  Revision  Changes    Path
  1.9       +7 -2      ports/databases/virtuoso/Makefile
  1.5       +5 -0      ports/security/squidclam/Makefile
  1.8       +4 -0      ports/www/havp/Makefile
  1.3       +1 -1      ports/x11-drivers/xf86-video-openchrome/Makefile