From Fedora Project Wiki

No edit summary
No edit summary
Line 9: Line 9:
Follow these steps:
Follow these steps:


   1. Make sure that your clones of the upstream GNU Binutils and the Fedora rawhide binutils are up to date on the right branch and clean.  If there any problems or uncommitted changes, resolve them before continuing.
   1. Make sure that your clones of the upstream GNU Binutils is up to date, on the right branch and clean.  If there any problems or uncommitted changes, resolve them before continuing.


   <pre>
   <pre>
   cd <upstream-binutils> ; git switch HEAD ; git pull ; git status
   cd <upstream-binutils> ; git switch HEAD ; git pull ; git status
  cd <rawhide-binutils>  ; git switch rawhide ; git pull ; git status
   </pre>
   </pre>


Line 22: Line 21:
   </pre>
   </pre>


  3. Copy the tarball into the fedora sources, adding in a date string:
  3. Copy the tarball into the fedora sources, replacing the version number with a commit id.


   <pre>
   <pre>
Line 29: Line 28:


   4.
   4.
cd <rawhide-binutils>  ; git switch rawhide ; git pull ; git status

Revision as of 17:13, 20 February 2024

Rawhide synchronization for the GNU Binutils

  • THIS PAGE IS UNDER DEVELOPMENT AND SHOULD NOT BE CONSIDERED READY FOR USE*

This page documents the process by which the rawhide binutils package is synced with the upstream GNU Binutils project. The aim of this process is to make syncing simple and easy so that it can be performed on a regular basis. Due to the fact that the binutils is an important component in the toolchain used to build many of the packages in rawhide however, it is important to extensively test a new binutils before putting it into the buildroot. This does make the syncing process more time consuming and complicated.

This process is based upon a similar process for the GNU C Library (GlibcRawhideSync), but tweaked to fit the binutils package.

Follow these steps:

 1. Make sure that your clones of the upstream GNU Binutils is up to date, on the right branch and clean.  If there any problems or uncommitted changes, resolve them before continuing.
  cd <upstream-binutils> ; git switch HEAD ; git pull ; git status
  
 2. Create a source tarball from the upstream sources:
  cd <upstream-binutils> ; rm -f *.xz ; ./src-release -x binutils 
  
3. Copy the tarball into the fedora sources, replacing the version number with a commit id. 
  cp binutils*.xz <rawhide-binutils>/binutils-`date =%F`.tar.xz
  
 4.

cd <rawhide-binutils>  ; git switch rawhide ; git pull ; git status