[GSOC] How to fix this path problem?

[Joel Sherrill]

On 06/20/2012 10:11 AM, Gedare Bloom wrote:
> On Wed, Jun 20, 2012 at 9:25 AM, Joel Sherrill
> <joel.sherrill at oarcorp.com>  wrote:
>> On 06/19/2012 09:52 PM, Xiaochen Pan wrote:
>>> Thank you very much.
>>>
>>> I have used the virtual machine image of centos and rebuilt and
>>> reinstalled the rtems according to the webpage.
>>>
>>> After I have reinstalled it, I want to build the testsuites  in the rtems
>>> directory from the start, aka, configure and make, even though there are  '
>>> .exe' files already produced by the installation process.
>>>
> Does it make sense to be building the testsuites from outside of the
> primary RTEMS build? They were not designed to do this so you might
> need to add some extra glue to get this behavior to work.
No. That is not supposed to work.

mkdir b-sis
cd b-sis
../rtems/configure --prefix=${HOME}/... --target=sparc-rtems4.11 \
   --enable-rtemsbsp=sis --enable-tests
make
make install

Did you update the tree?

Joel is wondering if the Centos image you are using has the
checkout from git or cvs. If cvs, then you need a fresh checkout
from git.

Either way, as root, you will need to do a "yum upgrade" to
get the latest tools.  And if you get updates to the source tree,
you might as well run "./bootstrap" from the top of the
RTEMS source tree before building.
>>> For the previous email, the error command is:
>>> sparc-rtems4.11-gcc -specs bsp_specs -qrtems -g -O2 -mcu=cypress -o
>>> sp01.exe init.o task1.o
>>>
>>> I have exported the environment variables as follows:
>>> export RTEMS_MAKEFILE_PATH = /opt/rtems-4.11/sparc-rtems4.11/sis
>> When you configure RTEMS, you provide a directory to install into as the
>> --prefix=XXX argument. Since you need root permission to write into
>> /opt/rtems-4.11, I can almost guarantee that is not where sis is installed.
>> Check the way you built RTEMS, where you installed the BSP, and fix
>> that setting.
>>
>> The general form of the RTEMS_MAKEFILE_PATH is:
>>
>> ${prefix}/${target}/${bsp}
>>
>> where
>>
>> prefix = directory RTEMS is installed to (e.g. --prefix argument)
>> target = CPU architecture/target (e.g. --target argument)
>> bsp = BSP selected (e.g. one of the BSPs provided to --enable-rtemsbsp)
>>
>> You have to do a "make install" before it will be at that path.
>>> export PATH =
>>> /opt/rtems-4.11/bin:/opt/rtems-4.11/sparc-rtems4.11/sis/lib:$PATH
>>> export C_INCLUDE_FILE=/opt/rtems-4.11/sparc-rtems4.11/sis/lib/include
>>>
>>> It can't locate bsp_specs and linkcmds, both of which are in the
>>> /opt/rtems-4.11/sparc-rtems4.11/sis/lib directory, which is already
>>> exported.
>>>
>>> I am emailing to ask where I was wrong about the configuation.
>>>
>>> In addition, where should I put the source files for new application in
>>> order to build the application? Where are the templates for autoconf and
>>> automake tools inputs files? And for the make/custom/sis.cfg, where should
>>> they be placed in order to build the application successfully?
>>>
>>> Regards,
>>> xiaochen
>>>
>>>
>>>
>>> On Jun 19, 2012, at 12:33 PM, Ralf Corsepius wrote:
>>>
>>>> On 06/19/2012 06:18 PM, Gedare Bloom wrote:
>>>>> Please post how you configured rtems, how you made rtems, and how you
>>>>> installed rtems.
>>>> More important than this is sending the call which triggers this error
>>>> message.
>>>>
>>>> I am pretty sure the OP is missing an argument to a compiler call.
>>>>
>>>> Ralf
>>>
>>> _______________________________________________
>>> rtems-devel mailing list
>>> rtems-devel at rtems.org
>>> http://www.rtems.org/mailman/listinfo/rtems-devel
>>
>>
>> --
>> 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
>>
>>


-- 
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