SheepShaver V2.2 Installation and User's Guide (Linux)

Back to index

Patching the source code

In order to keep up with recent development you could consider patching the source code with patches as they come available.
Files needed for patching can be found here. In our case (SheepShaver) patches are sometimes written to get pieces of software running, although not good enough to be added to the stable source.

• Please keep in mind that the patches you find may, or may not, have been incorporated in the rpm or source code you downloaded earlier.
   
• Patching basically means applying changes to the source code that have not yet been submitted to the CVS (concurrent versioning system) or the source or RPM packages.
   
•  There is no way to be certain about whether a patch has been incorporated in the distribution, but to examine the source code in the files on your machine, or look at the development archives or other messages form the developers.
   
• A rule of thumb is that patches older than the source code or RPM have been added. However, this is not always so. 

Below you will find remarks about how to apply patches in a general way.
Further down there is a example of a script you could use for automating the patch commands.

General remarks:

Patching the code is done through the "patch" command. Familiarise yourself with the syntax. The patch command takes several parameters, like an input file, and some directives about how to handle the patch. The input file is created with the "diff" command that lists the differenced between two files on the developers machine. You can use the .diff file to change the file on your machine accordingly. Remember the extension of the resulting file does not have to be ".diff" You can see an example of this in the script below.

• Example patch command line:
  
  "patch -p0 -i /cvs/patches/sheep_ethernet.diff"
   
• What this means:
  
  "patch":    starts the patch command.
  "-p0"   :    give patch a directive to start looking for the target file in the path specified in the diff file. (-p1 would subtract the first path entry in the diff file, and so on)
  "-i"      :    the patch info is read from the following file.
  "/cvs/patches/sheep_ethernet.diff" :  tells patch where to find the input file.

A sample script to download, patch, compile and run SheepShaver:
(you will need a password to download, it is: anoncvs)

mkdir /cvs
cd /cvs
mkdir patches

cvs -d :pserver:anoncvs@down.physik.uni-mainz.de:/cvs login
cvs -d :pserver:anoncvs@down.physik.uni-mainz.de:/cvs checkout BasiliskII
cvs -d :pserver:anoncvs@down.physik.uni-mainz.de:/cvs checkout SheepShaver

cd /cvs/patches

wget http://gwenole.beauchesne.free.fr/sheepshaver/files/SheepShaver-2.2-hacks.patch
wget http://gwenole.beauchesne.free.fr/sheepshaver/patches/sheep_ethernet.diff

cd /cvs/SheepShaver/src/
patch -p0 -i /cvs/patches/sheep_ethernet.diff

cd /cvs/SheepShaver
patch -p1 -i /cvs/patches/SheepShaver-2.2-hacks.patch

cd /cvs/SheepShaver
make links
cd src/Unix
./autogen.sh
make
./SheepShaver
 

Explanation of the script:
The script creates some directories to download the source code and patches in, it then downloads the sources from CVS and gets the patches you want.
Next, it uses the patch command to apply the patches to the downloaded code. Finally it performs the compilation routine and calls SheepShaver to start.

In order to use the script make the file executable and run it in a terminal window


Figure 1: making the script executable

You can change the script to your liking, whenever changes to patches are coming about.