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)
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
users' modifications loss [1].
* Use the situation to rename files/patch-ac to files/patch-doc_Makefile.in
according to /usr/ports/Tools/scripts/splitpatch.pl convention.
Inspired by: ports/110512 [1]
Submitted by: Alexander Logvinov <ports@logvinov.com> [1]
PR: 87592
Submitted by: Phil Oleson <oz@nixil.net>
Approved by: sf (maintainer timeout, 2 days approved by so@)
Security: CAN-2005-3185, http://secunia.com/advisories/17192/
devel/wget starts to lag behind the releases of wget.
At least with a development version we are able to figure
out when it is stable enough to ftp/wget updated.
Add CONFLICTS to ftp/wget/Makefile
PR: ports/61155
Submitted by: Edwin Groothuis <edwin@mavetju.org>
- fix .netrc parsing bug
- fix 2GB limitation
- re-add IPv6 capability
- fix SEGV with special url line
check debian/changelog for more detail.
o replace /usr/local with ${PREFIX} in wgetrc and info.
PR: 38824 reported 2GB limitation
Obtained from: Debian GNU/Linux
its absence. Further investigation lead me to the answer, it depends
on perl. wget.1 has been built with pod2man which is of course a part
of perl5 port now in -CURRENT.
add USE_PERL5 and resurrect MAN1 for this port.
Thanks to: vanilla
- switch devel/gettext (0.11.1) on, installing full package
- flip devel/gettext-old (0.10.35) to installing only static binaries
with a "-old" suffix -- gettext-old will have its deorbit burn
sequence initiated just after 4.6-RELEASE
- fix up ports for the new world order
Reviewed by: portmgr
IPv6 capability has been lost. Please use wget+ipv6 instead.
as zh_TW.po is distributed in Big5, we no longer requires iconv hack.
zh_TW message tested by: clive
the explanation I've received:
"msgfmt-new can handle UTF-8 .po, but cant' convert it into big5 .po.
wget links against legacy gettext libraries, which simply lets garbage
in and out, doesnt' know what it produces."
Bump PORTREVISION.
Submitted by: Clive Lin <clive@tongi.org>
