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)
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 versioned autotools are now strictly for building other ports in the tree.
Likewise, the gnu- autotools are for runtime dependencies for IDEs, and others,
where unmodified cross-platform capabilities are desired.
Take back maintainership. I'll be scouring the PR database shortly,
if I miss any, or someone beats me to it, please feel free to reassign
appropriately.
or interest to look after these things any more.
To whomever picks these up, I salute you. I'll reset the relevant
PRs to ports-bugs in a couple of weeks if no-one has taken over
maintainership.
Farewell, autotool hell.
of the autotools project to remove all but the latest versions of
libtool, autoconf, and automake, by 31st December 2004.
Note that autoconf259 and automake18 aren't yet accessible through the
relevant USE_* knobs, but will be as soon as bsd.autotools.mk comes into
existence.
list by bsd.port.mk insert anti foot-shooting device, which prevents
infinite fork loop when the user defines corresponding USE_XXX in global
make.conf, command line or environment.
Similar devices should probably be inserted into ports that might be inserted
into dependency list by others bsd.foo.mk files (bsd.ruby.mk, bsd.python.mk
and so on.)
since I'm doing most of the updating, and am working on a
port/Mk/bsd.<gnublah>.mk to move some cruft around.
Sponsored by: Mr. Smith and Mr. Wesson. :)
- Backout recent upgrade because it broke way too many ports;
- assign maintainership to portmgr@FreeBSD.org due to importancy of this port
to the overall ports infrastructure.
the inode numbers of files.
This should fix the "duplicated macros" error when aclocal is
invoked with `-I ${X11BASE}/share/aclocal' explicitly.
- Do not scan ${X11BASE}/share/aclocal if it does not exist. (Or it's
(a symlink to)* a directory)
This should fix the "no such directory" error when you build a non-X
port without X installed. (like on bento)
(ie: ${LOCALBASE}), but also ${X11BASE}/share/aclocal via an extra
patch and some configure-time substitution
Discussed on: ports (quite a while back)
Original disgusting hack by: ade
Suggested improvements by: asami
Reworked patch by: ade
