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)
supports them. This is determined by running ``configure --help'' in
do-configure target and set the shell variable _LATE_CONFIGURE_ARGS
which is then passed to CONFIGURE_ARGS.
- Remove --mandir and --infodir in ports' Makefile where applicable
Few ports use REINPLACE_CMD to achieve the same effect, remove them too.
- Correct some manual pages location from PREFIX/man to MANPREFIX/man
- Define INFO_PATH where necessary
- Document that .info files are installed in a subdirectory relative to
PREFIX/INFO_PATH and slightly change add-plist-info to use INFO_PATH and
subdirectory detection.
PR: ports/111470
Approved by: portmgr
Discussed with: stas (Mk/*), gerald (info related stuffs)
Tested by: pointyhat exp run
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.
either IGNORE or BROKEN.
Since there seems to be some confusion, for the record:
BROKEN is reserved for ports that don't work. This will prevent
users from installing the port, but please note that
ports marked as BROKEN will still be built by bento
IGNORE is reserved for ports that should not be built for one
reason or another (including bento). Users and bento
will not build ports marked as IGNORE.
FORBIDDEN is reserved for security breakages only!!! Only mark a
port as FORBIDDEN if there is a security issue with the
port at the time.
Reviewed by: kris (portmgr)
2. Rewrote pkg-comment and pkg-descr files.
3. Marked pkg-plist file as not done.
4. Made do-build and do-install targets indicating that this port is
not at all ready to even be looked at. The repocopy was a placeholder
for when I can get to it.
