CONFIDENTIAL
Z3-DM8169-APP-L1-RPS V2.01.10
___________________________________________________________________________________________
Z3 Technology, LLC
♦
100 N 8
th
ST, STE 250
♦
Lincoln, NE 68508-1369 USA
♦
+1.402.323.0702
7
3.
Untarring and Building the Sample Code
3.1 Preparing the Linux Environment
Prior to building the Z3 sample code, certain modules are required. In Ubuntu 10.x or later, the following
command can be used to get the required modules:
sudo apt-get install bison flex mtd-utils liblzo2-dev uuid-dev zlib1g-dev
libpcre3-dev autoconf autoconf-archive automake automake1.9 automake1.9-doc
libtool libtool-doc
In Fedora, the command would be:
sudo yum install bison flex mtd-utils mtd-utils-ubi lzo-devel libuuid-devel
pcre-devel automake automake17 automake14 autoconf libtool
If you are running a 64-bit OS, it may be necessary to install some 32-bit libraries for the cross-compiling
toolchain. You can determine whether your OS is 64-bit by using the “uname –p” command. A 64-bit OS
will return “x86_64,” while a 32-bit OS will return “i386”, “i586”, or “i686”.
For 64-bit Ubuntu, you can get the necessary libraries by typing:
# sudo apt-get install ia32-libs
For 64-bit Fedora, you can type:
# sudo yum install glibc.i686
3.2
Making the Directories and Running the Make Script
The software provided will allow you to re-create the pre-installed software of the Z3-DM8169-L1-RPS
starting from the included source code.
On a PC running Linux, create a directory where the released materials are going to be located:
# mkdir /home/z3/z3-netra-rdk
Copy the released tar archive to that directory (note: the name may slightly vary).
# cp SW-7R2-00199-01_DM8169-APP-L1-RPS-SRC-20140409.tar.bz2 /home/z3/z3-netra-rdk
Untar the archive (name of tar file may slightly vary. Untarring will take 5 to 10 minutes).
# tar -xvjf SW-7R2-00199-01_DM8169-APP-L1-RPS-SRC-20140409.tar.bz2
Then go into the directory just created and run the build script (directory name may slightly vary):
# cd z3-netra-RDK-20140409
# ./makeall
Note: Building can take around 30-40 minutes. You will also need to type in the sudo password a few
times toward the end of the build.
The outcome of the build process should be newly created image files in the images directory.