2016-07-09 08:37:46 +02:00
|
|
|
# $NetBSD: Makefile,v 1.103 2016/07/09 06:38:05 wiz Exp $
|
2013-11-30 10:01:26 +01:00
|
|
|
#
|
|
|
|
|
# for major version updates, don't forget adding new links in
|
|
|
|
|
# mk/tools/automake.mk
|
1997-10-06 16:06:09 +02:00
|
|
|
|
Update to 1.15:
New in 1.15:
* Improvements and refactorings in the install-sh script:
- It has been modernized, and now makes the following assumptions
*unconditionally*:
(1) a working 'dirname' program is available;
(2) the ${var:-value} shell parameters substitution works;
(3) the "set -f" and "set +f" shell commands work, and, respectively,
disable and enable shell globbing.
- The script implements stricter error checking, and now it complains
and bails out if any of the following expectations is not met:
(1) the options -d and -t are never used together;
(2) the argument passed to option -t is a directory;
(3) if there are two or more SOURCEFILE arguments, the
DESTINATION argument must be a directory.
* Automake-generated testsuites:
- The default test-driver used by the Automake-generates testsuites
now appends the result and exit status of each "plain" test to the
associated log file (automake bug#11814).
- The perl implementation of the TAP testsuite driver is no longer
installed in the Automake's scripts directory, and is instead just
distributed as a "contrib" addition. There should be no reason to
use this implementation anyway in real packages, since the awk+shell
implementation of the TAP driver (which is documented in the manual)
is more portable and has feature parity with the perl implementation.
- The rule generating 'test-suite.log' no longer risk incurring in an
extra useless "make all" recursive invocation in some corner cases
(automake bug#16302).
* Distribution:
- Automake bug#18286: "make distcheck" could sometimes fail to detect
files missing from the distribution tarball, especially in those cases
where both the generated files and their dependencies are explicitly
in $(srcdir). An important example of this are *generated* makefile
fragments included at Automake time in Makefile.am; e.g.:
...
$(srcdir)/fragment.am: $(srcdir)/data.txt $(srcdir)/preproc.sh
cd $(srcdir) && $(SHELL) preproc.sh <data.txt >fragment.am
include $(srcdir)/fragment.am
...
If the use forgot to add data.txt and/or preproc.sh in the distribution
tarball, "make distcheck" would have erroneously succeeded! This issue
is now fixed.
- As a consequence of the previous change, "make distcheck" will run
using '$(distdir)/_build/sub' as the build directory, rather than
simply '$(distdir)/_build' (as it was the case for Automake 1.14 and
earlier). Consequently, the './configure' and 'make' invocations
issued by the distcheck recipe now have $(srcdir) equal to '../..',
rather than to just '..'. Dependent and similar variables (e.g.,
'$(top_srcdir)') are also changed accordingly.
Thus, Makefiles that made assumptions about the exact values of the
build and source directories used by "make distcheck" will have to
be adjusted. Notice that making such assumptions was a bad and
unsupported practice anyway, since the exact locations of those
directories should be considered implementation details, and we
reserve the right to change them at any time.
* Miscellaneous bugs fixed:
- The expansion of AM_INIT_AUTOMAKE ends once again with a trailing
newline (bug#16841). Regression introduced in Automake 1.14.
- We no longer risk to use '$ac_aux_dir' before it's defined (see
automake bug#15981). Bug introduced in Automake 1.14.
- The code used to detect whether the currently used make is GNU make
or not (relying on the private macro 'am__is_gnu_make') no longer
risks causing "Arg list too long" for projects using automatic
dependency tracking and having a ton of source files (bug#18744).
- Automake tries to offer a more deterministic output for generated
Makefiles, in the face of the newly-introduced randomization for
hash keys order in Perl 5.18.
- In older Automake versions, if a user defined one single Makefile
fragment (say 'foo.am') to be included via Automake includes in
his main Makefile.am, and defined a custom make rule to generate that
file from other data, Automake used to spuriously complain with some
message like "... overrides Automake target '$(srcdir)/foo.am".
This bug is now fixed.
- The user can now extend the special .PRECIOUS target, the same way
he could already do with the .MAKE .and .PHONY targets.
- Some confusing typos have been fixed in the manual and in few warning
messages (automake bug#16827 and bug#16997).
2015-01-08 17:40:50 +01:00
|
|
|
DISTNAME= automake-1.15
|
2016-07-09 08:37:46 +02:00
|
|
|
PKGREVISION= 4
|
1997-10-06 16:06:09 +02:00
|
|
|
CATEGORIES= devel
|
Update to 1.8:
* New features
- Default source file names in the absence of a _SOURCES declaration
are made by removing any target extension before appending `.c', so
to make the libtool module `foo.la' from `foo.c', you only need to
do this:
lib_LTLIBRARIES = foo.la
foo_la_LDFLAGS = -module
For backward compatibility, foo_la.c will be used instead of
foo.c if this file exists or is the explicit target of a rule.
However -Wobsolete will warn about this deprecated naming.
- AR's `cru' flags are now set in a global ARFLAGS variable instead
of being hard-coded in each $(AR) invocation, so they can be
substituted from configure.ac. This has been requested by people
dealing with non-POSIX ar implementations.
- New warning option: -Woverride. This will warn about any user
target or variable definitions which override Automake
definitions.
- Texinfo rules back up and restore info files when makeinfo fails.
- Texinfo rules now support the `html' target.
Running this requires Texinfo 4.0 or greater.
`html' is a new recursive target, so if your package mixes
hand-crafted `Makefile.in's with Automake-generated
`Makefile.in's, you should adjust the former to support (or
ignore) this target so that `make html' recurses successfully. If
you had a custom `html' rule in your `Makefile.am', it's better to
rename it as `html-local', otherwise your rule will override
Automake's new rule (you can check that by running `automake
-Woverride') and that will stop the recursion to subdirectories.
Last but not least, this `html' rule is declared PHONY, even when
overridden. Fortunately, it appears that few packages use a
non-PHONY `html' rule.
- Any file which is m4_included from configure.ac will appear as a
configure and Makefile.in dependency, and will be automatically
distributed.
- The rules for rebuilding Makefiles and Makefile.ins will now
rebuild all Makefiles and all Makefile.ins at once when one of
configure's dependencies has changed. This is considerably faster
than previous implementations, where config.status and automake
were run separately in each directory (this still happens when you
change a Makefile.am locally, without touching configure.ac or
friends). Doing this also solves a longstanding issue: these
rebuild rules failed to work when adding new directories to the
tree, forcing you to run automake manually.
- For similar reasons, the rules to rebuild configure,
config.status, and aclocal.m4 are now defined in all directories.
Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
should better define them in all directories. This is easily done
using an AC_SUBST (make sure you prefix these dependencies with
$(top_srcdir) since this variable will appear at different
levels of the build tree).
- aclocal will now use `m4_include' instead of copying local m4
files into aclocal.m4. (Local m4 files are those you ship with
your project, other files will be copied as usual.)
Because m4_included files are automatically distributed, it means
for most projects there is no point in EXTRA_DISTing the list of
m4 files which are used. (You can probably get rid of
m4/Makefile.am if you had one.)
- aclocal will avoid touching aclocal.m4 when possible, so that
Autom4te's cache isn't needlessly invalidated. This behavior can
be switched off with the new `--force' option.
- aclocal now uses Autoconf's --trace to detect macros which are
actually used and will no longer include unused macros simply
because they where mentioned. This was often the case for macros
called conditionally.
- New options no-dist and no-dist-gzip.
- compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
py-compile, and ylwrap, now all understand --version and --help.
- Automake will now recognize AC_CONFIG_LINKS so far as removing created
links as part of the distclean target and including source files in
distributions.
- AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
argument. The latter can be used to override the default behavior
(which is to abort).
- Automake will exit with $? = 63 on version mismatch. (So does
Autoconf 2.58) missing knows this, and in this case it will
emulate the tools as if they were absent. Because older versions
of Automake and Autoconf did not use this exit code, this change
will only be useful in projects generated with future versions of
these tools.
- When using AC_CONFIG_FILES with multiple input files, Automake
generates the first ".in" input file for which a ".am" exists.
(Former versions would try to use only the first input file.)
- lisp_DATA is now allowed. If you are using the empty ELCFILES
idiom to disable byte-compilation of lisp_LISP files, it is
recommended that you switch to using lisp_DATA. Note that
this is not strictly equivalent: lisp_DATA will install elisp
files even if emacs is not installed, while *_LISP do not
install anything unless emacs is found.
- Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
available. This selection is achieved through the Makefile
variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
`mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
`$(install_sh) -m 0755 -d'.
* Obsolete features
- Because `mkdir -p' is available on most platforms, and we can use
`install-sh -d' when it is not, the use of the mkinstalldirs
script is being phased out. `automake --add-missing' no longer
installs it, and if you remove mkinstalldirs from your package,
automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
Gettext 1.12.1 still requires mkinstalldirs. Fortunately
gettextize and autopoint will install it when needed. Automake
will continue to define the $(mkinstalldirs) and to distribute
mkinstalldirs when this script is in the source tree.
- AM_PROG_CC_STDC is now empty. The content of this macro was
merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
should adjust it to use $ac_cv_prog_cc_stdc instead. (This
renaming should be safe, even if you have to support several,
versions of Automake, because AC_PROG_CC defines this variable
since Autoconf 2.54.)
- Some users where using the undocumented ACLOCAL_M4_SOURCES
variable to override the aclocal.m4 dependencies computed
(inaccurately) by older versions of Automake. Because Automake
now tracks configure's m4 dependencies accurately (see m4_include
above), the use of ACLOCAL_M4_SOURCES should be considered
obsolete and will be flagged as such when running `automake
-Wobsolete'.
* Bug fixes
- Defining programs conditionally using Automake conditionals no
longer leads to a combinatorial explosion. The following
construct used to be troublesome when used with dozens of
conditions.
bin_PROGRAMS = a
if COND1
bin_PROGRAMS += a1
endif
if COND2
bin_PROGRAMS += a2
endif
if COND3
bin_PROGRAMS += a3
endif
...
Likewise for _SOURCES, _LDADD, and _LIBADD variables.
- Due to implementation constraints, previous versions of Automake
proscribed multiple conditional definitions of some variables
like bin_PROGRAMS:
if COND1
bin_PROGRAMS = a1
endif
if COND2
bin_PROGRAMS = a2
endif
All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
This restriction has been lifted, and these variables now
support multiple conditional definitions as do other variables.
- Cleanup the definitions of $(distdir) and $(top_distdir).
$(top_distdir) now points to the root of the distribution
directory created during `make dist', as it did in Automake 1.4,
not to the root of the build tree as it did in intervening
versions. Furthermore these two variables are now only defined in
the top level Makefile, and passed to sub-directories when running
`make dist'.
- The --no-force option now correctly checks the Makefile.in's
dependencies before deciding not to update it.
- Do not assume that make files are called Makefile in cleaning rules.
- Update .info files in the source tree, not in the build tree. This
is what the GNU Coding Standard recommend. Only Automake 1.7.x
used to update these files in the build tree (previous versions did
it in the source tree too), and it caused several problems, varying
from mere annoyance to portability issues.
- COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
when --add-missing and --force-missing are used. For backward
compatibility --add-missing will continue to install COPYING (in
`gnu' strictness) when none of these three files exist, but this
use is deprecated: you should better choose a license yourself and
install it once for all in your source tree (and in your code
management system).
- Fix ylwrap so that it does not overwrite header files that haven't
changed, as the inline rule already does.
- User-defined rules override automake-defined rules for the same
targets, even when rules do not have commands. This is not new
(and was documented), however some of the automake-generated
rules have escaped this principle in former Automake versions.
Rules for the following targets are affected by this fix:
clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
info, info-am, install-data-am, install-exec-am, install-info,
install-info-am, install-man, installcheck-am, maintainer-clean,
maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
ps, ps-am, uninstall-am, uninstall-info, uninstall-man
Practically it means that an attempt to supplement the dependencies
of some target, as in
clean: my-clean-rule
will now *silently override* the automake definition of the
rule for this target. Running `automake -Woverride' will diagnose
all such overriding definitions.
It should be noted that almost all these targets support a *-local
variant that is meant to supplement the automake-defined rule
(See node `Extending' in the manual). The above rule should
be rewritten as
clean-local: my-clean-rule
These *-local targets have been documented since at least
Automake 1.2, so you should not fear the change if you have
to support multiple automake versions.
* Miscellaneous
- The Automake manual is now distributed under the terms of the GNU FDL.
- Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
- core dumps are no longer removed by the cleaning rules. There are
at least three reasons for this:
1. These files should not be created by any build step,
so their removal do not fit any of the cleaning rules.
Actually, they may be precious to the developer.
2. If such file is created during a build, then it's clearly a
bug Automake should not hide. Not removing the file will
cause `make distcheck' to complain about its presence.
3. Operating systems have different naming conventions for
core dump files. A core file on one system might be a
completely legitimate data file on another system.
- RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
defined by Automake. This means that any definition in the
environment will be used, unless overridden in the Makefile.am or
on the command line. The old behavior, where these variables were
defined empty in each Makefile, can be obtained by AC_SUBSTing or
AC_ARG_VARing each variable from configure.ac.
- CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
documented. (The is not a new feature, these variables have
been there since at least Automake 1.4.)
2003-12-11 17:32:34 +01:00
|
|
|
MASTER_SITES= ${MASTER_SITE_GNU:=automake/} \
|
|
|
|
|
ftp://sources.redhat.com/pub/automake/
|
Update to 1.11.3:
New in 1.11.3:
* WARNING: Future backward-incompatibilities!
- The support for the "obscure" multilib feature has been deprecated,
and will be moved out of the automake core in the next major Automake
release (1.12).
- The support for ".log -> .html" conversion and the check-html and
recheck-html targets will be removed in the next major Automake
release (1.12).
- The obsolescent AM_WITH_REGEX macro has been deprecated (since the
GNU rx library has been decommissioned), and will be removed in the
next major Automake release (1.12).
- The `lzma' compression format for distribution archives has been
deprecated in favor of `xz' and `lzip', and will be removed in the
next major Automake release (1.12).
- The `--acdir' option of aclocal is deprecated, and will probably be
removed in the next major Automake release (1.12).
- The exact order in which the directories in the aclocal macro
search path are looked up is probably going to be changed in the
next Automake release (1.12).
- The Automake support for automatic de-ANSI-fication will be removed
in the next major Automake release (1.12).
- Starting from the next Automake release (1.12), warnings in the
`extra-portability' category will be enabled by `-Wall' (right now,
one has to use `-Wextra-portability' explicitly).
* Miscellaneous changes:
- Automake's own build system is more silent by default, making use of
the 'silent-rules' option.
- The master copy of the `gnupload' script is now maintained in gnulib,
not in automake.
- The `missing' script doesn't try to wrap calls to `tar' anymore.
- "make dist" doesn't wrap `tar' invocations with the `missing' script
anymore. Similarly, the obsolescent variable `$(AMTAR)' (which you
shouldn't be using BTW ;-) does not invoke the missing script anymore
to wrap tar, but simply invokes the `tar' program itself.
- "make dist" can now create lzip-compressed tarballs.
- In the Automake info documentation, the Top node and the nodes about
the invocation of the automake and aclocal programs have been renamed;
now, calling "info automake" will open the Top node, while calling
"info automake-invocation" and "info aclocal-invocation" will access
the nodes about the invocation of respectively automake and aclocal.
- Automake is now distributed as a gzip-compressed and an xz-compressed
tarball. Previously, bzip2 was used instead of xz.
- The last relics of Python 1.5 support have been removed from the
AM_PATH_PYTHON macro.
- For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
and adds them to the normal list of dependencies, but without
overwriting the foo_DEPENDENCIES variable, which is normally computed
by automake.
Bugs fixed in 1.11.3:
* Bugs introduced by 1.11.2:
- Automake now correctly recognizes the prefix/primary combination
`pkglibexec_SCRIPTS' as valid.
- The parallel-tests harness doesn't trip anymore on sed implementations
with stricter limits on the length of input lines (problem seen at
least on Solaris 8).
* Long-standing bugs:
- The "deleted header file problem" for *.am files is avoided by stub
rules. This allows `make' to trigger a rerun of `automake' also if
some previously needed `.am' file has been removed.
- The `silent-rules' option now generates working makefiles even
for the uncommon `make' implementations that do not support the
nested-variables extension to POSIX 2008. For such `make'
implementations, whether a build is silent is determined at
configure time, and cannot be overridden at make time with
`make V=0' or `make V=1'.
- Vala support now works better in VPATH setups.
New in 1.11.2:
* Changes to aclocal:
- The `--acdir' option is deprecated. Now you should use the new options
`--automake-acdir' and `--system-acdir' instead.
- The `ACLOCAL_PATH' environment variable is now interpreted as a
colon-separated list of additional directories to search after the
automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
and before the system acdir (by default ${prefix}/share/aclocal).
* Miscellaneous changes:
- The Automake support for automatic de-ANSI-fication has been
deprecated. It will probably be removed in the next major Automake
release (1.12).
- The `lzma' compression scheme and associated automake option `dist-lzma'
is obsoleted by `xz' and `dist-xz' due to upstream changes.
- You may adjust the compression options used in dist-xz and dist-bzip2.
The default is now merely -e for xz, but still -9 for bzip; you may
specify a different level via the XZ_OPT and BZIP2 envvars respectively.
E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
- The `compile' script now converts some options for MSVC for a better
user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
- The py-compile script now accepts empty arguments passed to the options
`--destdir' and `--basedir', and complains about unrecognized options.
Moreover, a non-option argument or a special `--' argument terminates
the list of options.
- A developer that needs to pass specific flags to configure at "make
distcheck" time can now, and indeed is advised to, do so by defining
the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
instead of the old DISTCHECK_CONFIGURE_FLAGS.
The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
user; still, the old Makefile.am files that used to define it will
still continue to work as before.
- New macro AM_PROG_AR that looks for an archiver and wraps it in the new
'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
This new macro is required for LIBRARIES and LTLIBRARIES when automake
is run with -Wextra-portability and -Werror.
- When using DejaGnu-based testsuites, the user can extend the `site.exp'
file generated by automake-provided rules by defining the special make
variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
- The `install-info' rule can now be instructed not to create/update
the `${infodir}/dir' file, by exporting the new environment variable
`AM_UPDATE_INFO_DIR' to the value "no".
Bugs fixed in 1.11.2:
* Bugs introduced by 1.11:
- The parallel-tests driver no longer produces erroneous results with
Tru64/OSF 5.1 sh upon unreadable log files.
- The `parallel-tests' test driver does not report spurious successes
when used with concurrent FreeBSD make (e.g., "make check -j3").
- When the parallel-tests driver is in use, automake now explicitly
rejects invalid entries and conditional contents in TEST_EXTENSIONS,
instead of issuing confusing and apparently unrelated error messages
(e.g., "non-POSIX variable name", "bad characters in variable name",
or "redefinition of TEST_EXTENSIONS), or even, in some situations,
silently producing broken `Makefile.in' files.
- The `silent-rules' option now truly silences all compile rules, even
when dependency tracking is disabled. Also, when `silent-rules' is
not used, `make' output no longer contains spurious backslash-only
lines, thus once again matching what Automake did before 1.11.
- The AM_COND_IF macro also works if the shell expression for the
conditional is no longer valid for the condition.
* Long-standing bugs:
- The order of Yacc and Lex flags is fixed to be consistent with other
languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
$(LFLAGS), so that the user variables override the developer variables.
- "make distcheck" now correctly complains also when "make uninstall"
leaves one and only one file installed in $(prefix).
- A "make uninstall" issued before a "make install", or after a mere
"make install-data" or a mere "make install-exec" does not spuriously
fail anymore.
- Automake now warns about more primary/directory invalid combinations,
such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
- Rules generated by Automake now try harder to not change any files when
`make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
Yacc source files and the rule to update config.h.
- Several scripts and the parallel-tests testsuite driver now exit with
the right exit status upon receiving a signal.
- A per-Makefile.am setting of -Werror does not erroneously carry over
to the handling of other Makefile.am files.
- The code for automatic dependency tracking works around a Solaris
make bug triggered by sources containing repeated slashes when the
`subdir-objects' option was used.
- The makedepend and hp depmodes now work better with VPATH builds.
- Java sources specified with check_JAVA are no longer compiled for
"make all", but only for "make check".
- An usage like "java_JAVA = foo.java" will now cause Automake to warn
and error out if `javadir' is undefined, instead of silently producing
a broken Makefile.in.
- aclocal and automake now honour the configure-time definitions of
AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
- The `install-info' recipe no longer tries to guess whether the
`install-info' program is from Debian or from GNU, and adaptively
change its behaviour; this has proven to be frail and easy to
regress.
2012-03-03 13:58:13 +01:00
|
|
|
EXTRACT_SUFX= .tar.xz
|
1997-10-06 16:06:09 +02:00
|
|
|
|
2003-07-17 23:21:03 +02:00
|
|
|
MAINTAINER= wiz@NetBSD.org
|
1998-08-20 17:16:34 +02:00
|
|
|
HOMEPAGE= http://www.gnu.org/software/automake/automake.html
|
2001-02-16 15:38:16 +01:00
|
|
|
COMMENT= GNU Standards-compliant Makefile generator
|
Update to 1.11:
New in 1.11:
* Version requirements:
- Autoconf 2.62 or greater is required.
* Changes to aclocal:
- The autoconf version check implemented by aclocal in aclocal.m4
(and new in Automake 1.10) is degraded to a warning. This helps
in the common case where the Autoconf versions used are compatible.
* Changes to automake:
- The automake program can run multiple threads for creating most
Makefile.in files concurrently, if at least Perl 5.7.2 is available
with interpreter-based threads enabled. Set the environment variable
AUTOMAKE_JOBS to the maximum number of threads to use, in order to
enable this experimental feature.
* Changes to Libtool support:
- Libtool generic flags are now passed to the install and uninstall
modes as well.
- distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
config.lt is removed correctly now.
* Languages changes:
- subdir-object mode works now with Fortran (F77, FC, preprocessed
Fortran, and Ratfor).
- For files with extension .f90, .f95, .f03, or .f08, the flag
$(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
- Files with extension .sx are also treated as preprocessed assembler.
- The default source file extension (.c) can be overridden with
AM_DEFAULT_SOURCE_EXT now.
- Python 3.0 is supported now, Python releases prior to 2.0 are no
longer supported.
- AM_PATH_PYTHON honors python's idea about the site directory.
- There is initial support for the Vala programming language, when using
Vala 0.7.0 or later.
* Miscellaneous changes:
- Automake development is done in a git repository on Savannah now, see
http://git.sv.gnu.org/gitweb/?p=automake.git
A read-only CVS mirror is provided at
cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
checkout -d automake HEAD
- "make dist" can now create xz-compressed tarballs,
as well as (deprecated?) lzma-compressed tarballs.
- `automake --add-missing' will by default install the GPLv3 file as
COPYING if it is missing. It will also warn that the license file
should be added to source control. Note that Automake will never
overwrite an existing COPYING file, even when the `--force-missing'
option is used.
- The manual is now distributed under the terms of the GNU FDL 1.3.
- Automake ships and installs man pages for automake and aclocal now.
- New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
- install-sh supports -C, which does not update the installed file
(and its time stamps) if the contents did not change.
- The `gnupload' script has been revamped.
- The `depcomp' and `compile' scripts now work with MSVC under MSYS.
- The targets `install' and `uninstall' are more efficient now, in that
for example multiple files from one Automake variable such as
`bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
invocation if they do not have to be renamed.
Both install and uninstall may sometimes enter (`cd' into) the target
installation directory now, when no build-local scripts are used.
Both install and uninstall do not fail anymore but do nothing if an
installation directory variable like `bindir' is set to the empty string.
For built-in rules, `make install' now fails reliably if installation
of a file failed. Conversely, `make uninstall' even succeeds when
issued multiple times.
These changes may need some adjustments from users: For example,
some `install' programs refuse to install multiple copies of the
same file in one invocation, so you may need to remove duplicate
entries from file lists.
Also, within one set of files, say, nobase_data_DATA, the order of
installation may be changed, or even unstable among different hosts,
due to the use of associative arrays in awk. The increased use of
awk matches a similar move in Autoconf to provide for better scaling.
Further, most undocumented per-rule install command variables such as
binSCRIPT_INSTALL have been removed because they are not needed any
more. Packages which use them should be using the appropriate one of
INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
counterpart, depending on the type of files and the need for automatic
target directory creation.
- The "deleted header file problem" for *.m4 files is avoided by
stub rules. This allows `make' to trigger a rerun of `aclocal'
also if some previously needed macro file has been removed.
- Rebuild rules now also work for a removed `subdir/Makefile.in' in
an otherwise up to date tree.
- The `color-tests' option causes colored test result output on terminals.
- The `parallel-tests' option enables a new test driver that allows for
parallel test execution, inter-test dependencies, lazy test execution
for unit-testing, re-testing only failed tests, and formatted result output
as RST (reStructuredText) and HTML. Enabling this option may require some
changes to your test suite setup; see the manual for details.
- The `silent-rules' option enables Linux kernel-style silent build output.
This option requires the widely supported but non-POSIX `make' feature
of recursive variable expansion, so do not use it if your package needs
to build with `make' implementations that do not support it.
To enable less verbose build output, the developer has to use the Automake
option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
macro. The user may then set the default verbosity by passing the
`--enable-silent-rules' option to `configure'. At `make' run time, this
default may be overridden using `make V=0' for less verbose, and `make V=1'
for backward-compatible verbose output.
- New prefix `notrans_' for manpages which should not be transformed
by --program-transform.
- New macro AM_COND_IF for conditional evaluation and conditional
config files.
- For AC_CONFIG_LINKS, if source and destination are equal, do not
remove the file in a non-VPATH build. Such setups work with Autoconf
2.62 or newer.
- AM_MAINTAINER_MODE now allows for an optional argument specifying
the default setting.
- AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
useful especially for multi-line values.
- Automake's early configure-time sanity check now diagnoses an
unsafe absolute source directory name and makes configure fail.
- The Automake macros and rules cope better with whitespace in the
current directory name, as long as the relative path to `configure'
does not contain whitespace. To this end, the values of `$(MISSING)'
and `$(install_sh)' may contain suitable quoting, and their expansion
might need `eval'uation if used outside of a makefile. These
undocumented variables may be used in several documented macros such
as $(AUTOCONF) or $(MAKEINFO).
Bugs fixed in 1.11:
* Long standing bugs:
- Fix aix dependency tracking for libtool objects.
- Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
unnecessary use of the `compile' script.
- For nobase_*_LTLIBRARIES with nonempty directory components, the
correct `-rpath' argument is used now.
- `config.status --file=Makefile depfiles' now also works with the
extra quoting used internally by Autoconf 2.62 and newer
(it used to work only without the `--file=' bit).
- The `missing' script works better with versioned tool names.
- Semantics for `missing help2man' have been revamped:
Previously, if `help2man' was not present, `missing help2man' would have
the following semantics: if some man page was out of date but present, then
a warning would be printed, but the exit status was 0. If the man page was
not present at all, then `missing' would create a replacement man page
containing an error message, and exit with a status of 2. This does not play
well with `make': the next run will see this particular man page as being up
to date, and will only error out on the next generated man page, if any;
repeat until all pages are done. This was not desirable.
These are the new semantics: if some man page is not present, and help2man
is not either, then `missing' will warn and generate the replacement page
containing the error message, but exit successfully. However, `make dist'
will ensure that no such bogus man pages are packaged into a tarball.
- Targets provided by automake behave better with `make -n', in that they
take care not to create files.
- `config.status Makefile... depfiles' works fine again in the presence of
disabled dependency tracking.
- The default no-op recursive rules for these targets also work with BSD make
now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
- `make distcheck' works also when both a directory and some file below it
have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
- Texinfo dvi, ps, pdf, and html output files are not removed upon
`make mostlyclean' any more; only the LaTeX by-products are.
- Renamed objects also work with the `subdir-objects' option and
source file languages which Automake does not know itself.
- `automake' now correctly complains about variable assignments which are
preceded by a comment, extend over multiple lines with backslash-escaped
newlines, and end in a comment sign. Previous versions would silently
and wrongly ignore such assignments completely.
* Bugs introduced by 1.10:
- Fix output of dummy dependency files in presence of post-processed
Makefile.in's again, but also cope with long lines.
- $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
that have been declared as programs in the same Makefile.
This is for consistency with the analogous change to TESTS in 1.10.
- Fix order of standard includes to again be `-I. -I$(srcdir)',
followed by directories containing config headers.
2009-06-08 16:44:35 +02:00
|
|
|
LICENSE= gnu-gpl-v2
|
1997-10-06 16:06:09 +02:00
|
|
|
|
Update to 1.11:
New in 1.11:
* Version requirements:
- Autoconf 2.62 or greater is required.
* Changes to aclocal:
- The autoconf version check implemented by aclocal in aclocal.m4
(and new in Automake 1.10) is degraded to a warning. This helps
in the common case where the Autoconf versions used are compatible.
* Changes to automake:
- The automake program can run multiple threads for creating most
Makefile.in files concurrently, if at least Perl 5.7.2 is available
with interpreter-based threads enabled. Set the environment variable
AUTOMAKE_JOBS to the maximum number of threads to use, in order to
enable this experimental feature.
* Changes to Libtool support:
- Libtool generic flags are now passed to the install and uninstall
modes as well.
- distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
config.lt is removed correctly now.
* Languages changes:
- subdir-object mode works now with Fortran (F77, FC, preprocessed
Fortran, and Ratfor).
- For files with extension .f90, .f95, .f03, or .f08, the flag
$(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
- Files with extension .sx are also treated as preprocessed assembler.
- The default source file extension (.c) can be overridden with
AM_DEFAULT_SOURCE_EXT now.
- Python 3.0 is supported now, Python releases prior to 2.0 are no
longer supported.
- AM_PATH_PYTHON honors python's idea about the site directory.
- There is initial support for the Vala programming language, when using
Vala 0.7.0 or later.
* Miscellaneous changes:
- Automake development is done in a git repository on Savannah now, see
http://git.sv.gnu.org/gitweb/?p=automake.git
A read-only CVS mirror is provided at
cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
checkout -d automake HEAD
- "make dist" can now create xz-compressed tarballs,
as well as (deprecated?) lzma-compressed tarballs.
- `automake --add-missing' will by default install the GPLv3 file as
COPYING if it is missing. It will also warn that the license file
should be added to source control. Note that Automake will never
overwrite an existing COPYING file, even when the `--force-missing'
option is used.
- The manual is now distributed under the terms of the GNU FDL 1.3.
- Automake ships and installs man pages for automake and aclocal now.
- New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
- install-sh supports -C, which does not update the installed file
(and its time stamps) if the contents did not change.
- The `gnupload' script has been revamped.
- The `depcomp' and `compile' scripts now work with MSVC under MSYS.
- The targets `install' and `uninstall' are more efficient now, in that
for example multiple files from one Automake variable such as
`bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
invocation if they do not have to be renamed.
Both install and uninstall may sometimes enter (`cd' into) the target
installation directory now, when no build-local scripts are used.
Both install and uninstall do not fail anymore but do nothing if an
installation directory variable like `bindir' is set to the empty string.
For built-in rules, `make install' now fails reliably if installation
of a file failed. Conversely, `make uninstall' even succeeds when
issued multiple times.
These changes may need some adjustments from users: For example,
some `install' programs refuse to install multiple copies of the
same file in one invocation, so you may need to remove duplicate
entries from file lists.
Also, within one set of files, say, nobase_data_DATA, the order of
installation may be changed, or even unstable among different hosts,
due to the use of associative arrays in awk. The increased use of
awk matches a similar move in Autoconf to provide for better scaling.
Further, most undocumented per-rule install command variables such as
binSCRIPT_INSTALL have been removed because they are not needed any
more. Packages which use them should be using the appropriate one of
INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
counterpart, depending on the type of files and the need for automatic
target directory creation.
- The "deleted header file problem" for *.m4 files is avoided by
stub rules. This allows `make' to trigger a rerun of `aclocal'
also if some previously needed macro file has been removed.
- Rebuild rules now also work for a removed `subdir/Makefile.in' in
an otherwise up to date tree.
- The `color-tests' option causes colored test result output on terminals.
- The `parallel-tests' option enables a new test driver that allows for
parallel test execution, inter-test dependencies, lazy test execution
for unit-testing, re-testing only failed tests, and formatted result output
as RST (reStructuredText) and HTML. Enabling this option may require some
changes to your test suite setup; see the manual for details.
- The `silent-rules' option enables Linux kernel-style silent build output.
This option requires the widely supported but non-POSIX `make' feature
of recursive variable expansion, so do not use it if your package needs
to build with `make' implementations that do not support it.
To enable less verbose build output, the developer has to use the Automake
option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
macro. The user may then set the default verbosity by passing the
`--enable-silent-rules' option to `configure'. At `make' run time, this
default may be overridden using `make V=0' for less verbose, and `make V=1'
for backward-compatible verbose output.
- New prefix `notrans_' for manpages which should not be transformed
by --program-transform.
- New macro AM_COND_IF for conditional evaluation and conditional
config files.
- For AC_CONFIG_LINKS, if source and destination are equal, do not
remove the file in a non-VPATH build. Such setups work with Autoconf
2.62 or newer.
- AM_MAINTAINER_MODE now allows for an optional argument specifying
the default setting.
- AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
useful especially for multi-line values.
- Automake's early configure-time sanity check now diagnoses an
unsafe absolute source directory name and makes configure fail.
- The Automake macros and rules cope better with whitespace in the
current directory name, as long as the relative path to `configure'
does not contain whitespace. To this end, the values of `$(MISSING)'
and `$(install_sh)' may contain suitable quoting, and their expansion
might need `eval'uation if used outside of a makefile. These
undocumented variables may be used in several documented macros such
as $(AUTOCONF) or $(MAKEINFO).
Bugs fixed in 1.11:
* Long standing bugs:
- Fix aix dependency tracking for libtool objects.
- Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
unnecessary use of the `compile' script.
- For nobase_*_LTLIBRARIES with nonempty directory components, the
correct `-rpath' argument is used now.
- `config.status --file=Makefile depfiles' now also works with the
extra quoting used internally by Autoconf 2.62 and newer
(it used to work only without the `--file=' bit).
- The `missing' script works better with versioned tool names.
- Semantics for `missing help2man' have been revamped:
Previously, if `help2man' was not present, `missing help2man' would have
the following semantics: if some man page was out of date but present, then
a warning would be printed, but the exit status was 0. If the man page was
not present at all, then `missing' would create a replacement man page
containing an error message, and exit with a status of 2. This does not play
well with `make': the next run will see this particular man page as being up
to date, and will only error out on the next generated man page, if any;
repeat until all pages are done. This was not desirable.
These are the new semantics: if some man page is not present, and help2man
is not either, then `missing' will warn and generate the replacement page
containing the error message, but exit successfully. However, `make dist'
will ensure that no such bogus man pages are packaged into a tarball.
- Targets provided by automake behave better with `make -n', in that they
take care not to create files.
- `config.status Makefile... depfiles' works fine again in the presence of
disabled dependency tracking.
- The default no-op recursive rules for these targets also work with BSD make
now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
- `make distcheck' works also when both a directory and some file below it
have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
- Texinfo dvi, ps, pdf, and html output files are not removed upon
`make mostlyclean' any more; only the LaTeX by-products are.
- Renamed objects also work with the `subdir-objects' option and
source file languages which Automake does not know itself.
- `automake' now correctly complains about variable assignments which are
preceded by a comment, extend over multiple lines with backslash-escaped
newlines, and end in a comment sign. Previous versions would silently
and wrongly ignore such assignments completely.
* Bugs introduced by 1.10:
- Fix output of dummy dependency files in presence of post-processed
Makefile.in's again, but also cope with long lines.
- $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
that have been declared as programs in the same Makefile.
This is for consistency with the analogous change to TESTS in 1.10.
- Fix order of standard includes to again be `-I. -I$(srcdir)',
followed by directories containing config headers.
2009-06-08 16:44:35 +02:00
|
|
|
DEPENDS+= autoconf>=2.62:../../devel/autoconf
|
2006-11-02 18:59:37 +01:00
|
|
|
|
2005-07-16 21:10:37 +02:00
|
|
|
USE_TOOLS+= gm4:run perl:run
|
2005-05-22 22:51:45 +02:00
|
|
|
|
Update to 1.15:
New in 1.15:
* Improvements and refactorings in the install-sh script:
- It has been modernized, and now makes the following assumptions
*unconditionally*:
(1) a working 'dirname' program is available;
(2) the ${var:-value} shell parameters substitution works;
(3) the "set -f" and "set +f" shell commands work, and, respectively,
disable and enable shell globbing.
- The script implements stricter error checking, and now it complains
and bails out if any of the following expectations is not met:
(1) the options -d and -t are never used together;
(2) the argument passed to option -t is a directory;
(3) if there are two or more SOURCEFILE arguments, the
DESTINATION argument must be a directory.
* Automake-generated testsuites:
- The default test-driver used by the Automake-generates testsuites
now appends the result and exit status of each "plain" test to the
associated log file (automake bug#11814).
- The perl implementation of the TAP testsuite driver is no longer
installed in the Automake's scripts directory, and is instead just
distributed as a "contrib" addition. There should be no reason to
use this implementation anyway in real packages, since the awk+shell
implementation of the TAP driver (which is documented in the manual)
is more portable and has feature parity with the perl implementation.
- The rule generating 'test-suite.log' no longer risk incurring in an
extra useless "make all" recursive invocation in some corner cases
(automake bug#16302).
* Distribution:
- Automake bug#18286: "make distcheck" could sometimes fail to detect
files missing from the distribution tarball, especially in those cases
where both the generated files and their dependencies are explicitly
in $(srcdir). An important example of this are *generated* makefile
fragments included at Automake time in Makefile.am; e.g.:
...
$(srcdir)/fragment.am: $(srcdir)/data.txt $(srcdir)/preproc.sh
cd $(srcdir) && $(SHELL) preproc.sh <data.txt >fragment.am
include $(srcdir)/fragment.am
...
If the use forgot to add data.txt and/or preproc.sh in the distribution
tarball, "make distcheck" would have erroneously succeeded! This issue
is now fixed.
- As a consequence of the previous change, "make distcheck" will run
using '$(distdir)/_build/sub' as the build directory, rather than
simply '$(distdir)/_build' (as it was the case for Automake 1.14 and
earlier). Consequently, the './configure' and 'make' invocations
issued by the distcheck recipe now have $(srcdir) equal to '../..',
rather than to just '..'. Dependent and similar variables (e.g.,
'$(top_srcdir)') are also changed accordingly.
Thus, Makefiles that made assumptions about the exact values of the
build and source directories used by "make distcheck" will have to
be adjusted. Notice that making such assumptions was a bad and
unsupported practice anyway, since the exact locations of those
directories should be considered implementation details, and we
reserve the right to change them at any time.
* Miscellaneous bugs fixed:
- The expansion of AM_INIT_AUTOMAKE ends once again with a trailing
newline (bug#16841). Regression introduced in Automake 1.14.
- We no longer risk to use '$ac_aux_dir' before it's defined (see
automake bug#15981). Bug introduced in Automake 1.14.
- The code used to detect whether the currently used make is GNU make
or not (relying on the private macro 'am__is_gnu_make') no longer
risks causing "Arg list too long" for projects using automatic
dependency tracking and having a ton of source files (bug#18744).
- Automake tries to offer a more deterministic output for generated
Makefiles, in the face of the newly-introduced randomization for
hash keys order in Perl 5.18.
- In older Automake versions, if a user defined one single Makefile
fragment (say 'foo.am') to be included via Automake includes in
his main Makefile.am, and defined a custom make rule to generate that
file from other data, Automake used to spuriously complain with some
message like "... overrides Automake target '$(srcdir)/foo.am".
This bug is now fixed.
- The user can now extend the special .PRECIOUS target, the same way
he could already do with the .MAKE .and .PHONY targets.
- Some confusing typos have been fixed in the manual and in few warning
messages (automake bug#16827 and bug#16997).
2015-01-08 17:40:50 +01:00
|
|
|
PLIST_SUBST+= PKG_DIR_VERSION=1.15
|
2001-11-28 06:20:38 +01:00
|
|
|
GNU_CONFIGURE= YES
|
2002-08-25 23:48:57 +02:00
|
|
|
_STRIPFLAG_INSTALL= # none
|
2010-10-17 02:39:32 +02:00
|
|
|
INFO_FILES= YES
|
2002-10-03 21:31:51 +02:00
|
|
|
|
2004-03-19 11:41:48 +01:00
|
|
|
# doesn't work because buildlink3 hides scripts
|
|
|
|
|
# from autoconf too well
|
|
|
|
|
#TEST_TARGET= check
|
2003-10-19 03:34:13 +02:00
|
|
|
|
1998-04-15 12:38:15 +02:00
|
|
|
.include "../../mk/bsd.pkg.mk"
|
