2013-05-27 16:46:08 +02:00
|
|
|
---
|
2013-06-17 13:45:26 +02:00
|
|
|
lib/config.guess | 156 +++++++++++++++++++++++++++++--------------------------
|
|
|
|
1 file changed, 83 insertions(+), 73 deletions(-)
|
2013-05-27 16:46:08 +02:00
|
|
|
|
2013-02-27 06:43:54 +01:00
|
|
|
Index: lib/config.guess
|
|
|
|
===================================================================
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
--- lib/config.guess.orig 2015-02-10 12:01:47.557016290 +0100
|
|
|
|
+++ lib/config.guess 2015-02-10 12:05:32.791670816 +0100
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
@@ -153,6 +153,16 @@ Linux|GNU|GNU/*)
|
|
|
|
;;
|
|
|
|
esac
|
2006-12-19 00:15:10 +01:00
|
|
|
|
|
|
|
+case "${UNAME_MACHINE}" in
|
2012-04-18 07:07:27 +02:00
|
|
|
+ i?86)
|
|
|
|
+ test -z "$VENDOR" && VENDOR=pc
|
|
|
|
+ ;;
|
|
|
|
+ *)
|
|
|
|
+ test -z "$VENDOR" && VENDOR=unknown
|
|
|
|
+ ;;
|
2006-12-19 00:15:10 +01:00
|
|
|
+esac
|
|
|
|
+test -f /etc/SuSE-release -o -f /.buildenv && VENDOR=suse
|
|
|
|
+
|
|
|
|
# Note: order is significant - the case branches are not exclusive.
|
|
|
|
|
|
|
|
case "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
@@ -217,23 +227,23 @@ case "${UNAME_MACHINE}:${UNAME_SYSTEM}:$
|
2013-02-27 06:43:54 +01:00
|
|
|
exit ;;
|
|
|
|
*:Bitrig:*:*)
|
|
|
|
UNAME_MACHINE_ARCH=`arch | sed 's/Bitrig.//'`
|
|
|
|
- echo ${UNAME_MACHINE_ARCH}-unknown-bitrig${UNAME_RELEASE}
|
|
|
|
+ echo ${UNAME_MACHINE_ARCH}-${VENDOR}-bitrig${UNAME_RELEASE}
|
2009-12-11 17:59:51 +01:00
|
|
|
exit ;;
|
|
|
|
*:OpenBSD:*:*)
|
|
|
|
UNAME_MACHINE_ARCH=`arch | sed 's/OpenBSD.//'`
|
|
|
|
- echo ${UNAME_MACHINE_ARCH}-unknown-openbsd${UNAME_RELEASE}
|
|
|
|
+ echo ${UNAME_MACHINE_ARCH}-${VENDOR}-openbsd${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
*:ekkoBSD:*:*)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-ekkobsd${UNAME_RELEASE}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-ekkobsd${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
*:SolidBSD:*:*)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-solidbsd${UNAME_RELEASE}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-solidbsd${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
macppc:MirBSD:*:*)
|
|
|
|
- echo powerpc-unknown-mirbsd${UNAME_RELEASE}
|
|
|
|
+ echo powerpc-${VENDOR}-mirbsd${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
*:MirBSD:*:*)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-mirbsd${UNAME_RELEASE}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-mirbsd${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
alpha:OSF1:*:*)
|
|
|
|
case $UNAME_RELEASE in
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
@@ -301,13 +311,13 @@ case "${UNAME_MACHINE}:${UNAME_SYSTEM}:$
|
2009-12-11 17:59:51 +01:00
|
|
|
echo alpha-dec-winnt3.5
|
|
|
|
exit ;;
|
|
|
|
Amiga*:UNIX_System_V:4.0:*)
|
|
|
|
- echo m68k-unknown-sysv4
|
|
|
|
+ echo m68k-${VENDOR}-sysv4
|
|
|
|
exit ;;
|
|
|
|
*:[Aa]miga[Oo][Ss]:*:*)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-amigaos
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-amigaos
|
|
|
|
exit ;;
|
|
|
|
*:[Mm]orph[Oo][Ss]:*:*)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-morphos
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-morphos
|
|
|
|
exit ;;
|
|
|
|
*:OS/390:*:*)
|
|
|
|
echo i370-ibm-openedition
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
@@ -322,7 +332,7 @@ case "${UNAME_MACHINE}:${UNAME_SYSTEM}:$
|
2009-12-11 17:59:51 +01:00
|
|
|
echo arm-acorn-riscix${UNAME_RELEASE}
|
|
|
|
exit ;;
|
2013-02-27 06:43:54 +01:00
|
|
|
arm*:riscos:*:*|arm*:RISCOS:*:*)
|
2009-12-11 17:59:51 +01:00
|
|
|
- echo arm-unknown-riscos
|
|
|
|
+ echo arm-${VENDOR}-riscos
|
|
|
|
exit ;;
|
|
|
|
SR2?01:HI-UX/MPP:*:* | SR8000:HI-UX/MPP:*:*)
|
|
|
|
echo hppa1.1-hitachi-hiuxmpp
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
@@ -430,7 +440,7 @@ case "${UNAME_MACHINE}:${UNAME_SYSTEM}:$
|
2012-04-18 07:07:27 +02:00
|
|
|
echo m68k-hades-mint${UNAME_RELEASE}
|
|
|
|
exit ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
*:*MiNT:*:* | *:*mint:*:* | *:*TOS:*:*)
|
2012-04-18 07:07:27 +02:00
|
|
|
- echo m68k-unknown-mint${UNAME_RELEASE}
|
|
|
|
+ echo m68k-${VENDOR}-mint${UNAME_RELEASE}
|
|
|
|
exit ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
m68k:machten:*:*)
|
|
|
|
echo m68k-apple-machten${UNAME_RELEASE}
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -742,9 +752,9 @@ EOF
|
2009-12-11 17:59:51 +01:00
|
|
|
exit ;;
|
|
|
|
i*86:OSF1:*:*)
|
|
|
|
if [ -x /usr/sbin/sysversion ] ; then
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-osf1mk
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-osf1mk
|
|
|
|
else
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-osf1
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-osf1
|
|
|
|
fi
|
|
|
|
exit ;;
|
|
|
|
parisc*:Lites*:*:*)
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -804,18 +814,18 @@ EOF
|
2009-12-11 17:59:51 +01:00
|
|
|
echo ${UNAME_MACHINE}-pc-bsdi${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
sparc*:BSD/OS:*:*)
|
|
|
|
- echo sparc-unknown-bsdi${UNAME_RELEASE}
|
|
|
|
+ echo sparc-${VENDOR}-bsdi${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
*:BSD/OS:*:*)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-bsdi${UNAME_RELEASE}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-bsdi${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
*:FreeBSD:*:*)
|
2012-04-18 07:07:27 +02:00
|
|
|
UNAME_PROCESSOR=`/usr/bin/uname -p`
|
|
|
|
case ${UNAME_PROCESSOR} in
|
2009-12-11 17:59:51 +01:00
|
|
|
amd64)
|
|
|
|
- echo x86_64-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
|
|
|
|
+ echo x86_64-${VENDOR}-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
|
|
|
|
*)
|
2012-04-18 07:07:27 +02:00
|
|
|
- echo ${UNAME_PROCESSOR}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
|
|
|
|
+ echo ${UNAME_PROCESSOR}-${VENDOR}-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
esac
|
|
|
|
exit ;;
|
|
|
|
i*:CYGWIN*:*)
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -843,10 +853,10 @@ EOF
|
2009-12-11 17:59:51 +01:00
|
|
|
echo i586-pc-interix${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
authenticamd | genuineintel | EM64T)
|
|
|
|
- echo x86_64-unknown-interix${UNAME_RELEASE}
|
|
|
|
+ echo x86_64-${VENDOR}-interix${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
IA64)
|
|
|
|
- echo ia64-unknown-interix${UNAME_RELEASE}
|
|
|
|
+ echo ia64-${VENDOR}-interix${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
esac ;;
|
|
|
|
[345]86:Windows_95:* | [345]86:Windows_98:* | [345]86:Windows_NT:*)
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -865,31 +875,31 @@ EOF
|
2009-12-11 17:59:51 +01:00
|
|
|
echo ${UNAME_MACHINE}-pc-uwin
|
|
|
|
exit ;;
|
|
|
|
amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
|
|
|
|
- echo x86_64-unknown-cygwin
|
|
|
|
+ echo x86_64-${VENDOR}-cygwin
|
|
|
|
exit ;;
|
|
|
|
p*:CYGWIN*:*)
|
|
|
|
- echo powerpcle-unknown-cygwin
|
|
|
|
+ echo powerpcle-${VENDOR}-cygwin
|
|
|
|
exit ;;
|
|
|
|
prep*:SunOS:5.*:*)
|
|
|
|
- echo powerpcle-unknown-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
|
|
|
|
+ echo powerpcle-${VENDOR}-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
|
|
|
|
exit ;;
|
|
|
|
*:GNU:*:*)
|
|
|
|
# the GNU system
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo `echo ${UNAME_MACHINE}|sed -e 's,[-/].*$,,'`-unknown-${LIBC}`echo ${UNAME_RELEASE}|sed -e 's,/.*$,,'`
|
|
|
|
+ echo `echo ${UNAME_MACHINE}|sed -e 's,[-/].*$,,'`-${VENDOR}-${LIBC}`echo ${UNAME_RELEASE}|sed -e 's,/.*$,,'`
|
2009-12-11 17:59:51 +01:00
|
|
|
exit ;;
|
|
|
|
*:GNU/*:*:*)
|
|
|
|
# other systems with GNU libc and userland
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-`echo ${UNAME_SYSTEM} | sed 's,^[^/]*/,,' | tr '[A-Z]' '[a-z]'``echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-`echo ${UNAME_SYSTEM} | sed 's,^[^/]*/,,' | tr '[A-Z]' '[a-z]'``echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`-${LIBC}
|
2009-12-11 17:59:51 +01:00
|
|
|
exit ;;
|
|
|
|
i*86:Minix:*:*)
|
|
|
|
echo ${UNAME_MACHINE}-pc-minix
|
2012-04-18 07:07:27 +02:00
|
|
|
exit ;;
|
|
|
|
aarch64:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2012-04-18 07:07:27 +02:00
|
|
|
exit ;;
|
|
|
|
aarch64_be:Linux:*:*)
|
|
|
|
UNAME_MACHINE=aarch64_be
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2012-04-18 07:07:27 +02:00
|
|
|
exit ;;
|
|
|
|
alpha:Linux:*:*)
|
|
|
|
case `sed -n '/^cpu model/s/^.*: \(.*\)/\1/p' < /proc/cpuinfo` in
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -903,29 +913,29 @@ EOF
|
2012-04-18 07:07:27 +02:00
|
|
|
esac
|
2009-12-11 17:59:51 +01:00
|
|
|
objdump --private-headers /bin/sh | grep -q ld.so.1
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
if test "$?" = 0 ; then LIBC="gnulibc1" ; fi
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2009-12-11 17:59:51 +01:00
|
|
|
exit ;;
|
2013-05-27 16:46:08 +02:00
|
|
|
arc:Linux:*:* | arceb:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
|
|
|
exit ;;
|
|
|
|
arm*:Linux:*:*)
|
|
|
|
eval $set_cc_for_build
|
2008-01-25 16:52:26 +01:00
|
|
|
if echo __ARM_EABI__ | $CC_FOR_BUILD -E - 2>/dev/null \
|
|
|
|
| grep -q __ARM_EABI__
|
|
|
|
then
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2008-01-25 16:52:26 +01:00
|
|
|
else
|
2012-04-18 07:07:27 +02:00
|
|
|
if echo __ARM_PCS_VFP | $CC_FOR_BUILD -E - 2>/dev/null \
|
|
|
|
| grep -q __ARM_PCS_VFP
|
|
|
|
then
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}eabi
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}eabi
|
2012-04-18 07:07:27 +02:00
|
|
|
else
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}eabihf
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}eabihf
|
2012-04-18 07:07:27 +02:00
|
|
|
fi
|
2008-01-25 16:52:26 +01:00
|
|
|
fi
|
|
|
|
exit ;;
|
|
|
|
avr32*:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
|
|
|
cris:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
echo ${UNAME_MACHINE}-axis-linux-${LIBC}
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -934,22 +944,22 @@ EOF
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
echo ${UNAME_MACHINE}-axis-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
|
|
|
frv:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2012-04-18 07:07:27 +02:00
|
|
|
exit ;;
|
|
|
|
hexagon:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
i*86:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
echo ${UNAME_MACHINE}-pc-linux-${LIBC}
|
2009-12-11 17:59:51 +01:00
|
|
|
exit ;;
|
2006-12-19 00:15:10 +01:00
|
|
|
ia64:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
|
|
|
m32r*:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
|
|
|
m68*:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
mips:Linux:*:* | mips64:Linux:*:*)
|
2006-12-19 00:15:10 +01:00
|
|
|
eval $set_cc_for_build
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -968,63 +978,63 @@ EOF
|
2009-12-11 17:59:51 +01:00
|
|
|
#endif
|
|
|
|
EOF
|
|
|
|
eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^CPU'`
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- test x"${CPU}" != x && { echo "${CPU}-unknown-linux-${LIBC}"; exit; }
|
|
|
|
+ test x"${CPU}" != x && { echo "${CPU}-${VENDOR}-linux-${LIBC}"; exit; }
|
2006-12-19 00:15:10 +01: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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
openrisc*:Linux:*:*)
|
|
|
|
- echo or1k-unknown-linux-${LIBC}
|
|
|
|
+ echo or1k-${VENDOR}-linux-${LIBC}
|
2013-05-27 16:46:08 +02:00
|
|
|
exit ;;
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
or32:Linux:*:* | or1k*:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
padre:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo sparc-unknown-linux-${LIBC}
|
|
|
|
+ echo sparc-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
parisc64:Linux:*:* | hppa64:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo hppa64-unknown-linux-${LIBC}
|
|
|
|
+ echo hppa64-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
|
|
|
parisc:Linux:*:* | hppa:Linux:*:*)
|
|
|
|
# Look for CPU level
|
|
|
|
case `grep '^cpu[^a-z]*:' /proc/cpuinfo 2>/dev/null | cut -d' ' -f2` in
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- PA7*) echo hppa1.1-unknown-linux-${LIBC} ;;
|
|
|
|
- PA8*) echo hppa2.0-unknown-linux-${LIBC} ;;
|
|
|
|
- *) echo hppa-unknown-linux-${LIBC} ;;
|
|
|
|
+ PA7*) echo hppa1.1-${VENDOR}-linux-${LIBC} ;;
|
|
|
|
+ PA8*) echo hppa2.0-${VENDOR}-linux-${LIBC} ;;
|
|
|
|
+ *) echo hppa-${VENDOR}-linux-${LIBC} ;;
|
2006-12-19 00:15:10 +01:00
|
|
|
esac
|
|
|
|
exit ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
ppc64:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo powerpc64-unknown-linux-${LIBC}
|
|
|
|
+ echo powerpc64-${VENDOR}-linux-${LIBC}
|
2009-12-11 17:59:51 +01:00
|
|
|
exit ;;
|
|
|
|
ppc:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo powerpc-unknown-linux-${LIBC}
|
|
|
|
+ echo powerpc-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
2013-06-17 13:45:26 +02:00
|
|
|
ppc64le:Linux:*:*)
|
|
|
|
- echo powerpc64le-unknown-linux-${LIBC}
|
|
|
|
+ echo powerpc64le-${VENDOR}-linux-${LIBC}
|
|
|
|
exit ;;
|
|
|
|
ppcle:Linux:*:*)
|
|
|
|
- echo powerpcle-unknown-linux-${LIBC}
|
|
|
|
+ echo powerpcle-${VENDOR}-linux-${LIBC}
|
|
|
|
exit ;;
|
2006-12-19 00:15:10 +01:00
|
|
|
s390:Linux:*:* | s390x:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
echo ${UNAME_MACHINE}-ibm-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
|
|
|
sh64*:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
|
|
|
sh*:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
|
|
|
sparc:Linux:*:* | sparc64:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2012-04-18 07:07:27 +02:00
|
|
|
exit ;;
|
|
|
|
tile*:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
|
|
|
vax:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
echo ${UNAME_MACHINE}-dec-linux-${LIBC}
|
|
|
|
exit ;;
|
|
|
|
x86_64:Linux:*:*)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2006-12-19 00:15:10 +01:00
|
|
|
exit ;;
|
2008-01-25 16:52:26 +01:00
|
|
|
xtensa*:Linux:*:*)
|
- Update to 1.13.3:
* Documentation fixes:
- The documentation no longer mistakenly reports that the
obsolete 'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable
are going to be removed in Automake 2.0.
* Bugs fixed:
- Byte-compilation of Emacs lisp files could fail spuriously on
Solaris, when /bin/ksh or /usr/xpg4/bin/sh were used as shell.
- If the same user-defined suffixes were transformed into
different Automake-known suffixes in different Makefile.am
files in the same project, automake could get confused and
generate inconsistent Makefiles (automake bug#14441).
For example, if 'Makefile.am' contained a ".ext.cc:" suffix
rule, and 'sub/Makefile.am' contained a ".ext.c:" suffix rule,
automake would have mistakenly placed into 'Makefile.in' rules
to compile "*.c" files into object files, and into
'sub/Makefile.in' rules to compile "*.cc" files into object
files --- rather than the other way around. This is now fixed.
- Several spurious failures have been fixed (they hit especially
MinGW/MSYS builds). See automake bugs #14493, #14494, #14495,
#14498, #14499, #14500, #14501, #14517 and #14528.
- Some other minor miscellaneous changes and fixlets.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=34
2013-06-12 15:24:56 +02:00
|
|
|
- echo ${UNAME_MACHINE}-unknown-linux-${LIBC}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-linux-${LIBC}
|
2008-01-25 16:52:26 +01:00
|
|
|
exit ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
i*86:DYNIX/ptx:4*:*)
|
|
|
|
# ptx 4.0 does uname -s correctly, with DYNIX/ptx in there.
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -1046,16 +1056,16 @@ EOF
|
2009-03-17 16:44:42 +01:00
|
|
|
echo ${UNAME_MACHINE}-pc-os2-emx
|
|
|
|
exit ;;
|
|
|
|
i*86:XTS-300:*:STOP)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-stop
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-stop
|
|
|
|
exit ;;
|
|
|
|
i*86:atheos:*:*)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-atheos
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-atheos
|
|
|
|
exit ;;
|
|
|
|
i*86:syllable:*:*)
|
|
|
|
echo ${UNAME_MACHINE}-pc-syllable
|
|
|
|
exit ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
i*86:LynxOS:2.*:* | i*86:LynxOS:3.[01]*:* | i*86:LynxOS:4.[02]*:*)
|
2009-03-17 16:44:42 +01:00
|
|
|
- echo i386-unknown-lynxos${UNAME_RELEASE}
|
2012-04-18 07:07:27 +02:00
|
|
|
+ echo i386-${VENODR}-lynxos${UNAME_RELEASE}
|
2009-03-17 16:44:42 +01:00
|
|
|
exit ;;
|
|
|
|
i*86:*DOS:*:*)
|
|
|
|
echo ${UNAME_MACHINE}-pc-msdosdjgpp
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -1075,7 +1085,7 @@ EOF
|
2009-03-17 16:44:42 +01:00
|
|
|
*Pentium) UNAME_MACHINE=i586 ;;
|
|
|
|
*Pent*|*Celeron) UNAME_MACHINE=i686 ;;
|
|
|
|
esac
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-sysv${UNAME_RELEASE}${UNAME_SYSTEM}${UNAME_VERSION}
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-sysv${UNAME_RELEASE}${UNAME_SYSTEM}${UNAME_VERSION}
|
|
|
|
exit ;;
|
|
|
|
i*86:*:3.2:*)
|
|
|
|
if test -f /usr/options/cb.name; then
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -1114,7 +1124,7 @@ EOF
|
2009-03-17 16:44:42 +01:00
|
|
|
if grep Stardent /usr/include/sys/uadmin.h >/dev/null 2>&1 ; then
|
|
|
|
echo i860-stardent-sysv${UNAME_RELEASE} # Stardent Vistra i860-SVR4
|
|
|
|
else # Add other i860-SVR4 vendors below as they are discovered.
|
|
|
|
- echo i860-unknown-sysv${UNAME_RELEASE} # Unknown i860-SVR4
|
2012-04-18 07:07:27 +02:00
|
|
|
+ echo i860-${VENODR}-sysv${UNAME_RELEASE} # Unknown i860-SVR4
|
2009-03-17 16:44:42 +01:00
|
|
|
fi
|
|
|
|
exit ;;
|
|
|
|
mini*:CTIX:SYS*5:*)
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -1151,19 +1161,19 @@ EOF
|
2009-08-28 17:50:33 +02:00
|
|
|
/bin/uname -p 2>/dev/null | /bin/grep pteron >/dev/null \
|
|
|
|
&& { echo i586-ncr-sysv4.3${OS_REL}; exit; } ;;
|
2009-03-17 16:44:42 +01:00
|
|
|
m68*:LynxOS:2.*:* | m68*:LynxOS:3.0*:*)
|
|
|
|
- echo m68k-unknown-lynxos${UNAME_RELEASE}
|
|
|
|
+ echo m68k-${VENDOR}-lynxos${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
mc68030:UNIX_System_V:4.*:*)
|
|
|
|
echo m68k-atari-sysv4
|
|
|
|
exit ;;
|
|
|
|
TSUNAMI:LynxOS:2.*:*)
|
|
|
|
- echo sparc-unknown-lynxos${UNAME_RELEASE}
|
|
|
|
+ echo sparc-${VENDOR}-lynxos${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
rs6000:LynxOS:2.*:*)
|
|
|
|
- echo rs6000-unknown-lynxos${UNAME_RELEASE}
|
|
|
|
+ echo rs6000-${VENDOR}-lynxos${UNAME_RELEASE}
|
|
|
|
exit ;;
|
2009-12-11 17:59:51 +01:00
|
|
|
PowerPC:LynxOS:2.*:* | PowerPC:LynxOS:3.[01]*:* | PowerPC:LynxOS:4.[02]*:*)
|
2009-03-17 16:44:42 +01:00
|
|
|
- echo powerpc-unknown-lynxos${UNAME_RELEASE}
|
|
|
|
+ echo powerpc-${VENDOR}-lynxos${UNAME_RELEASE}
|
|
|
|
exit ;;
|
|
|
|
SM[BE]S:UNIX_SV:*:*)
|
|
|
|
echo mips-dde-sysv${UNAME_RELEASE}
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -1213,7 +1223,7 @@ EOF
|
2009-03-17 16:44:42 +01:00
|
|
|
if [ -d /usr/nec ]; then
|
2012-04-18 07:07:27 +02:00
|
|
|
echo mips-nec-sysv${UNAME_RELEASE}
|
2009-03-17 16:44:42 +01:00
|
|
|
else
|
2012-04-18 07:07:27 +02:00
|
|
|
- echo mips-unknown-sysv${UNAME_RELEASE}
|
|
|
|
+ echo mips-${VENDOR}-sysv${UNAME_RELEASE}
|
2009-03-17 16:44:42 +01:00
|
|
|
fi
|
2012-04-18 07:07:27 +02:00
|
|
|
exit ;;
|
2009-03-17 16:44:42 +01:00
|
|
|
BeBox:BeOS:*:*) # BeOS running on hardware made by Be, PPC only.
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -1229,7 +1239,7 @@ EOF
|
2013-02-27 06:43:54 +01:00
|
|
|
echo i586-pc-haiku
|
|
|
|
exit ;;
|
|
|
|
x86_64:Haiku:*:*)
|
|
|
|
- echo x86_64-unknown-haiku
|
|
|
|
+ echo x86_64-${VENDOR}-haiku
|
|
|
|
exit ;;
|
|
|
|
SX-4:SUPER-UX:*:*)
|
|
|
|
echo sx4-nec-superux${UNAME_RELEASE}
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -1322,13 +1332,13 @@ EOF
|
2009-03-17 16:44:42 +01:00
|
|
|
else
|
|
|
|
UNAME_MACHINE="$cputype"
|
|
|
|
fi
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-plan9
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-plan9
|
|
|
|
exit ;;
|
|
|
|
*:TOPS-10:*:*)
|
|
|
|
- echo pdp10-unknown-tops10
|
|
|
|
+ echo pdp10-${VENDOR}-tops10
|
|
|
|
exit ;;
|
|
|
|
*:TENEX:*:*)
|
|
|
|
- echo pdp10-unknown-tenex
|
|
|
|
+ echo pdp10-${VENDOR}-tenex
|
|
|
|
exit ;;
|
|
|
|
KS10:TOPS-20:*:* | KL10:TOPS-20:*:* | TYPE4:TOPS-20:*:*)
|
|
|
|
echo pdp10-dec-tops20
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -1337,16 +1347,16 @@ EOF
|
2009-03-17 16:44:42 +01:00
|
|
|
echo pdp10-xkl-tops20
|
|
|
|
exit ;;
|
|
|
|
*:TOPS-20:*:*)
|
|
|
|
- echo pdp10-unknown-tops20
|
|
|
|
+ echo pdp10-${VENDOR}-tops20
|
|
|
|
exit ;;
|
|
|
|
*:ITS:*:*)
|
|
|
|
- echo pdp10-unknown-its
|
|
|
|
+ echo pdp10-${VENDOR}-its
|
|
|
|
exit ;;
|
|
|
|
SEI:*:*:SEIUX)
|
2012-04-18 07:07:27 +02:00
|
|
|
echo mips-sei-seiux${UNAME_RELEASE}
|
2009-03-17 16:44:42 +01:00
|
|
|
exit ;;
|
|
|
|
*:DragonFly:*:*)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-dragonfly`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-dragonfly`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`
|
|
|
|
exit ;;
|
|
|
|
*:*VMS:*:*)
|
2012-04-18 07:07:27 +02:00
|
|
|
UNAME_MACHINE=`(uname -p) 2>/dev/null`
|
- 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).
- Remove automake-fix-ac_aux_dir-used-before-initialized.patch as the
change is incorporated now.
- Refresh automake-SuSE.patch and automake-require_file.patch so that
they apply cleanly.
OBS-URL: https://build.opensuse.org/package/show/devel:tools:building/automake?expand=0&rev=46
2015-02-10 12:25:10 +01:00
|
|
|
@@ -1368,7 +1378,7 @@ EOF
|
2012-04-18 07:07:27 +02:00
|
|
|
echo ${UNAME_MACHINE}-pc-aros
|
|
|
|
exit ;;
|
|
|
|
x86_64:VMkernel:*:*)
|
|
|
|
- echo ${UNAME_MACHINE}-unknown-esx
|
|
|
|
+ echo ${UNAME_MACHINE}-${VENDOR}-esx
|
|
|
|
exit ;;
|
|
|
|
esac
|
|
|
|
|