I tested on -current/amd64 past the utmpx change and on
8.0-RELEASE-p2/i386 for the old code path.
Reviewed: Giorgos Keramidas (maintainer)
Approved: Pav Lucistnik (for portmgr)
Feature safe: yes
since the commit broke dependencies and the ports infrastructure
was not fully prepared (a new emacs/editors22 port is needed
for compatibility reasons);
. bump PORTEPOCH.
Reported by: Jan Henrik Sylvester <me at janh.de>, kostik
Pointy hat to: bsam (me)
Emacs 23 has a wide variety of new features, including:
* Improved Unicode support.
* Font rendering with Fontconfig and Xft.
* Support for using X displays and text terminals in one session,
and for running as a daemon.
* Support for multi-file commits in distributed version-control
systems (VC-dir).
* New modes and packages for viewing PDF and postscript files
(Doc-view mode), connecting to processes through D-Bus (dbus),
connecting to the GNU Privacy Guard (EasyPG), editing XML
documents (nXML mode), editing Ruby programs (Ruby mode), and more.
Detailed list is available at: http://www.gnu.org/software/emacs/NEWS.23.1
PR: ports/137956
Submitted by: Ashish SHUKLA <wahjava at gmail.com>
Approved by: keramida@ceid.upatras.gr (maintainer tineout, 19 days)
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)
- Remove USE_XLIB/USE_X_PREFIX/USE_XPM in favor of USE_XORG
- Remove X11BASE support in favor of LOCALBASE or PREFIX
- Use USE_LDCONFIG instead of INSTALLS_SHLIB
- Remove unneeded USE_GCC 3.4+
Thanks to all Helpers:
Dmitry Marakasov, Chess Griffin, beech@, dinoex, rafan, gahr,
ehaupt, nox, itetcu, flz, pav
PR: 116263
Tested on: pointyhat
Approved by: portmgr (pav)
This includes various enhancements and fixes, including a
serious bug caused by using gmalloc's allocation and free
functions and the system version of posix_memalign().
PR: ports/114993
Submitted by: Gardner Bell
Reviewed by: 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.
Note that emacs is run as part of the build, so it shows as a build
failure...
To explain (for maintainer's benefit):
Previously the linker would put the text segment in region 2 and the
data segment in region 3. This was changed for FreeBSD (due to me
sending a patch :-) to load the text segment in region 1 with the data
segment immediately following the text segment in the same region (or
subsequent regions of the text segment is larger than 2^61 bytes in
size -- fat chance :-)
So, the previous value of DATA_SEG_BITS (=0x6000000000000000, the
region base of the data segment prior to the binutils 2.15 import),
needed to be changed to match the current layout (=0x2000000000000000,
the region 1 base address).
Approved by: portmgr (krion -- thank!)
