- Tighten COMMENT line and drop the article
- Fix the build against Clang and thus drop USE_GCC
- Remove PKGMESSAGE, it's set automatically
- Correctly pad ${CAT} ${PKGMESSAGE}
- Couple of minor fixes (LIB_DEPENDS, etc.)
Approved by: tabthorpe (maintainer)
- Update textproc/clucene to 2.3.3.4. Note this version is required by
recent LibreOffice.
- Remove textproc/clucene-contrib because it is now integrated into
textproc/clucene. [2]
- Mark textproc/p5-Lucene as broken. There is no dependent port and it was
only written for obsolete Lucene 0.9.x API. [3]
- Update deskutils/kdepim4 and deskutils/strigi to build with the new
CLucene port. [4]
- Update misc/bibletime and misc/sword to use new CLucene 2.3.x API. [5]
Approved by: clsung (maintainer timeout) [1]
Approved by: tj (maintainer) [2]
Approved by: perl [3]
Approved by: kde [4]
Approved by: tabthorpe (maintainer timeout) [5]
Obtained from: The SWORD Project [5]
rely on gcc. The patch uses the new USE_GCC=any code in Mk/bsd.gcc.mk to
accomplish this.
The ports chosen were ports that blocked 2 or more ports from building with
clang. (There are several hundred other ports that still fail to build with
clang, even with this patch. This is merely one step along the way.)
Those interested in fixing these ports with clang, and have clang as their
default compiler, can simply set FORCE_BASE_CC_FOR_TESTING=yes.
For those who have gcc as their default compiler, this change is believed
to cause no change.
Hat: portmgr
Tested with: multiple runs on amd64-8-exp-bcm and 9-exp-clang, with various
combinations of patch/no-patch and flag settings.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)
- remove USE_GCC=34+, this was an implied workaround for FreeBSD 4.X compatibility.
PR: ports/108941
Submitted by: Thomas Abthorpe <thomas@goodking.ca> (maintainer)
Bump PORTREVISION of all dependent ports.
Fix the build errors in the few ports that still use the long deprecated,
and now obsoleted, cURL options.
Thanks to everyone who took the time to look over the patch!
Discussed on: -ports
