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)
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
- Remove USE_XLIB/USE_X_PREFIX/USE_XPM in favor of USE_XORG
- Remove X11BASE support in favor of LOCALBASE or PREFIX
- Use USE_LDCONFIG instead of INSTALLS_SHLIB
- Remove unneeded USE_GCC 3.4+
Thanks to all Helpers:
Dmitry Marakasov, Chess Griffin, beech@, dinoex, rafan, gahr,
ehaupt, nox, itetcu, flz, pav
PR: 116263
Tested on: pointyhat
Approved by: portmgr (pav)
driver by displaing NOTICE on pkg-message.
o Fix invalid compiling on amd64.
PR: ports/120783
Submitted and
Summraized by: Eygene Ryabinkin rea-fbsd a codelabs.ru
Dual-head doesn't work properly with this version but at least most
single-head setups will work correctly.
PR: ports/117726
Submitted by: Bernd Strauß
Discussed on: x11@
doesn't build there anyway. This is affecting the release builds.
This is a workaround: sparc64 video drivers probably need more exclusions.
Briefly discussed with: flz
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)
X.org 7.3 applied to the xorg-server port, so the special keys
of Sun USB keyboards can be used with the sun_usb XKB symbols
map and the LEDs of Sun RS232 keyboards work again.
Approved by: flz
breaks the build when XORG_COMPLETE is set. [1]
- Add VIDEO_EXCL, a list of mutually exclusive video drivers.
- Add openchrome to VIDEO_OFF.
Reported by: brian [1]
