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)
Get rid of the dlmalloc dependency on a recent FreeBSD versions (>= 700036)
since they provide malloc_usable_size().
PR: ports/120058 (with some modifications)
Submitted by: Dave Grochowski <malus.x@gmail.com>
graphics/xaralx-devel port because the icon and the executable are
installed under xaralx-devel.png and xaralx-devel respectively to
make it possible to have both xaralx and xaralx-devel installed.
* Add libtool dependency because configure.in mentions AC_PROG_LIBTOOL
which seems to be defined by libtool.m4 installed by libtool. This allows
us to drop the hack of removing it from configure.in
* Invoking "pkg-config --cflags atk fontconfig gdk-2.0 pango" is not
necessary anymore. Drop it.
* Invoke autoreconf with a hacked value of ACLOCAL environment variable
to make aclocal find gettext.m4 which is installed in /usr/local/aclocal/
but aclocal is searching /usr/local/aclocal19/. ade@ promised to fix this
soon
* Remove unnecessary changes to configure.in, they are not needed now
documentation and license files, icon, a .desktop file and examples.
* Switch from LOCALBASE to X11BASE since this is a true a X application
that needs to link against the X libraries and now installs .desktop
file and an icon.
Rename this ports to use the real vendor package name. The advantage of this
is to allow our users' keyword search works and easier for users to file the
Bugzilla report when they use our name of ports. Debian, Gentoo, NetBSD and
other OSs have the correct package name, but not in our ports tree.
My team, FreeBSD GNOME Team, have agreed with it.
As for other ports, chase the rename.
PR: ports/97985
Repocopy by: marcus
* Move all the hacks from the slave port (xaralx-devel) to the
master port (xaralx) because these are now common for both ports
* Switch both ports from .gz to .bz2 to save some resources
I think I will stick this port to the XaraLX recommended version which
is currently 0.4r798 and maybe create xaralx-devel port which will follow
the current (and possibly unstable) version of the software.
This is an old commercial Windows software which recently got
Open Source'd under GPL.
The open source/unix version is still in development and has a lot of
unimplemented features but it shows a great potential.
