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.
deficiency in orbit-python's Makefile structure: it's not sufficiently
inclusive w.r.t actually using *_CFLAGS generated by various test programs
called from its own configure script. Added a patch to fix this.
- (It's also not very good about using generated *_LIBS, which may cause
future problems.)
- No PORTREVISION bump; this is a build-time problem.
PR: 36278
Submitted by: Christopher Farley <chris@northernbrewer.com>
- Release notes:
- many new features
- improved stability
- improved memory usage - all known leaks fixed
- improved compliance with Python mapping specification
- CORBA exceptions overhauled
- object references implemented as class instances
- works better with GNOME IDLs
- etc.
