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.
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.
From submitter:
- Remove an outdated comment in the Makefile.
- Fix MASTER_SITES.
- Switch from ancient math/libgmp-freebsd to math/libgmp4, the former
hardly compiles on architectures other/newer than i386 and alpha.
Tested on i386 and sparc64.
Submitted by: marius@alchemy.franken.de
---snip---
- Revert the partially enabled building and usage of the libgmp version
shipping with ssh introduced with the upgrade to 1.2.33. For -current
depend on math/libgmp-freebsd and use the libgmp in the base system
for -stable like this port did before. This fixes compilation on
-current and turns of the annoying errors when the configure of the
ssh-enclosed libgmp tests the optimisations using the wrong assembler-
syntax on 4-stable. The later causes configure to hang on 3-stable.
- Don't define 'REALLY_WANT_SSH=1' in the Makefile else the FORBIDDEN
for FreeBSD systems shipping with OpenSSH in the base-distribution and
not defining 'REALLY_WANT_SSH' is useless. This was also broken with
the last commit.
Tested on 5.0-current, 4-stable and 3-stable.
---snip---
Submitted by: marius@alchemy.franken.de
in the wrong order). Fix this, and bump PORTREVISION again. The window
was only a few minutes, but this won't disrupt things, and someone may
have updated in that window given the prominence of the problem.
Obtained from: Matt Power <mhpower@BOS.BINDVIEW.COM> via Bugtraq
the more restrictive SSH2 license), deprecate this port in favour of
OpenSSH as a parting shot (still allow people to build by setting an
environment variable) and remove myself as maintainer since I don't
have any interest in maintaining it.
About the only thing this port does which OpenSSH can't do well is
Kerberized logins..once that is working properly in OpenSSH I'm planning
to nuke the port.
stopping the server.
Martti's submission did not include -h, which I added because if I had
added the scripts the way he submitted them, the server wouldn't be
started on startup.
PR: 10196
Submitted by: Martti Kuparinen <martti.kuparinen@ericsson.com>
Reviewed by: kris (partially)
No response: maintainers (PR opened February 22, 1999)
With latest -current configure fails:
checking getaddrinfo bug... buggy
Fatal: You must get working getaddrinfo() function.
or you can specify "--disable-ipv6".
be added. This is done to support the build on pre 4.0 machines with
the KAME IPv6 stack installed. It has been verified to build+work
with both 4.0 and 3.4+kame.
Org. patch Submitted By: Munechika SUMIKAWA <sumikawa@ebina.hitachi.co.jp>
