<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:24.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:18.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Times New Roman","serif";
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Times New Roman","serif";
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-IN" link="blue" vlink="purple">
<div class="Section1">
<h1><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";
color:black;font-weight:normal">Hi all,<o:p></o:p></span></h1>
<p class="MsoNormal"><b><span style="font-size:14.0pt;color:black"> </span>
</b><span style="font-size:12.0pt;color:black">I got the below cross compilation procedure for dhcp from</span><b><span style="font-size:14.0pt;color:black">
</span></b><cite><span style="font-family:"Calibri","sans-serif";font-style:normal"><a href="http://www.hurricane.at/howtos/dhcp-cross.html%20.%20">www.hurricane.at/howtos/dhcp-<b>cross</b>.html .
</a><o:p></o:p></span></cite></p>
<p class="MsoNormal" style="text-indent:36.0pt"><cite><span style="font-size:
12.0pt;font-family:"Calibri","sans-serif";font-style:normal">Actually
</span></cite><cite><span style="font-size:12.0pt;font-family:"Calibri","sans-serif";font-style:normal"> this compliation for power pc platform.
<o:p></o:p></span></cite></p>
<p class="MsoNormal"><cite><span style="font-size:12.0pt;font-family:"Calibri","sans-serif";
font-style:normal"> I would like to know , whether i can follow the same procedure for armv5b compiler.<o:p></o:p></span></cite></p>
<p class="MsoNormal"><cite><span style="font-size:12.0pt;font-family:"Calibri","sans-serif";
font-style:normal"> Otherwise there is any other separate dhcp cross compiler procedure for ISC DHCP using armv5b compiler.</span></cite><span style="font-size:12.0pt"><o:p></o:p></span></p>
<h1><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";
color:black"><o:p> </o:p></span></h1>
<h1><span style="color:black">DHCP Cross-compile How-To<o:p></o:p></span></h1>
<p><span style="font-size:13.5pt;color:black"><br>
Author: <a href="mailto:mgorjup@hurricane.at">Matthias Gorjup</a> <br>
Last Update: 9th Feb 2003<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">This document describes how to cross-compile DHCP package, provided by Internet <br>
Software Consortium (<a href="http://www.hurricane.at/howtos/www.isc.org">www.isc.org</a>), for power pc platform. <br>
<o:p></o:p></span></p>
<h2><span style="color:black">1. Getting the package<o:p></o:p></span></h2>
<p><span style="font-size:13.5pt;color:black"><br>
Get the latest package from <a href="http://www.isc.org/products/DHCP/">http://www.isc.org/products/DHCP/</a> (at the time <br>
of writing it is dhcp-3.0pl2.tar.gz) and untar it to your home directory:<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">> cd /home/gorjup <br>
> tar xzvf dhcp-3.0pl2.tar.gz <br>
<o:p></o:p></span></p>
<h2><span style="color:black">2. Cross-compiling<o:p></o:p></span></h2>
<p><span style="font-size:13.5pt;color:black"><br>
After you have installed your development kit (I used DTDK-0.3 toolchain, built by <br>
Markus Haag ), set the proper environment variables:<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">> export CROSS_COMPILE=ppc-linux- <br>
> PATH=$PATH:/opt/dtdk-0.3/mpc860/bin <br>
> export CC=ppc-linux-gcc <br>
> export AR=ppc-linux-ar <br>
> export STRIP=ppc-linux-strip <br>
> export RANLIB=ppc-linux-ranlib <br>
> export LD=ppc-linux-ld <br>
> export NM=ppc-linux-nm<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">Go to the dhcp directory and configure the dhcp package:<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">> cd /home/gorjup/dhcp-3.0pl2 <br>
> ./configure<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">Now a new directory, named work.linux-2.2, has been created. Go to this directory <br>
and edit Makefiles. In all makefiles (in the main one and in all the subdirectories) <br>
you need to do some changes:<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">> cd work.linux-2.2<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">- add the destination directory for cross-compiled files and man pages:<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">DESTDIR = /home/gorjup/target_ppc_dhcp<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">- change line, beginning with RANLIB:<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">- RANLIB = ranlib <br>
+ RANLIB = ppc-linux-ranlib<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">- add the definition for CC variable: <br>
+ CC = ppc-linux-gcc<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">In following makefiles: <br>
common/Makefile, dhcpctl/Makefile, dst/Makefile, minires/Makefile and omapip/Makefile <br>
you need to replace ar binutility with ppc-linux-ar. <br>
You find ar binutility at the end of Makefiles. <br>
Now cross-compile the package:<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">> make <br>
> make install<o:p></o:p></span></p>
<p><span style="font-size:13.5pt;color:black">At the end you can strip the binaries by using ppc-linux-strip. <br>
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<P><strong><span style='font-size:10.0pt;font-family:
"Palatino Linotype","serif";color:green'> Please do not print this email unless it is absolutely necessary. </span></strong><span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
<p> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. </p>
<p>WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. </p>
<p>
www.wipro.com
</p>
</body>
</html>