-Update libtool and libltdl to 2.2.6a.
-Remove devel/libtool15 and devel/libltdl15.
-Fix ports build with libtool22/libltdl22.
-Bump ports that depend on libltdl22 due to shared library version change.
-Explain what to do update in the UPDATING.
It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop
and applications in the runtime.
With help: marcus and kwm
Pointyhat-exp: a few times by pav
Tested by: pgollucci, "Romain Tartière" <romain@blogreen.org>, and
a few MarcusCom CVS users. Also, I might have missed a few.
Repocopy by: marcus
Approved by: portmgr
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 useless USE_LIBTOOL along with the custom regex and replace it with a
patch;
- properly pass CONFIGURE_TARGET for this configure script generated by the
newest autoconf.
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
FWIW, checkout of these things took 5+hrs, staying on the local
.freebsd.org net w/o hitting the 'net at all.
As promised,
$ time cvs ci
real 67m51.701s
user 0m1.250s
sys 0m5.345s
of order includes--this version compiled on a 2.2.6 machine without
problems, though).
Rather than patch it, I cut a new release.
Problem #2 is:
> 1) Though the port depends on GDBM, the configure script does not find
> it; I got that to work by creating ad hoc symlinks for
> /usr/include/gdbm.h and /usr/lib/libgdbm.a --> for some reasons,
> /usr/local/include and /usr/local/lib are ignored (btw, any way I can do
> that "cleanly" for all ports?)
which I haven't touched. Since the standard gcc doesn't search
/usr/local/include and /usr/local/lib, it is neccesary to have
CFLAGS=-I/usr/local/include
LDFLAGS=-L/usr/local/lib
before configure succeeds, but I tried adding those lines to MAKE_ENV
and it didn't help configure (is there a CONFIGURE_ENV)?
Why doesn't it search those paths anyway? I looked at other ports which
require gdbm and they are no different, it seems they all have this problem,
or their makefiles have hardcoded /usr/local paths in them.
-josh
