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)
- move 1.0 obsoleted version to net/libnet10
net/libnet is latest Stable Version
net/libnet is latest Beta Version
- Fix all depended ports with a new DEPENDS scheme
- While I'm here fix security/yersinia build on 4.x
(getopt_long and ncurses issues)
PR: ports/85519 (based on)
Submitted by: Stas Yakovlev <stas.yakovlev_at_gmail.com>
- Removed dependency on automake and autoconf
- Use PKGNAMESUFFIX
- Use CONFLICTS to prevent installation over stable version
- Install examples and documentation
- Use DOCSDIR/EXAMPLESDIR
- Reword COMMENT and pkg-descr, add Author tag
PR: 54421
Submitted by: sergei
Approved by: maintainer timeout (5 months)
libnet-devel will maintain libnet-1.1.x. A limited number of ports currently
support or will require libnet-1.1.x in the future. The API is not backwards
compatible. Unfortunately many ports still require libnet-1.0.x and do not
support the new API (and may never support it). libnet-devel will fill the
gap until the API change settles out and 1.0.x is fully deprecated.
