<div dir="ltr"><div>If there aren't any errors or warnings, I believe you are good to try your hands at the hello or ticker sample. <br></div>To simulate i386, you should prefer QEMU.<br><pre class="wiki"><span style="font-family:arial,helvetica,sans-serif">qemu-system-i386 -kernel <your-executable-file><br><br>you can also try the examples-v2 repository. There are lot of examples for someone to begin with.<br></span></pre><pre class="wiki"><span style="font-family:arial,helvetica,sans-serif">export the RTEMS_MAKEFILE_PATH variable to </span><span style="font-family:arial,helvetica,sans-serif">INSTALL_POINT/i386-rtems4.11/pc386</span></pre><pre class="wiki"><span style="font-family:arial,helvetica,sans-serif">, where INSTALL_POINT is where you installed your bsp, and then a make will build the examples.</span> <br></pre></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 8, 2015 at 1:42 AM, Sarvesh Patkar <span dir="ltr"><<a href="mailto:sarveshspatkar@gmail.com" target="_blank">sarveshspatkar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks for the quick replies. I tried it as you said. I realised the typo. How can I be sure of whether it happened correctly now? (I didn't see the warnings this time) </div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 7, 2015 at 1:05 PM, Joel Sherrill <span dir="ltr"><<a href="mailto:joel.sherrill@oarcorp.com" target="_blank">joel.sherrill@oarcorp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
<br>
On 8/7/2015 11:40 AM, Donald H Locker wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thank you for this, Joel. Can you please clarify the directory structure?<br>
<br>
My understanding is that the non-prefixed directories are sub-dirs of the first, i.e. the structure is:<br>
<br>
~/rtems-4.11-work<br>
~/rtems-4.11-work/tools<br>
~/rtems-4.11-work/bsp-install<br>
~/rtems-4.11-work/rtems<br>
~/rtems-4.11-work/b-pc386<br>
<br>
Is this a correct interpretation?<br>
</blockquote>
<br></span>
Yes. But that is just my working environment. It is not the only<br>
way to do it. :)<br>
<br>
The important thing is that the BSP install point be separate from<br>
the rtems source or build directories.<br>
<br>
It may or may not be the same as the tools installation. Personal<br>
or project preference.<div><div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thank you again,<br>
Donald.<br>
<br>
----- Original Message -----<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
From: "Joel Sherrill" <<a href="mailto:joel.sherrill@oarcorp.com" target="_blank">joel.sherrill@oarcorp.com</a>><br>
To: "Sarvesh Patkar" <<a href="mailto:sarveshspatkar@gmail.com" target="_blank">sarveshspatkar@gmail.com</a>>, <a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br>
Sent: Friday, August 7, 2015 11:32:56 AM<br>
Subject: Re: Installation query<br>
<br>
<br>
<br>
On 8/7/2015 9:33 AM, Sarvesh Patkar wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey guys,<br>
<br>
I am a newbie. So, I am having a lot of doubts and issues in understanding<br>
while installation. I deleted all that I had installed till yesterday and<br>
started over. I executed the following commands.<br>
<br>
mkdir -p development/rtems/src<br>
cd development/rtems/src<br>
git clone git://<a href="http://git.rtems.org/rtems-source-builder.git" rel="noreferrer" target="_blank">git.rtems.org/rtems-source-builder.git</a><br>
<<a href="http://git.rtems.org/rtems-source-builder.git" rel="noreferrer" target="_blank">http://git.rtems.org/rtems-source-builder.git</a>><br>
cd rtems-source-builder<br>
source-builder/sb-check<br>
cd rtems<br>
../source-builder/sb-set-builder --log=l-pc386.txt<br>
--prefix=/home/sarvesh/development/rtems/4.11 4.11/rtems-i386<br>
/home/sarvesh/development/rtems/4.11/bin/i386-rtems4.11-gcc -v<br>
git clone git://<a href="http://git.rtems.org/rtems.git" rel="noreferrer" target="_blank">git.rtems.org/rtems.git</a> <<a href="http://git.rtems.org/rtems.git" rel="noreferrer" target="_blank">http://git.rtems.org/rtems.git</a>><br>
cd rtems<br>
export PATH=/home/sarvesh/development/rtems/4.11/bin:$PATH<br>
./bootstrap<br>
cd ..<br>
mkdir pc386<br>
mkdir pc386/install<br>
</blockquote>
<br>
Your install directory should not be under the build directory.<br>
They should be separate.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
cd pc386<br>
../rtems/configure --target=i386-rtems4.11 --enable-rtremsbsp=pc386<br>
--enable-tests=samples --disable-posix<br>
--prefix=/home/sarvesh/development/rtems/4.11/pc386/install<br>
</blockquote>
^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
<br>
You spelled the option incorrectly. It is "--enable-rtemsbsp=pc386"<br>
<br>
As a point of reference, I have this (more or less) as my tree structure.<br>
<br>
~/rtems-4.11-work<br>
tools<br>
bsp-install<br>
rtems<br>
b-pc386<br>
<br>
There is no obligation or requirement to do it that way. All BSPs can be<br>
installed into a single directory safely. And it could be the same as the<br>
tools directory.<br>
<br>
b-pc386 can be removed after the installation.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
make<br>
<br>
This is what happened at the very end of executing 'make'.<br>
Rest of it seemed all correct.<br>
<br>
Making all in edison<br>
make[2]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c/edison'<br>
make[2]: *** No rule to make target `all'. Stop.<br>
make[2]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c/edison'<br>
make[1]: *** [all-recursive] Error 1<br>
make[1]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'<br>
make: *** [all-recursive] Error 1<br>
<br>
<br>
I also tried running the next command according to the Quick Start page<br>
sudo PATH=/home/sarvesh/development/rtems/4.11/bin:${PATH} make install<br>
<br>
This is what followed.<br>
<br>
Making install in tools/build<br>
make[1]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/build'<br>
make[2]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/build'<br>
/bin/mkdir -p '/home/sarvesh/development/rtems/4.11/pc386/install/bin'<br>
/usr/bin/install -c cklength eolstrip packhex unhex rtems-bin2c<br>
'/home/sarvesh/development/rtems/4.11/pc386/install/bin'<br>
/bin/mkdir -p '/home/sarvesh/development/rtems/4.11/pc386/install/bin'<br>
/usr/bin/install -c install-if-change<br>
'/home/sarvesh/development/rtems/4.11/pc386/install/bin'<br>
make[2]: Nothing to be done for `install-data-am'.<br>
make[2]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/build'<br>
make[1]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/build'<br>
Making install in tools/cpu<br>
make[1]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'<br>
Making install in generic<br>
make[2]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu/generic'<br>
make[3]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu/generic'<br>
make[3]: Nothing to be done for `install-exec-am'.<br>
make[3]: Nothing to be done for `install-data-am'.<br>
make[3]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu/generic'<br>
make[2]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu/generic'<br>
make[2]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'<br>
make[3]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'<br>
make[3]: Nothing to be done for `install-exec-am'.<br>
make[3]: Nothing to be done for `install-data-am'.<br>
make[3]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'<br>
make[2]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'<br>
make[1]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'<br>
Making install in testsuites/tools<br>
make[1]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'<br>
Making install in generic<br>
make[2]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools/generic'<br>
make[3]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools/generic'<br>
/bin/mkdir -p '/home/sarvesh/development/rtems/4.11/pc386/install/bin'<br>
/usr/bin/install -c difftest<br>
'/home/sarvesh/development/rtems/4.11/pc386/install/bin/./i386-rtems4.11-difftest'<br>
/usr/bin/install -c sorttimes<br>
'/home/sarvesh/development/rtems/4.11/pc386/install/bin/./i386-rtems4.11-sorttimes'<br>
make[3]: Nothing to be done for `install-data-am'.<br>
make[3]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools/generic'<br>
make[2]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools/generic'<br>
make[2]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'<br>
make[3]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'<br>
make[3]: Nothing to be done for `install-exec-am'.<br>
make[3]: Nothing to be done for `install-data-am'.<br>
make[3]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'<br>
make[2]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'<br>
make[1]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'<br>
Making install in i386-rtems4.11/c<br>
make[1]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'<br>
Making install in .<br>
make[2]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'<br>
make[3]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'<br>
make[3]: Nothing to be done for `install-exec-am'.<br>
make[3]: Nothing to be done for `install-data-am'.<br>
make[3]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'<br>
make[2]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'<br>
*Making install in edison<br>
make[2]: Entering directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c/edison'<br>
make[2]: *** No rule to make target `install'. Stop.<br>
make[2]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c/edison'<br>
make[1]: *** [install-recursive] Error 1<br>
make[1]: Leaving directory<br>
`/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'<br>
make: *** [install-recursive] Error 1<br>
<br>
*<br>
Can you please help me understand why this may be happening and how it can<br>
be overcome?<br>
<br>
Thank you,<br>
<br>
Sarvesh Patkar<br>
<br>
<br>
</blockquote>
<br>
--<br>
Joel Sherrill, Ph.D. Director of Research & Development<br>
joel.sherrill@OARcorp.com On-Line Applications Research<br>
Ask me about RTEMS: a free RTOS Huntsville AL 35805<br>
Support Available <a href="tel:%28256%29%20722-9985" value="+12567229985" target="_blank">(256) 722-9985</a><br>
_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
<br>
</blockquote>
_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
<br>
</blockquote>
<br>
-- <br>
Joel Sherrill, Ph.D. Director of Research & Development<br>
joel.sherrill@OARcorp.com On-Line Applications Research<br>
Ask me about RTEMS: a free RTOS Huntsville AL 35805<br>
Support Available <a href="tel:%28256%29%20722-9985" value="+12567229985" target="_blank">(256) 722-9985</a><br>
_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br></blockquote></div><br></div>