From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2124) id 4AC1C3858C53; Fri, 5 Aug 2022 13:07:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4AC1C3858C53 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable From: Nick Clifton To: bfd-cvs@sourceware.org Subject: [binutils-gdb] Update following 2.39 release X-Act-Checkin: binutils-gdb X-Git-Author: Nick Clifton X-Git-Refname: refs/heads/master X-Git-Oldrev: 37c59664adcb87bdf3279a5919940785057fe565 X-Git-Newrev: 5ee285ca3e5cca998c76ca1c92927008849ff00e Message-Id: <20220805130717.4AC1C3858C53@sourceware.org> Date: Fri, 5 Aug 2022 13:07:17 +0000 (GMT) X-BeenThere: binutils-cvs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2022 13:07:17 -0000 https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D5ee285ca3e5c= ca998c76ca1c92927008849ff00e commit 5ee285ca3e5cca998c76ca1c92927008849ff00e Author: Nick Clifton Date: Fri Aug 5 14:07:11 2022 +0100 Update following 2.39 release Diff: --- binutils/README-how-to-make-a-release | 45 ++++++++++++++++++++++---------= ---- 1 file changed, 28 insertions(+), 17 deletions(-) diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to= -make-a-release index bdaa23dbbc0..d9eee05c452 100644 --- a/binutils/README-how-to-make-a-release +++ b/binutils/README-how-to-make-a-release @@ -207,23 +207,30 @@ When the time comes to actually make the release.... =20 21. a. Update the release number in bfd/version.m4 on the release branch to a whole new minor version number, without a point - value. Eg "2.38.90" becomes "2.39". - =20 + value. Eg "2.39.90" becomes "2.40". + b. Change bfd/development.sh to set all values to "false". - =20 + c. Regenerate the configure and makefiles. And *info* files. =20 + make all-gas all-ld all-binutils all-gprof all-gold all-gprofng + make info + =20 d. Create a ChangeLog from the git refs for all of the commits from when changelog entries were no longer required: =20 gitlog-to-changelog --since=3D2021-07-03 > ChangeLog.git + git add ChangeLog.git =20 - The gitlog-to-changelog script is part of the sources - of the "config" project. + The gitlog-to-changelog script is part of the sources + of the "config" project. =09 - e. Add ChangeLog entries for all of the updates and add a - "this-is-the-2.38-release" comment and commit. + e. Add ChangeLog entries for all of the updates and add a + "this-is-the-2.38-release" comment and commit. =20 + git commit + git push + =20 22. Check that your file creation mask will create the correct file permissions. Eg: =20 @@ -238,7 +245,7 @@ When the time comes to actually make the release.... 23. Note - check to see if any new files have been added to the top level of the source directory, but which are not in the DEVO_SUPPORT variable in the src-release.sh script. If they are - needed then add them. NB/ Add the new ChangeLog.git file. + needed then add them. =20 Create the release tarballs: =20 @@ -247,46 +254,50 @@ When the time comes to actually make the release.... 24. Check that the files in the tarballs have the correct permissions. =20 - tar tvf binutils-2.39.tar.bz2 | grep -e "---" + tar tvf binutils-*.tar.bz2 | grep -e "---" =20 Also check that the man files are not empty. (cf PR 28144). =20 - tar tvf binutils-2.39.tar.xz | grep -e "\.1" + tar tvf binutils-*.tar.xz | grep -e "\.1" =20 25. Sanity check the release on x86_64-pc-linux-gnu by building and running the testsuites (gas, gold, binutils and ld). Make the - source directory read-only before building. Also test - "make install". If necessary fix any problems. + source directory read-only before building. (Note - the gprofng + sources need a writeable doc/ directory. This is a bug that needs + to be fixed). + Also test "make install". + If necessary fix any problems. =20 pushd /dev/shm mkdir delme cd delme tar xvf /binutils-2.*.tar.lz chmod -R -w binutils-2.* + chmod +w binutils-2.*/gprofng/doc mkdir build cd build ../binutils-2.*/configure --quiet --enable-gold --prefix=3D`pwd`/install = --enable-plugins --enable-shared make all-gas all-gold all-ld all-binutils all-gprof all-gprofng make check-gas check-binutils check-ld check-gold - make install-gas install-gold install-ld install-binutils + make install-gas install-gold install-ld install-binutils install-= gprofng =20 # Needed for step 29... make html pdf =20 popd -=09 + 26. Tag the branch with the new release number: [optional: add "-u XXXXX" to sign with a gpg key] enter a tag message such as: "Official GNU Binutils 2.3x release" =20 - git tag -a binutils-2_38 -u DD9E3C4F <=3D=3D=3D Be careful to ge= t the tag right + git tag -a binutils-2_40 -u DD9E3C4F <=3D=3D=3D Be careful to ge= t the tag right =20 NB/ If you do sign the binaries make sure to use a key that has been published with the FSF. =20 Then push the release: =09 - git push origin binutils-2_3x + git push origin binutils-2_40 =20 If you get an error message along the lines of: "Invalid revision range ..." you can ignore it. @@ -308,7 +319,7 @@ When the time comes to actually make the release.... sftp sourceware.org cd /sourceware/ftp/pub/binutils/releases put binutils-2.3*.tar.* - chmod 644 binutils-2.3x.tar.* + chmod 644 binutils-2.3*.tar.* quit =20 FIXME: Are the signatures (created by the gnupload script in step 27)