Building RTEMS

[Chris Sparks]

Well I noticed that only the RTEMS part changed for pre5 and not the 
tools so I installed
the patch to pre4 to make pre5 and my building seems to be progressing 
pretty nicely.

I am getting excited that I am getting closer to my goal of getting a 
sample program to run.
May not get to it until I get back from SIGAda conference this year.  Is 
anyone going?  I'd
like to swap RTEMS stories.

Has anyone done any graphics (VGA, SVGA, whatever) with RTEMS?  I need it.

Chris Sparks

Chris Sparks wrote:

> Ok I figured out what I did wrong and I was not passing the right 
> parameter into configure so
> it couldn't find i386-rtems-gcc.  So I went ahead fixed my mistake and 
> the build still crashes.
> It wants me to do a make dist-clean or some such action.
>
> My question really is what specifically do I need to do to get up to 
> pre5.  I have pre4 and I
> didn't want to have to download everything.  What exactly changed that 
> I need to upgrade to?
>
> Thanks,
> chris Sparks
>
> Ralf Corsepius wrote:
>
>> On Tue, 2003-12-02 at 07:26, Chris Sparks wrote:
>>  
>>
>>> Hello Ralf,
>>>
>>> Ralf Corsepius wrote:
>>>
>>>   
>>>
>>>> On Mon, 2003-12-01 at 03:35, Chris Sparks wrote:
>>>>
>>>>
>>>>     
>>>>
>>>>> Hi,
>>>>>
>>>>> It has been quiet on this list for some time now....
>>>>>
>>>>> I managed to get a half decent Fedora up and running and was going 
>>>>> through instructions to build
>>>>> RTEMS.  I am using the Getting started with the C++ users manual 
>>>>> and I got several errors.
>>>>> The first was "checking for i386-gcc... no"
>>>>> which I know I set the path right.
>>>>>  
>>>>>       
>>>>
>>>> Well, though you say so, I doubt it.
>>>>
>>>>     
>>>
>>> What is strange is that the native gcc is "gcc" not "i386-gcc" and 
>>> the target gcc is "i386-rtems-gcc" so
>>> I don't know what this "i386-gcc" is.
>>>   
>>
>> I don't know what you are doing ;-)
>>
>> The native C-compiler must be called cc or gcc and must be in $PATH
>>
>> which gcc
>> should tell you if this applies.
>>
>>  
>>
>>>>> The second came from configure, "no acceptable cc found in $PATH
>>>>>  
>>>>> So what is going on here?
>>>>>  
>>>>>       
>>>>
>>>> Make sure to have
>>>> * the native toolchain installed
>>>> * the target toolchain installed
>>>>
>>>> And to have set up $PATH correctly.
>>>>
>>>>     
>>>
>>> I have the "/opt/rtems/bin" before all others in my path.  Is this 
>>> wrong?
>>>   
>>
>> It depends on which of the RTEMS toolchains you have installed.
>>
>> It could be one of these:
>> /opt/rtems/bin (Used until now), /opt/rtems-4.6/bin (Probably used by 
>> the final 4.6-release) or
>> /opt/rtems-4.7/bin (To be used by future snapshots).
>>
>> Assuming you want to build i386-rtems, you should have one of
>> /opt/rtems/bin/i386-rtems-gcc
>> /opt/rtems-4.6/bin/i386-rtems4.6-gcc
>> /opt/rtems-4.7/bin/i386-rtems4.7-gcc
>>
>> Prepend the */bin to $PATH, that contains the i386-rtems*-gcc you have.
>>
>> Then configure RTEMS using the string that prefixes the target gcc 
>> you have:
>> Eg. If having /opt/rtems/bin/i386-rtems-gcc, the  use
>> configure --target=i386-rtems [options]
>>
>> If having /opt/rtems-4.6/bin/i386-rtems4.6-gcc, then use
>> configure --target=i386-rtems4.6 [options]
>>
>> Ralf
>>
>>
>>
>>  
>>
>