summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Smith <psmith@gnu.org>2023-02-26 15:52:25 -0500
committerPaul Smith <psmith@gnu.org>2023-02-26 15:52:25 -0500
commite6bd61d949df4bde73d2f7c09d09df687c9283b2 (patch)
tree3ab7d480dddf8b9e2022c371e752c66469975455
parentfcefae5ec9743c6816fd3bbc896a05526fce9230 (diff)
downloadmake-git-e6bd61d949df4bde73d2f7c09d09df687c9283b2.tar.gz
* README.git: Clarify some release steps
* README.in: Update some info and remove some obsolete notes.
-rw-r--r--README.git13
-rw-r--r--README.in23
2 files changed, 18 insertions, 18 deletions
diff --git a/README.git b/README.git
index dc445236..03125fa9 100644
--- a/README.git
+++ b/README.git
@@ -335,10 +335,15 @@ When publishing a final release there are extra steps that need to be taken:
Manage the Savannah project for GNU Make:
- * In Savannah modify the "Value", "Rank", and "Description" values for the
- current "SCM" entry in both "Component Version" and "Fix Release" fields
- to refer to the new release. The "Rank" field should be 10 less than the
- previous release so it orders properly.
+ * In Savannah edit the "Component Version" field and choose the "SCM" entry.
+ Modify the "Value", "Rank", and "Description" values for the to refer to
+ the new release. The "Rank" field should be 10 less than the previous
+ release so it orders properly.
+
+ * In Savannah edit the "Fixed Release" field and choose the "SCM" entry.
+ Modify the "Value", "Rank", and "Description" values for the to refer to
+ the new release. The "Rank" field should be 10 less than the previous
+ release so it orders properly.
* In Savannah create a new entry for the "Component Version" field:
- Value: SCM
diff --git a/README.in b/README.in
index bf4fb3d1..921c5ea3 100644
--- a/README.in
+++ b/README.in
@@ -3,11 +3,15 @@ This directory contains the @PACKAGE_VERSION@ release of @PACKAGE_NAME@.
See the file NEWS for the user-visible changes from previous releases.
In addition, there have been bugs fixed.
+>> If you are trying to build GNU Make from a Git clone rather than a
+>> downloaded source distribution, see the README.git file for instructions.
+
Please check the system-specific notes below for any caveats related to your
operating system.
-If you are trying to build GNU Make from a Git clone rather than a downloaded
-source distribution, see the README.git file for instructions.
+This README assumes you are building on a POSIX-based operating system.
+For ports to other operating systems please see the system-specific README
+files, as described in the "Ports" section below.
For source distribution building and installation instructions, see the file
INSTALL.
@@ -29,6 +33,7 @@ GNU Make is copyright by the Free Software Foundation. Copyright notices
condense sequential years into a range; e.g. "1987-1994" means all years
from 1987 to 1994 inclusive.
+
Downloading
-----------
@@ -140,16 +145,6 @@ known to be broken to be checked in. Use at your own risk.
System-specific Notes
---------------------
-It has been reported that the XLC 1.2 compiler on AIX 3.2 is buggy such
-that if you compile make with 'cc -O' on AIX 3.2, it will not work
-correctly. It is said that using 'cc' without '-O' does work.
-
-The standard /bin/sh on SunOS 4.1.3_U1 and 4.1.4 is broken and cannot be
-used to configure GNU Make. Please install a different shell such as
-bash or pdksh in order to run "configure". See this message for more
-information:
- https://mail.gnu.org/archive/html/bug-autoconf/2003-10/msg00190.html
-
One area that is often a problem in configuration and porting is the code
to check the system's current load average. To make it easier to test and
debug this code, you can do 'make check-loadavg' to see if it works
@@ -201,8 +196,8 @@ Ports
it you should start by asking on those mailing lists and forums.
Please note there are two _separate_ ports of GNU Make for Microsoft
-systems: a native Windows tool built with (for example) MSVC or Cygwin,
-and a DOS-based tool built with DJGPP. Please be sure you are looking
+systems: a native Windows port built with (for example) MSVC or MinGW,
+and a DOS-based port built with DJGPP. Please be sure you are looking
at the right README!