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.
the libtoolX ports instead of the one included with each port. Ports that
set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of
the included version. To restore previous behavior, use the new macro,
USE_INC_LIBTOOL_VER. Both macros accept the same argument: a libtool version.
For example, to use the ports version of libtool-1.5, add the following to
your Makefile:
USE_LIBTOOL_VER= 15
To use the included version of libtool with extra hacks provided by
libtool-1.5, add the following to your Makefile:
USE_INC_LIBTOOL_VER= 15
With this change, ports that had to add additional libtool hacks to prevent
.la files from being installed or to fix certain threading issues can now
delete those hacks (after appropriate testing, of course).
PR: 63944
Based on work by:eik and marcus
Approved by: ade (autotools maintainer)
Tested by: kris on pointyhat
Bound to be hidden problems: You bet
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.
sysconf is not. This causes glib to try and malloc UINT_MAX bytes of memeory
which basically translates to -1 bytes. Sanity check the value returned by
sysconf (_SC_GETPW_R_SIZE_MAX) to see that it's really implemented. This
fixes an abort people started to see in Glib-based applications.
Reported by: Shin-ichi YOSHIMOTO <yosimoto@waishi.jp>
the old xxx-config files, remove the "12" suffix. This will allow people
building Glib and GTK+ ports by hand to do so without a lot of extra
hacking. Since these ports are so heavily used, the xxx12-config files
aren't removed completely, but rather symlinked to their xxx-config
counterparts.
PR: 39417
FreeBSD's dlopen(NULL, ...) doesn't return a handle useable for resolving
symbols in both the program itself and all modules it dlopen'ed. Instead,
when requested for a self handle return RTLD_DEFAULT, which seems closely
matches dlopen(NULL, ...) in Linux. Bump PORTREVISION.
Recommended update for all GNOME/GTK users.
Inspired by: John Merryweather Cooper <john_m_cooper@yahoo.com>
previous commit message to bsd.port.mk, which said INSTALL_SHLIBS. Boo.)
Line up the rhs of variable assignments nicely. Remove a couple of extra
whitespaces while I'm here.
Suggested by: sobomax
Overview of Changes in GTK+ 1.2.8:
* GNU Make 3.79 bug workaround
* FAQ and tutorial updates and improvements
* Miscellaneous bug fixes: CList, Calendar, rc-files, FontSelection
Overview of Changes in GLib 1.2.8:
* GArray zero initialization bug fixed
* Fix for upper bound calculation of formatted strings
* Improved GCC detection
* AIX dynamic modules fix to retrive symbols from shared libraries for the main
program.
* Miscellaneous other minor bug fixes
