Recent changes to HowTo build

HowTo build modified by Eric Oberlander

Eric Oberlander — Fri, 01 Jan 2016 12:35:39 -0000

--- v10
+++ v11
@@ -37,12 +37,17 @@
 If you want to checkout a specific revision, for instance the 2.1.8 release, include the revision number:

     :::shell
-    svn checkout --revision 7813 http://svn.code.sf.net/p/ipcop/svn/ipcop/trunk
+    svn checkout --revision 7814 http://svn.code.sf.net/p/ipcop/svn/ipcop/trunk

 Or, as each version of IPCop is tagged (*release-2.1.8* in this case) so you could also export the tag:

     :::shell
     svn export http://svn.code.sf.net/p/ipcop/svn/ipcop/tags/release-2.1.8
+
+To work out the revision number of a particular release, use this example command to get the information:
+
+    :::shell
+    svn log -v --stop-on-copy http://svn.code.sf.net/p/ipcop/svn/ipcop/tags/release-2.1.5

 See the [Subversion manual](http://svnbook.red-bean.com/en/1.7/index.html) for more information on svn. Change into the trunk directory, you should now see various directories (config, doc, html, etc.) and make.sh script :

HowTo build modified by Eric Oberlander

Eric Oberlander — Thu, 31 Dec 2015 21:31:14 -0000

--- v9
+++ v10
@@ -1,4 +1,3 @@
-
 It should be possible to build IPCop on any (recent) Linux distribution. A kernel version greater or equal to 2.6.5 is required! There are 2 ways to build IPCop, with or without a prepackaged toolchain. The advantages of using a prepackaged toolchain are: less requirements on the building machine environment and timesaving.

 See __1__ below for exact package version requirements to build the toolchain.
@@ -40,7 +39,12 @@
     :::shell
     svn checkout --revision 7813 http://svn.code.sf.net/p/ipcop/svn/ipcop/trunk

-Each version of IPCop is tagged (release-2.1.8 in this case). See the [Subversion manual](http://svnbook.red-bean.com/en/1.7/index.html) for more information on svn. Change into the trunk directory, you should now see various directories (config, doc, html, etc.) and make.sh script :
+Or, as each version of IPCop is tagged (*release-2.1.8* in this case) so you could also export the tag:
+
+    :::shell
+    svn export http://svn.code.sf.net/p/ipcop/svn/ipcop/tags/release-2.1.8
+
+See the [Subversion manual](http://svnbook.red-bean.com/en/1.7/index.html) for more information on svn. Change into the trunk directory, you should now see various directories (config, doc, html, etc.) and make.sh script :

     :::shell
     cd trunk

HowTo build modified by Eric Oberlander

Eric Oberlander — Thu, 31 Dec 2015 21:24:53 -0000

--- v8
+++ v9
@@ -1,4 +1,3 @@
-

 It should be possible to build IPCop on any (recent) Linux distribution. A kernel version greater or equal to 2.6.5 is required! There are 2 ways to build IPCop, with or without a prepackaged toolchain. The advantages of using a prepackaged toolchain are: less requirements on the building machine environment and timesaving.

@@ -36,12 +35,12 @@
     :::shell
     svn checkout http://svn.code.sf.net/p/ipcop/svn/ipcop/trunk

-If you want to checkout a specific revision:
+If you want to checkout a specific revision, for instance the 2.1.8 release, include the revision number:

     :::shell
-    svn checkout --revision 555 http://svn.code.sf.net/p/ipcop/svn/ipcop/trunk
+    svn checkout --revision 7813 http://svn.code.sf.net/p/ipcop/svn/ipcop/trunk

-See the [Subversion manual](http://svnbook.red-bean.com/en/1.7/index.html) for more information on svn. Change into the trunk directory, you should now see various directories (config, doc, html, etc.) and make.sh script :
+Each version of IPCop is tagged (release-2.1.8 in this case). See the [Subversion manual](http://svnbook.red-bean.com/en/1.7/index.html) for more information on svn. Change into the trunk directory, you should now see various directories (config, doc, html, etc.) and make.sh script :

     :::shell
     cd trunk

HowTo build modified by Olaf Westrik

Olaf Westrik — Fri, 03 Oct 2014 20:29:17 -0000

--- v7
+++ v8
@@ -1,8 +1,5 @@
-The building HowTo has not been fully transferred yet.

-The not quite up-to-date description is here http://sourceforge.net/apps/trac/ipcop/wiki/BuildingHowToV2

----
 It should be possible to build IPCop on any (recent) Linux distribution. A kernel version greater or equal to 2.6.5 is required! There are 2 ways to build IPCop, with or without a prepackaged toolchain. The advantages of using a prepackaged toolchain are: less requirements on the building machine environment and timesaving.

 See __1__ below for exact package version requirements to build the toolchain.

HowTo build modified by Olaf Westrik

Olaf Westrik — Fri, 03 Oct 2014 20:27:16 -0000

--- v6
+++ v7
@@ -37,12 +37,12 @@
 Then checkout the current sources with:

     :::shell
-    svn checkout http://sourceforge.net/p/ipcop/svn/HEAD/tree/ipcop/trunk
+    svn checkout http://svn.code.sf.net/p/ipcop/svn/ipcop/trunk

 If you want to checkout a specific revision:

     :::shell
-    svn checkout --revision 555 http://sourceforge.net/p/ipcop/svn/HEAD/tree/ipcop/trunk
+    svn checkout --revision 555 http://svn.code.sf.net/p/ipcop/svn/ipcop/trunk

 See the [Subversion manual](http://svnbook.red-bean.com/en/1.7/index.html) for more information on svn. Change into the trunk directory, you should now see various directories (config, doc, html, etc.) and make.sh script :

HowTo build modified by Eric Oberlander

Eric Oberlander — Tue, 06 May 2014 12:05:51 -0000

--- v5
+++ v6
@@ -60,15 +60,15 @@

 Should some files not be available or have moved to a different URL, 'make.sh' will report an error. You might try a Google search and download files manually into the cache directory. 

-Build IPCop using prebuild toolchain
+Build IPCop using a prebuilt toolchain
 ---

-To save 30% time on building, there is the possibility to use a prebuild toolchain (42 MiB), retrieve using:
+To save 30% time on building, it is possible to use a prebuilt toolchain (42 MiB). Retrieve using:

     :::shell
     ./make.sh gettoolchain

-Using the prebuild toolchain also helps if your distro is old or very new and is not capable to create the IPCop building environment. 
+Using the prebuilt toolchain also helps if your distro is old or very new, and is not capable of creating the IPCop building environment.

HowTo build modified by Olaf Westrik

Olaf Westrik — Tue, 06 May 2014 11:46:40 -0000

--- v4
+++ v5
@@ -50,7 +50,29 @@
     cd trunk
     ls

+Retrieve other sources
+---
+    
+Load all files from all the different sources on the Internet 

+    :::shell
+    ./make.sh prefetch
+
+Should some files not be available or have moved to a different URL, 'make.sh' will report an error. You might try a Google search and download files manually into the cache directory. 
+
+Build IPCop using prebuild toolchain
+---
+
+To save 30% time on building, there is the possibility to use a prebuild toolchain (42 MiB), retrieve using:
+
+    :::shell
+    ./make.sh gettoolchain
+
+Using the prebuild toolchain also helps if your distro is old or very new and is not capable to create the IPCop building environment. 
+
+
+
+---
 1: Package versions required to build the toolchain

 Package | Version
@@ -76,3 +98,29 @@

 2: Build as root
+
+You will need to write these values in a .config file at ./make.sh directory level.
+
+~~~~~~
+# Default value
+NICE=10
+
+# How many concurrent jobs to run (NOTE: Don't use too high a value, or packages may have timing issues.
+# At least openssh fails if this is too high.  It's safe to set this to number of CPUs + 1)
+PARALLELISM=3
+
+# How many times should prefetch try to download a package. Don't set to too high a value and hammer sites
+MAX_RETRIES=3
+
+# Make distcc optional, by default don't use it.
+# To be efficient, distcc need that network is more efficient than local cpu
+# Gain is usually small unless cpu are not fast
+USE_DISTCC=no
+
+# Should we skip creation of USB images
+# This saves time if you only want to use PXE or CD installation
+SKIP_USB_IMAGES=yes
+
+# If you **absolutely** want to build ipcop as root,STRONGLY DISCOURAGED
+ALLOW_ROOT_TO_BUILD=yes
+~~~~~~

HowTo build modified by Olaf Westrik

Olaf Westrik — Tue, 06 May 2014 11:31:36 -0000

--- v3
+++ v4
@@ -1,3 +1,78 @@
-The building HowTo has not been transferred yet.
+The building HowTo has not been fully transferred yet.

 The not quite up-to-date description is here http://sourceforge.net/apps/trac/ipcop/wiki/BuildingHowToV2
+
+---
+It should be possible to build IPCop on any (recent) Linux distribution. A kernel version greater or equal to 2.6.5 is required! There are 2 ways to build IPCop, with or without a prepackaged toolchain. The advantages of using a prepackaged toolchain are: less requirements on the building machine environment and timesaving.
+
+See __1__ below for exact package version requirements to build the toolchain.
+
+Please observe that there is currently no cross-compilation support, i.e. if you want to build IPCop for Sparc you will need a Sparc machine.
+
+Examples below are from Debian Lenny but build environment is not limited to Debian. 
+
+Prepare building environment
+---
+
+As of SVN [r842] it is no longer necessary to build IPCop as root. You will need sudo installed. You need to copy in /etc/sudoers (using visudo is recommended) the lines indicated on first ./make.sh build. See __2__ below how to build as root, please note that it strongly recommended to build as non-root! 
+
+These are the minimum packages required when a prepackaged toolchain is available.
+
+    :::shell
+    apt-get install build-essential realpath sudo
+
+More packages are needed to build the toolchain (see later), realpath and build-essential are debian specific. On other distributions, build-essential could be have other names like development packages (gcc, libc headers, make,...). On opensuse-11.3 for example, it is required to install
+
+    :::shell
+    zypper install bison gcc make texinfo
+
+Retrieve IPCop sources
+---
+
+Sources are available from [SVN](http://sourceforge.net/p/ipcop/svn/HEAD/tree/ipcop/trunk)). This is the recommended way as it is easier to follow changes on the source tree. You will need the subversion package, install on Debian Lenny using (see [4] for other distros):
+
+    :::shell
+    apt-get install subversion
+
+Then checkout the current sources with:
+
+    :::shell
+    svn checkout http://sourceforge.net/p/ipcop/svn/HEAD/tree/ipcop/trunk
+
+If you want to checkout a specific revision:
+
+    :::shell
+    svn checkout --revision 555 http://sourceforge.net/p/ipcop/svn/HEAD/tree/ipcop/trunk
+
+See the [Subversion manual](http://svnbook.red-bean.com/en/1.7/index.html) for more information on svn. Change into the trunk directory, you should now see various directories (config, doc, html, etc.) and make.sh script :
+
+    :::shell
+    cd trunk
+    ls
+
+
+1: Package versions required to build the toolchain
+
+Package | Version
+-----|-----
+bash | 2.05a
+binutils | 2.12
+bison | 1.875
+bzip2 | 1.0.2
+coreutils | 5.0
+diffutils | 2.8
+findutils | 4.1.20
+gawk | 3.1.5
+gcc | 3.0.1
+glibc | 2.2.5
+grep | 2.5
+gzip | 1.2.4
+linux kernel | 2.6.5
+make | 3.79.1
+patch | 2.5.4
+sed | 3.0.2
+tar | 1.14
+texinfo | 4.8
+
+
+2: Build as root

HowTo build modified by Eric Oberlander

Eric Oberlander — Mon, 10 Mar 2014 16:24:01 -0000

--- v2
+++ v3
@@ -1,3 +1,3 @@
-The building HowTo is not transfered yet.
+The building HowTo has not been transferred yet.

-The not quit-up-to-date description is here http://sourceforge.net/apps/trac/ipcop/wiki/BuildingHowToV2
+The not quite up-to-date description is here http://sourceforge.net/apps/trac/ipcop/wiki/BuildingHowToV2

HowTo build modified by Olaf Westrik

Olaf Westrik — Mon, 10 Mar 2014 16:12:54 -0000

--- v1
+++ v2
@@ -1,3 +1,3 @@
 The building HowTo is not transfered yet.

-The now quit-up-to-date description is here http://sourceforge.net/apps/trac/ipcop/wiki/BuildingHowToV2
+The not quit-up-to-date description is here http://sourceforge.net/apps/trac/ipcop/wiki/BuildingHowToV2