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)
integrates Data, Services, and Business Processes across the enterprise.
Its unique product architecture enables it to delivery traditionally
distinct server functionality, within a single product offering,
along the following lines:
* Data Management & Integration (SQL, XML and EII)
* Application Integration (Web Services & SOA)
* Process Management & Integration (BPEL)
* Collaboration and Network Effects
WWW: http://virtuoso.openlinksw.com/
- Hosting modules (python and ruby) will be added as slave ports later.
- Mono hosting is broken on FreeBSD
- Perl hosting is broken on FreeBSD
(perl* ports are built without -Dusemultiplicity)
- PHP4/5 hosting is broken on FreeBSD (php* ports do not install libphp).
- JDBC driver will be added as a slave port later.
