<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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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-US link=blue vlink=purple><div class=WordSection1><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> rtems-devel-bounces@rtems.org [mailto:rtems-devel-bounces@rtems.org] <b>On Behalf Of </b>Ritesh Harjani<br><b>Sent:</b> Saturday, January 19, 2013 7:15 PM<br><b>To:</b> Cynthia Rempel<br><b>Cc:</b> rtems-devel@rtems.org<br><b>Subject:</b> Re: Improvements to SMP support<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Hi Cynthia<br><br>Thanks for your reponse. Please find answers to your queries inline. <o:p></o:p></p><div><p class=MsoNormal>On Sun, Jan 20, 2013 at 5:00 AM, Cynthia Rempel <<a href="mailto:cynt6007@vandals.uidaho.edu" target="_blank">cynt6007@vandals.uidaho.edu</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Hi Ritesh,<br><br>We appreciate your interest in RTEMS!<br>As you are familiar with ARM, would you be more interested in starting with the ARM port?<o:p></o:p></p><div><p class=MsoNormal><br>Sure will try my best at that. The sooner the better. Do mail me the guideline as to how should I proceed with that. <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal><br>Are you using the VM, pre-built tools, or building your own tool set?... There are different guidelines for each. <o:p></o:p></p></blockquote><div><p class=MsoNormal><br>I tried building my own tool set, but due to the error (mentioned in previous mail) couldn't proceed further. <br> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>Are you using minGW, Fedora, Ubuntu, or another type of host?<o:p></o:p></p></blockquote><div><p class=MsoNormal><br>I am using 64bit Ubuntu OS. <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal><br><br><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ritesh,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> I haven’t tried using Ubuntu for RTEMS development for a year or two but there may be native .deb packages for RTEMS development using Ubuntu available now; it was a work-in-progress last I checked.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> The method I used involved the “alien” package on Ubuntu which I used to convert Fedora .RPM packages into .DEB packages for Ubuntu. The procedure is documented on the RTEMS wiki at <a href="http://www.rtems.org/wiki/index.php/Debian_and_Ubuntu">http://www.rtems.org/wiki/index.php/Debian_and_Ubuntu</a>I haven’t tried the procedure lately but I would suggest trying the procedure given using the packages in <a href="http://www.rtems.org/ftp/pub/rtems/linux/4.11/fedora/18/x86_64/">http://www.rtems.org/ftp/pub/rtems/linux/4.11/fedora/18/x86_64/</a>.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> Compiling the tools from source is an interesting exercise but if you’re more interested in developing RTEMS itself or applications running on RTEMS (instead of building tools), it seems to me the easier path is to use pre-compiled tools whenever possible.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:16.8pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Steven G.<o:p></o:p></span></p></blockquote></div></div></div></body></html>