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_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)
- Remove FreeBSD 4.x code (USE_GCC=3.4+, USE_GETOPT_LONG and BROKEN).
- Use ARCH instead of MACHINE_ARCH for possible future cross-compilation
support.
- Add UBLIO option, which uses devel/libublio for greatly improved speed (when
reading an NTFS volume). Also print a warning when disabling UBLIO.
- Add pkg-message mentioning UBLIO and this port's limitations.
- Change mount.ntfs-fuse -> mount_ntfs-fuse manpage link and symlink to the
binary in /usr/sbin to allow using with 'mount -t ntfs-fuse' and in
/etc/fstab after mounting /usr.
- Add a note in pkg-descr about the fusefs driver and ntfs-3g split project.
- Add LOCK option to avoid access to the device while it's mounted.
PR: ports/116287
Submitted by: alepulver (myself)
Approved by: miwi, farrokhi (implicitly to miwi)
sysutils/fusefs-libs has been upgraded and ntfsprogs' FUSE based
fs driver (ntfsmount) doesn't compile against the new version.
The attached patch will make it compile against recent
sysutils/fusefs-libs versions (2.5.0, 2.5.1)
PR: ports/92568
Submitted by: Csaba Henk <csaba.henk@creo.hu>
- Add local patch to make FUSE support compile on FreeBSD [1].
- Force --enable-gnome-vfs when WITH_GNOMEVFS2 is set.
Asked by: Sergei Mozhaisky <technix@mediana.net.ua> [1]
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.
Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.
Preliminary documentation can be found at:
http://people.FreeBSD.org/~ade/autotools.txt
which is in the process of being SGMLized before introduction into the
Porters Handbook.
Light blue touch-paper. Run.
- Install the GnomeVFS module in ${X11BASE}, where GnomeVFS will look for it
- Use USE_GCC=3.4+ rather than USE_GCC=3.4
- Remove useless USE_CONFIGURE
- Fix the GnomeVFS spelling in the OPTIONS help
Submitted by: John Merryweather Cooper <john_m_cooper@yahoo.com> [1]
