Fwd: Developing under MacOS

[Binkowski, Cassio]

Hi Everyone

I'm trying to build the RTEMS tools from source but it does not seem to go
through the GCC Download and Build, for every architecture I have tried.
When the tool* *is running for *rtems-4.11-powerpc-rtems4.11-gcc-4.7.1-7/doit
*I get the following error over and over:

*/Users/cassiobinkowski/workspace/rtems/build/BUILD/rtems-4.11-powerpc-rtems4.11-gcc-4.7.1-7/doit:
line 41: cd: gcc-4.7.1: No such file or directory*

I don't know what I'm doing wrong. I even tried downloading the 4.10 tools.
I'm running the following lines inside my *$RTEMS/build* folder:

*export RTEMS=$HOME/workspace/rtems*
*SB=$RTEMS/specbuilder*
*target=$1*
*
*
*${SB}/sb-setup . --rtems=$RTEMS/rtems-crossrpms*
 *${SB}/sb-crossgcc --url
http://www.rtems.org/ftp/pub/rtems/SOURCES/4.11--prefix=$RTEMS/rtems-crossrpms/rtems4.11
--log l.txt $target
*


Am I doing something wrong?

Best regards
Cassio

On Fri, Jul 27, 2012 at 6:45 PM, Chris Johns <chrisj at rtems.org> wrote:

> Hi,
>
> Please follow the steps in the script I attached.
>
> 1. Clone the rtems-crossprpms.git repo.
>   $ git clone git://git.rtems.org/rtems-**crossrpms.git<http://git.rtems.org/rtems-crossrpms.git>
>
> 2. Run the sb-setup script:
>   $ sb-setup . --rtems=<path to the crossrpms clone>
>
> 3. Run the crossgcc script:
>   $ sb-crossgcc \
>      --url http://www.rtems.org/ftp/pub/**rtems/SOURCES/4.11<http://www.rtems.org/ftp/pub/rtems/SOURCES/4.11>\
>      --prefix=/rtems/4.11 --log l.txt
>
> After this you will have a tar files in the TAR directory.
>
> Again please review the sb-build.sh script I attached to the previous
> email.
>
> Chris
>
>
> On 28/07/12 7:39 AM, Binkowski, Cassio wrote:
>
>> Hi Chris
>>
>> Thank you very much for the scripts. It will sure help a lot.
>>
>> So, please confirm whether I got it right or not:
>>
>> 1) We need to clone the git repository, with source codes and the spec
>> files;
>> 2) We need to build the source codes using the spec files using the
>> script you provided;
>> 3) After step 2, we have TARs, that need will be extracted by the
>> install script.
>>
>> Is this right?
>>
>> But, one more question: what about gcc, autoconf and automake?
>>
>> Best regards
>> Cassio
>>
>> On Mon, Jul 23, 2012 at 8:13 PM, Chris Johns <chrisj at rtems.org
>> <mailto:chrisj at rtems.org>> wrote:
>>
>>     On 24/07/12 8:10 AM, Binkowski, Cassio wrote:
>>
>>
>>         I would like a copy very much. It would be highly appreciated.
>>
>>
>>     Follow the details in the link provided. You can find the
>>     specbuilder source detailed in the following post I made:
>>
>>     http://www.rtems.org/__**pipermail/rtems-users/2012-__**
>> July/010264.html<http://www.rtems.org/__pipermail/rtems-users/2012-__July/010264.html>
>>
>>     <http://www.rtems.org/**pipermail/rtems-users/2012-**July/010264.html<http://www.rtems.org/pipermail/rtems-users/2012-July/010264.html>
>> >
>>
>>     I have attached a script I use.
>>
>>
>>         Also, it is not very clear to me these things of building the
>>         tools from
>>         source and how it would work in MacOS just like it does in Linux.
>>
>>
>>     The source used builds on a number of platforms including MacOS. The
>>     task is to get that source to build a set of RTEMS tools that match
>>     the release.
>>
>>
>>         Would you mind giving me a brief overview?
>>
>>
>>     Ralf maintains the tools by creating RPM spec files. You find these
>>     in the rtems-crossrpms.git repo. A spec file is a detailed script of
>>     the steps needed to build a tool chain. If rpmbuild was available on
>>     every computer we could all use rpmbuild how-ever rpmbuild is
>>     limited to a few Linux distributions. This leave us with a couple of
>>     alternatives. Create a separate and parallel means to maintain tools
>>     building on "other" hosts from source or write a tool that can use
>>     the spec file as a source of steps. About 2 or 3 years ago I decided
>>     on the spec file path because it is a write once rather than needing
>>     to track all of Ralf changes. It has proved to be very useful.
>>
>>     Take a look at the sb-build.sh script. It runs a set-up phase that
>>     copies in the spec files from the rtems-crossrpms.git clone you need
>>     to have. It then build the tools into tar files. There is an
>>     rt-install.sh script that unpacks the tools into the install path.
>>
>>     When Ralf releases new tools you get pull the changes into your git
>>     repo and rebuild.
>>
>>     Chris
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20120918/22195343/attachment.html>