Building rtems-4.11
Joel Sherrill
Joel.Sherrill at OARcorp.com
Sat Nov 23 03:31:50 UTC 2013
The tools are all in the directory in your GCI development bin directory. Put that at the head of your path .. Not the opt directory.
Alan Cudmore <alan.cudmore at gmail.com> wrote:
Hi,
Now, Typing "sparc-rtems4.11-gcc" doesn't work :(
If I go to $HOME/GCIdevelopment/rtems/4.11/bin and do ./sparc-rtems4.11-gcc joel.c, it gives me an error.
/home/kevin/GCIdevelopment/rtems/4.11/lib/gcc/sparc-rtems4.11/4.8.1/../../../../sparc-rtems4.11/bin/ld: warning: cannot find entry symbol _start; defaulting to 0000000000010074
For this, try ./sparc-rtems4.11-gcc -c joel.c
It looks like the compiler is working and is trying to link an executable.
On your first problem:
And I get:
>
> configure: error: no acceptable cc found in $PATH
>
Do you have the native linux GCC tools installed?
try:
$ gcc -v
and see what it returns.
Hope this helps,
Alan
On 11/22/2013 10:14 PM, Kev Fei wrote:
RTEMS Source Builder for Tools
--------------------------------------
*Terminal:
cd
mkdir -p GCIdevelopment/rtems/src
cd GCIdevelopment/rtems/src
git clone git://git.rtems.org/rtems-source-builder.git<http://git.rtems.org/rtems-source-builder.git>
cd rtems-source-builder
--Environment checking
source-builder/sb-check
This turned up for me some
warning: exe: absolute exe found in path: (__bzip2) /usr/bin/bzip2
warning: exe: absolute exe found in path: (__chgrp) /usr/bin/chgrp
warning: exe: absolute exe found in path: (__chown) /usr/sbin/chown
warning: exe: absolute exe found in path: (__grep) /usr/bin/grep
warning: exe: absolute exe found in path: (__sed) /usr/bin/sed
These programs were installed. For example, I could run grep in terminal. However I had to find the programs from the other locations on the disk (/usr/bin or /bin or /lib) and copy them over for the next step to work.
Then it says my environment is ok.
*Terminal:
cd rtems
../source-builder/sb-set-builder --log=l-sparc.txt --prefix=$HOME/GCIdevelopment/rtems/4.11 4.11/rtems-sparc
This step takes a long time; it took me 46 minutes with downloading. Then it ended with an error. It said it could not find python 2.7, but I had it installed. After googling, it turned out I had to have python2.7-dev installed.
Finally it built in around 27 minutes.
*Terminal:
ls $HOME/GCIdevelopment/rtems/4.11
ls $HOME/GCIdevelopment/rtems/4.11/bin
Both turned up nice results.
After reading your comments, I realized I had somehow skipped over this step in a newbie mistake :P
../source-builder/sb-set-builder --log=l-sparc.txt --prefix=$HOME/GCIdevelopment/rtems/4.11 --bset-tar-file 4.11/rtems-sparc
Built in 29 minutes.
Now, Typing "sparc-rtems4.11-gcc" doesn't work :(
If I go to $HOME/GCIdevelopment/rtems/4.11/bin and do ./sparc-rtems4.11-gcc joel.c, it gives me an error.
/home/kevin/GCIdevelopment/rtems/4.11/lib/gcc/sparc-rtems4.11/4.8.1/../../../../sparc-rtems4.11/bin/ld: warning: cannot find entry symbol _start; defaulting to 0000000000010074
I think I might've copied over a bunch of the built tools from the 4.11/bin to the /opt/rtems-4.11/bin folder at one point.
Maybe I should just start this thing over sometime :P
Kevin Fei
On Fri, Nov 22, 2013 at 10:11 PM, Kev Fei <kev1fei at gmail.com<mailto:kev1fei at gmail.com>> wrote:
RTEMS Source Builder for Tools
--------------------------------------
*Terminal:
cd
mkdir -p GCIdevelopment/rtems/src
cd GCIdevelopment/rtems/src
git clone git://git.rtems.org/rtems-source-builder.git<http://git.rtems.org/rtems-source-builder.git>
cd rtems-source-builder
--Environment checking
source-builder/sb-check
This turned up for me some
warning: exe: absolute exe found in path: (__bzip2) /usr/bin/bzip2
warning: exe: absolute exe found in path: (__chgrp) /usr/bin/chgrp
warning: exe: absolute exe found in path: (__chown) /usr/sbin/chown
warning: exe: absolute exe found in path: (__grep) /usr/bin/grep
warning: exe: absolute exe found in path: (__sed) /usr/bin/sed
These programs were installed. For example, I could run grep in terminal. However I had to find the programs from the other locations on the disk (/usr/bin or /bin or /lib) and copy them over for the next step to work.
Then it says my environment is ok.
*Terminal:
cd rtems
../source-builder/sb-set-builder --log=l-sparc.txt --prefix=$HOME/GCIdevelopment/rtems/4.11 4.11/rtems-sparc
This step takes a long time; it took me 46 minutes with downloading. Then it ended with an error. It said it could not find python 2.7, but I had it installed. After googling, it turned out I had to have python2.7-dev installed.
Finally it built in around 27 minutes.
*Terminal:
ls $HOME/GCIdevelopment/rtems/4.11
ls $HOME/GCIdevelopment/rtems/4.11/bin
Both turned up nice results.
After reading your comments, I realized I had somehow skipped over this step in a newbie mistake :P
../source-builder/sb-set-builder --log=l-sparc.txt --prefix=$HOME/GCIdevelopment/rtems/4.11 --bset-tar-file 4.11/rtems-sparc
Built in 29 minutes.
Now, Typing "sparc-rtems4.11-gcc" doesn't work :(
If I go to $HOME/GCIdevelopment/rtems/4.11/bin and do ./sparc-rtems4.11-gcc joel.c, it gives me an error.
/home/kevin/GCIdevelopment/rtems/4.11/lib/gcc/sparc-rtems4.11/4.8.1/../../../../sparc-rtems4.11/bin/ld: warning: cannot find entry symbol _start; defaulting to 0000000000010074
I think I might've copied over a bunch of the built tools from the 4.11/bin to the /opt/rtems-4.11/bin folder at one point.
Maybe I should just start this thing over sometime :P
Kevin Fei
On Fri, Nov 22, 2013 at 8:33 PM, Joel Sherrill <joel.sherrill at oarcorp.com<mailto:joel.sherrill at oarcorp.com>> wrote:
On 11/22/2013 6:33 PM, Kev Fei wrote:
> Hello,
>
> I am trying to build rtems 4.11 on Linux Mint 13 LTS 64-bit for sparc as
> part of Google Code-In.
Thanks for posting this to the users list. :)
> I used the RTEMS Source Builder to build these tools and I think I have
> them installed correctly:
What command did you use with the RSB? I would have expected
to see the right autoconf and automake versions in this
directory.
More below.
> ls /opt/rtems-4.11/bin
> cklength sparc-rtems4.11-gcov
> eolstrip sparc-rtems4.11-gdb
> install-if-change sparc-rtems4.11-gprof
> packhex sparc-rtems4.11-ld
> rtems-bin2c sparc-rtems4.11-ld.bfd
> sparc-rtems4.11-addr2line sparc-rtems4.11-nm
> sparc-rtems4.11-ar sparc-rtems4.11-objcopy
> sparc-rtems4.11-as sparc-rtems4.11-objdump
> sparc-rtems4.11-c++ sparc-rtems4.11-ranlib
> sparc-rtems4.11-c++filt sparc-rtems4.11-readelf
> sparc-rtems4.11-cpp sparc-rtems4.11-run
> sparc-rtems4.11-difftest sparc-rtems4.11-sis
> sparc-rtems4.11-elfedit sparc-rtems4.11-size
> sparc-rtems4.11-g++ sparc-rtems4.11-sorttimes
> sparc-rtems4.11-gcc-4.8.1 sparc-rtems4.11-strings
> sparc-rtems4.11-gcc-ar sparc-rtems4.11-strip
> sparc-rtems4.11-gcc-nm unhex
> sparc-rtems4.11-gcc-ranlib xmlwf
>
> Now I'm trying to build rtems, following the Quick Start.
>
> In $HOME/GCIdevelopment/rtems,
> *Terminal:
>
> git clone git://git.rtems.org/rtems.git<http://git.rtems.org/rtems.git>
> <http://git.rtems.org/rtems.git> rtems
> cd rtems
> export PATH=/opt/rtems-4.11/bin:$PATH
> ./bootstrap
Try these steps and let's see what we get.
type sparc-rtems4.11-gcc
Then compile this program ..put it in joel.c
==============
int main() {return 0;}
==============
sparc-rtems4.11-gcc joel.c
What's the output? It should compile just fine.
>
> First I had to update automake and autoconf. rtems required versions
> higher than what the repositories had, so I had to google them and
> install them from source, which was easy enough.
The RSB handles autoconf/automake as part of the RTEMS tools
if invoked correctly so I am a bit confused. We need the command
as shown above but if you did this much right, they should be
in your PATH.. so
autoconf --version
automake --version
> ../rtems/configure --target=sparc-rtems4.11 --enable-rtemsbsp=sis
> --enable-tests=samples --disable-posix
> make
>
>
> And I get:
>
> configure: error: no acceptable cc found in $PATH
>
>
> Although sparc-rtems4.11-gcc-4.8.1 is already in
> rtems/b-sis/sparc-rtems4.11, I copy the other tools gcc-ar, gcc-nm, and
> gcc-ranlib too.
This doesn't sound like something you should have done.
> I try the above two commands again and it still doesn't work.
> Output:
>
> Making all in tools/build
> make[1]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/tools/build'
> make all-am
> make[2]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/tools/build'
> make[2]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/tools/build'
> make[1]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/tools/build'
> Making all in tools/cpu
> make[1]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/tools/cpu'
> Making all in generic
> make[2]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/tools/cpu/generic'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/tools/cpu/generic'
> make[2]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/tools/cpu'
> make[2]: Nothing to be done for `all-am'.
> make[2]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/tools/cpu'
> make[1]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/tools/cpu'
> Making all in testsuites/tools
> make[1]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/testsuites/tools'
> Making all in generic
> make[2]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/testsuites/tools/generic'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/testsuites/tools/generic'
> make[2]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/testsuites/tools'
> make[2]: Nothing to be done for `all-am'.
> make[2]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/testsuites/tools'
> make[1]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/testsuites/tools'
> Making all in sparc-rtems4.11/c
> make[1]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/sparc-rtems4.11/c'
> Making all in .
> make[2]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/sparc-rtems4.11/c'
> make[2]: Nothing to be done for `all-am'.
> make[2]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/sparc-rtems4.11/c'
> Making all in sis
> make[2]: Entering directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/sparc-rtems4.11/c/sis'
> make[2]: *** No rule to make target `all'. Stop.
> make[2]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/sparc-rtems4.11/c/sis'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/home/kevin/GCIdevelopment/rtems/b-sis/sparc-rtems4.11/c'
> make: *** [all-recursive] Error 1
>
>
> I have tried --enable-posix instead as well as removing the posix tag
> altogether. Google searches for ***No rule to make target 'all'. errors
> have not been very helpful.
>
> Does anybody have any ideas on what's going on? Thank you!
Try the above and post the results. I think RSB was invoked
with something minor wrong.
> Kevin Fei
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill at OARcorp.com<mailto:joel.sherrill at OARcorp.com> On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985<tel:%28256%29%20722-9985>
--
Physics!
Layton!
Nintendo!
Wikipedia!
--
Physics!
Layton!
Nintendo!
Wikipedia!
_______________________________________________
rtems-users mailing list
rtems-users at rtems.org<mailto:rtems-users at rtems.org>
http://www.rtems.org/mailman/listinfo/rtems-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20131122/d99d09cd/attachment-0001.html>
More information about the users
mailing list