Installation query

Joel Sherrill joel.sherrill at oarcorp.com
Fri Aug 7 18:05:19 UTC 2015



On 8/7/2015 11:40 AM, Donald H Locker wrote:
> Thank you for this, Joel. Can you please clarify the directory structure?
>
> My understanding is that the non-prefixed directories are sub-dirs of the first, i.e. the structure is:
>
>      ~/rtems-4.11-work
>      ~/rtems-4.11-work/tools
>      ~/rtems-4.11-work/bsp-install
>      ~/rtems-4.11-work/rtems
>      ~/rtems-4.11-work/b-pc386
>
> Is this a correct interpretation?

Yes. But that is just my working environment. It is not the only
way to do it. :)

The important thing is that the BSP install point be separate from
the rtems source or build directories.

It may or may not be the same as the tools installation. Personal
or project preference.

> Thank you again,
> Donald.
>
> ----- Original Message -----
>> From: "Joel Sherrill" <joel.sherrill at oarcorp.com>
>> To: "Sarvesh Patkar" <sarveshspatkar at gmail.com>, users at rtems.org
>> Sent: Friday, August 7, 2015 11:32:56 AM
>> Subject: Re: Installation query
>>
>>
>>
>> On 8/7/2015 9:33 AM, Sarvesh Patkar wrote:
>>> Hey guys,
>>>
>>> I am a newbie. So, I am having a lot of doubts and issues in understanding
>>> while installation. I deleted all that I had installed till yesterday and
>>> started over. I executed the following commands.
>>>
>>> mkdir -p development/rtems/src
>>> cd development/rtems/src
>>> git clone git://git.rtems.org/rtems-source-builder.git
>>> <http://git.rtems.org/rtems-source-builder.git>
>>> cd rtems-source-builder
>>> source-builder/sb-check
>>> cd rtems
>>> ../source-builder/sb-set-builder --log=l-pc386.txt
>>> --prefix=/home/sarvesh/development/rtems/4.11 4.11/rtems-i386
>>> /home/sarvesh/development/rtems/4.11/bin/i386-rtems4.11-gcc -v
>>> git clone git://git.rtems.org/rtems.git <http://git.rtems.org/rtems.git>
>>> cd rtems
>>> export PATH=/home/sarvesh/development/rtems/4.11/bin:$PATH
>>> ./bootstrap
>>> cd ..
>>> mkdir pc386
>>> mkdir pc386/install
>>
>> Your install directory should not be under the build directory.
>> They should be separate.
>>
>>> cd pc386
>>> ../rtems/configure --target=i386-rtems4.11 --enable-rtremsbsp=pc386
>>> --enable-tests=samples --disable-posix
>>> --prefix=/home/sarvesh/development/rtems/4.11/pc386/install
>>                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> You spelled the option incorrectly. It is "--enable-rtemsbsp=pc386"
>>
>> As a point of reference, I have this (more or less) as my tree structure.
>>
>> ~/rtems-4.11-work
>>      tools
>>      bsp-install
>>      rtems
>>      b-pc386
>>
>> There is no obligation or requirement to do it that way. All BSPs can be
>> installed into a single directory safely. And it could be the same as the
>> tools directory.
>>
>> b-pc386 can be removed after the installation.
>>
>>> make
>>>
>>> This is what happened at the very end of executing 'make'.
>>> Rest of it seemed all correct.
>>>
>>> Making all in edison
>>> make[2]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c/edison'
>>> make[2]: *** No rule to make target `all'.  Stop.
>>> make[2]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c/edison'
>>> make[1]: *** [all-recursive] Error 1
>>> make[1]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'
>>> make: *** [all-recursive] Error 1
>>>
>>>
>>> I also tried running the next command according to the Quick Start page
>>> sudo PATH=/home/sarvesh/development/rtems/4.11/bin:${PATH} make install
>>>
>>> This is what followed.
>>>
>>> Making install in tools/build
>>> make[1]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/build'
>>> make[2]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/build'
>>>    /bin/mkdir -p '/home/sarvesh/development/rtems/4.11/pc386/install/bin'
>>>     /usr/bin/install -c cklength eolstrip packhex unhex rtems-bin2c
>>>     '/home/sarvesh/development/rtems/4.11/pc386/install/bin'
>>>    /bin/mkdir -p '/home/sarvesh/development/rtems/4.11/pc386/install/bin'
>>>    /usr/bin/install -c install-if-change
>>>    '/home/sarvesh/development/rtems/4.11/pc386/install/bin'
>>> make[2]: Nothing to be done for `install-data-am'.
>>> make[2]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/build'
>>> make[1]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/build'
>>> Making install in tools/cpu
>>> make[1]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'
>>> Making install in generic
>>> make[2]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu/generic'
>>> make[3]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu/generic'
>>> make[3]: Nothing to be done for `install-exec-am'.
>>> make[3]: Nothing to be done for `install-data-am'.
>>> make[3]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu/generic'
>>> make[2]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu/generic'
>>> make[2]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'
>>> make[3]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'
>>> make[3]: Nothing to be done for `install-exec-am'.
>>> make[3]: Nothing to be done for `install-data-am'.
>>> make[3]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'
>>> make[2]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'
>>> make[1]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/tools/cpu'
>>> Making install in testsuites/tools
>>> make[1]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'
>>> Making install in generic
>>> make[2]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools/generic'
>>> make[3]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools/generic'
>>>    /bin/mkdir -p '/home/sarvesh/development/rtems/4.11/pc386/install/bin'
>>>    /usr/bin/install -c difftest
>>>    '/home/sarvesh/development/rtems/4.11/pc386/install/bin/./i386-rtems4.11-difftest'
>>>    /usr/bin/install -c sorttimes
>>>    '/home/sarvesh/development/rtems/4.11/pc386/install/bin/./i386-rtems4.11-sorttimes'
>>> make[3]: Nothing to be done for `install-data-am'.
>>> make[3]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools/generic'
>>> make[2]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools/generic'
>>> make[2]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'
>>> make[3]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'
>>> make[3]: Nothing to be done for `install-exec-am'.
>>> make[3]: Nothing to be done for `install-data-am'.
>>> make[3]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'
>>> make[2]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'
>>> make[1]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/testsuites/tools'
>>> Making install in i386-rtems4.11/c
>>> make[1]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'
>>> Making install in .
>>> make[2]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'
>>> make[3]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'
>>> make[3]: Nothing to be done for `install-exec-am'.
>>> make[3]: Nothing to be done for `install-data-am'.
>>> make[3]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'
>>> make[2]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'
>>> *Making install in edison
>>> make[2]: Entering directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c/edison'
>>> make[2]: *** No rule to make target `install'.  Stop.
>>> make[2]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c/edison'
>>> make[1]: *** [install-recursive] Error 1
>>> make[1]: Leaving directory
>>> `/home/sarvesh/development/rtems/src/rtems-source-builder/rtems/pc386/i386-rtems4.11/c'
>>> make: *** [install-recursive] Error 1
>>>
>>> *
>>> Can you please help me understand why this may be happening and how it can
>>> be overcome?
>>>
>>> Thank you,
>>>
>>> Sarvesh Patkar
>>>
>>>
>>
>> --
>> Joel Sherrill, Ph.D.             Director of Research & Development
>> joel.sherrill at OARcorp.com        On-Line Applications Research
>> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>> Support Available                (256) 722-9985
>> _______________________________________________
>> users mailing list
>> users at rtems.org
>> http://lists.rtems.org/mailman/listinfo/users
>>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985


More information about the users mailing list