From: Paul Eggert Date: Wed, 1 Jan 2025 22:28:48 +0000 (-0800) Subject: make fetch X-Git-Tag: v1.17.90~38 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=8da33f8f084dc2f052e8a8ec1ca14d1e2165cba3;p=thirdparty%2Fautomake.git make fetch --- diff --git a/INSTALL b/INSTALL index d3b6e4ec4..c032ea507 100644 --- a/INSTALL +++ b/INSTALL @@ -13,7 +13,10 @@ Basic Installation should configure, build, and install this package. The first line, which bootstraps, is intended for developers; when building from -distribution tarballs it does nothing and can be skipped. +distribution tarballs it does nothing and can be skipped. A package +might name the bootstrapping script differently; if the name is +‘autogen.sh’, for example, the first line should say ‘./autogen.sh’ +instead of ‘./bootstrap’. The following more-detailed instructions are generic; see the ‘README’ file for instructions specific to this package. Some packages @@ -25,23 +28,22 @@ found in the GNU Coding Standards. Many packages have scripts meant for developers instead of ordinary builders, as they may use developer tools that are less commonly installed, or they may access the network, which has privacy -implications. If the ‘bootstrap’ shell script exists, it attempts to -build the ‘configure’ shell script and related files, possibly using -developer tools or the network. Because the output of ‘bootstrap’ is -system-independent, it is normally run by a package developer so that -its output can be put into the distribution tarball and ordinary -builders and users need not run ‘bootstrap’. Some packages have -commands like ‘./autopull.sh’ and ‘./autogen.sh’ that you can run -instead of ‘./bootstrap’, for more fine-grained control over -bootstrapping. - - The ‘configure’ shell script attempts to guess correct values for -various system-dependent variables used during compilation. It uses -those values to create a ‘Makefile’ in each directory of the package. -It may also create one or more ‘.h’ files containing system-dependent -definitions. Finally, it creates a shell script ‘config.status’ that -you can run in the future to recreate the current configuration, and a -file ‘config.log’ containing output useful for debugging ‘configure’. +implications. These scripts attempt to bootstrap by building the +‘configure’ script and related files, possibly using developer tools or +the network. Because the output of bootstrapping is system-independent, +it is normally run by a package developer so that its output can be put +into the distribution tarball and ordinary builders and users need not +bootstrap. Some packages have commands like ‘./autopull.sh’ and +‘./autogen.sh’ that you can run instead of ‘./bootstrap’, for more +fine-grained control over bootstrapping. + + The ‘configure’ script attempts to guess correct values for various +system-dependent variables used during compilation. It uses those +values to create a ‘Makefile’ in each directory of the package. It may +also create one or more ‘.h’ files containing system-dependent +definitions. Finally, it creates a script ‘config.status’ that you can +run in the future to recreate the current configuration, and a file +‘config.log’ containing output useful for debugging ‘configure’. It can also use an optional file (typically called ‘config.cache’ and enabled with ‘--cache-file=config.cache’ or simply ‘-C’) that saves the @@ -64,9 +66,10 @@ editing ‘configure’ directly. 1. ‘cd’ to the directory containing the package’s source code. 2. If this is a developer checkout and file ‘configure’ does not yet - exist, type ‘./bootstrap’ to create it. You may need special - developer tools and network access to bootstrap, and the network - access may have privacy implications. + exist, run the bootstrapping script (typically ‘./bootstrap’ or + ‘./autogen.sh’) to bootstrap and create the file. You may need + special developer tools and network access to bootstrap, and the + network access may have privacy implications. 3. Type ‘./configure’ to configure the package for your system. This might take a while. While running, ‘configure’ prints messages @@ -356,7 +359,7 @@ more details. Copyright notice ================ - Copyright © 1994–1996, 1999–2002, 2004–2017, 2020–2024 Free Software + Copyright © 1994–1996, 1999–2002, 2004–2017, 2020–2025 Free Software Foundation, Inc. Copying and distribution of this file, with or without modification, diff --git a/lib/INSTALL b/lib/INSTALL index d3b6e4ec4..8c608b8f4 100644 --- a/lib/INSTALL +++ b/lib/INSTALL @@ -13,7 +13,10 @@ Basic Installation should configure, build, and install this package. The first line, which bootstraps, is intended for developers; when building from -distribution tarballs it does nothing and can be skipped. +distribution tarballs it does nothing and can be skipped. A package +might name the bootstrapping script differently; if the name is +‘autogen.sh’, for example, the first line should say ‘./autogen.sh’ +instead of ‘./bootstrap’. The following more-detailed instructions are generic; see the ‘README’ file for instructions specific to this package. Some packages @@ -25,23 +28,22 @@ found in the GNU Coding Standards. Many packages have scripts meant for developers instead of ordinary builders, as they may use developer tools that are less commonly installed, or they may access the network, which has privacy -implications. If the ‘bootstrap’ shell script exists, it attempts to -build the ‘configure’ shell script and related files, possibly using -developer tools or the network. Because the output of ‘bootstrap’ is -system-independent, it is normally run by a package developer so that -its output can be put into the distribution tarball and ordinary -builders and users need not run ‘bootstrap’. Some packages have -commands like ‘./autopull.sh’ and ‘./autogen.sh’ that you can run -instead of ‘./bootstrap’, for more fine-grained control over -bootstrapping. - - The ‘configure’ shell script attempts to guess correct values for -various system-dependent variables used during compilation. It uses -those values to create a ‘Makefile’ in each directory of the package. -It may also create one or more ‘.h’ files containing system-dependent -definitions. Finally, it creates a shell script ‘config.status’ that -you can run in the future to recreate the current configuration, and a -file ‘config.log’ containing output useful for debugging ‘configure’. +implications. These scripts attempt to bootstrap by building the +‘configure’ script and related files, possibly using developer tools or +the network. Because the output of bootstrapping is system-independent, +it is normally run by a package developer so that its output can be put +into the distribution tarball and ordinary builders and users need not +bootstrap. Some packages have commands like ‘./autopull.sh’ and +‘./autogen.sh’ that you can run instead of ‘./bootstrap’, for more +fine-grained control over bootstrapping. + + The ‘configure’ script attempts to guess correct values for various +system-dependent variables used during compilation. It uses those +values to create a ‘Makefile’ in each directory of the package. It may +also create one or more ‘.h’ files containing system-dependent +definitions. Finally, it creates a script ‘config.status’ that you can +run in the future to recreate the current configuration, and a file +‘config.log’ containing output useful for debugging ‘configure’. It can also use an optional file (typically called ‘config.cache’ and enabled with ‘--cache-file=config.cache’ or simply ‘-C’) that saves the @@ -64,9 +66,10 @@ editing ‘configure’ directly. 1. ‘cd’ to the directory containing the package’s source code. 2. If this is a developer checkout and file ‘configure’ does not yet - exist, type ‘./bootstrap’ to create it. You may need special - developer tools and network access to bootstrap, and the network - access may have privacy implications. + exist, run the bootstrapping script (typically ‘./bootstrap’ or + ‘./autogen.sh’) to bootstrap and create the file. You may need + special developer tools and network access to bootstrap, and the + network access may have privacy implications. 3. Type ‘./configure’ to configure the package for your system. This might take a while. While running, ‘configure’ prints messages diff --git a/lib/config.guess b/lib/config.guess index f6d217a49..48a684601 100755 --- a/lib/config.guess +++ b/lib/config.guess @@ -4,7 +4,7 @@ # shellcheck disable=SC2006,SC2268 # see below for rationale -timestamp='2024-01-01' +timestamp='2024-07-27' # This file is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by @@ -123,7 +123,7 @@ set_cc_for_build() { dummy=$tmp/dummy case ${CC_FOR_BUILD-},${HOST_CC-},${CC-} in ,,) echo "int x;" > "$dummy.c" - for driver in cc gcc c89 c99 ; do + for driver in cc gcc c17 c99 c89 ; do if ($driver -c -o "$dummy.o" "$dummy.c") >/dev/null 2>&1 ; then CC_FOR_BUILD=$driver break @@ -634,7 +634,8 @@ EOF sed 's/^ //' << EOF > "$dummy.c" #include - main() + int + main () { if (!__power_pc()) exit(1); @@ -718,7 +719,8 @@ EOF #include #include - int main () + int + main () { #if defined(_SC_KERNEL_BITS) long bits = sysconf(_SC_KERNEL_BITS); @@ -1621,6 +1623,7 @@ cat > "$dummy.c" <&2 exit 1 ;; - kfreebsd*-gnu*- | kopensolaris*-gnu*-) + kfreebsd*-gnu*- | knetbsd*-gnu*- | netbsd*-gnu*- | kopensolaris*-gnu*-) ;; vxworks-simlinux- | vxworks-simwindows- | vxworks-spe-) ;; @@ -1864,6 +2245,8 @@ case $kernel-$os-$obj in ;; os2-emx-) ;; + rtmk-nova-) + ;; *-eabi*- | *-gnueabi*-) ;; none--*) @@ -1890,7 +2273,7 @@ case $vendor in *-riscix*) vendor=acorn ;; - *-sunos*) + *-sunos* | *-solaris*) vendor=sun ;; *-cnk* | *-aix*) diff --git a/lib/gendocs.sh b/lib/gendocs.sh index f93e5123a..f7d862d90 100755 --- a/lib/gendocs.sh +++ b/lib/gendocs.sh @@ -2,9 +2,9 @@ # gendocs.sh -- generate a GNU manual in many formats. This script is # mentioned in maintain.texi. See the help message below for usage details. -scriptversion=2024-07-04.03 +scriptversion=2025-01-01.00 -# Copyright 2003-2024 Free Software Foundation, Inc. +# Copyright 2003-2025 Free Software Foundation, Inc. # # This program is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by @@ -73,7 +73,7 @@ texarg="-t @finalout" version="gendocs.sh $scriptversion -Copyright 2024 Free Software Foundation, Inc. +Copyright 2025-2025 Free Software Foundation, Inc. There is NO warranty. You may redistribute this software under the terms of the GNU General Public License. For more information about these matters, see the files named COPYING." diff --git a/lib/gendocs_template b/lib/gendocs_template index 277b1755d..9069a5478 100644 --- a/lib/gendocs_template +++ b/lib/gendocs_template @@ -2,7 +2,7 @@