<div dir="ltr"><div><div><div>Hi Gedare,<br><br></div> That worked, thanks. I was then able to get the "waf configure" step to work in the examples-v2 directory by using the following line: <br><br><span style="font-size:15px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline" id="docs-internal-guid-756fd3c0-b1e4-cc46-7150-1733e23f503b"><font>~/development/rtems/rtems-tools/waf configure --rtems=$HOME/development/rtems/just_a_test --rtems-tools=$HOME/development/rtems/4.11 --rtems-bsps=arm/beagleboneblack</font><br><br></span></div><span style="font-size:15px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline" id="docs-internal-guid-756fd3c0-b1e4-cc46-7150-1733e23f503b"><font>And the waf configure seems to have worked. However, when I try to run the "waf" step to build everything in examples-v2, it gets really far, but stops on step 96 of 116 with a linker error. Does this error look like a configuration problem or is it something that might be just wrong with one of the examples which I should just skip over? One wierd thing I noticed was that the "hello-deep.c" file that it was talking about is a filename with an initial space which threw me for a loop for a minute!<br><br></font></span></div><span style="font-size:15px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline" id="docs-internal-guid-756fd3c0-b1e4-cc46-7150-1733e23f503b"><font>-andrew</font></span><br><span style="font-size:15px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline" id="docs-internal-guid-756fd3c0-b1e4-cc46-7150-1733e23f503b"></span><div><div><span style="font-size:15px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline" id="docs-internal-guid-756fd3c0-b1e4-cc46-7150-1733e23f503b"></span><br><span style="font-size:15px;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline" id="docs-internal-guid-756fd3c0-b1e4-cc46-7150-1733e23f503b"></span><div><div><div><div><div>...<br>[ 95/116] cprogram: build/arm-rtems4.11-beagleboneblack/posix_api/psx_sched_report/test.c.1.o -> build/arm-rtems4.11-beagleboneblack/posix_api/psx_sched_report/psx_sched_report.exe<br>[ 96/116] cprogram: build/arm-rtems4.11-beagleboneblack/led/event_server/init.c.1.o -> build/arm-rtems4.11-beagleboneblack/led/event_server/event_server.exe<br>/home/andrewha/development/rtems/4.11/bin/arm-rtems4.11-gcc: hello-deep.o: In function `__wrap_Init':<br>/home/andrewha/development/rtems/4.11/bin/arm-rtems4.11-gcc: /home/andrewha/development/examples-v2/build/arm-rtems4.11-beagleboneblack/ hello-deep.c:78: undefined reference to `Init'<br>/home/andrewha/development/rtems/4.11/bin/arm-rtems4.11-gcc: collect2: error: ld returned 1 exit status<br>error: linking: Linker error<br>Waf: Leaving directory `/home/andrewha/development/examples-v2/build/arm-rtems4.11-beagleboneblack'<br>Build failed<br> -> task in 'hello-deep.texe' failed (exit status 10): <br> {task 140274785055824: rtrace test.c.2.o -> hello-deep.texe}<br>['/home/andrewha/development/rtems/4.11/bin/rtems-tld', '-W hello-deep', '-C', '../../hello/both_hello/hello-deep.ini', '-r', '/home/andrewha/development/rtems/just_a_test', '-B', 'arm/beagleboneblack', '-c', '/home/andrewha/development/rtems/4.11/bin/arm-rtems4.11-gcc', '-l', '/home/andrewha/development/rtems/4.11/bin/arm-rtems4.11-gcc', '--', 'hello/both_hello/test.c.2.o', '-qrtems', '-B/home/andrewha/development/rtems/just_a_test/arm-rtems4.11/lib/', '-B/home/andrewha/development/rtems/just_a_test/arm-rtems4.11/beagleboneblack/lib/', '--specs', 'bsp_specs', '-mcpu=cortex-a8', '-mcpu=cortex-a8', '-o', '/home/andrewha/development/examples-v2/build/arm-rtems4.11-beagleboneblack/hello/both_hello/hello-deep.texe', '-Wl,-Bstatic']<br><br></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 22, 2015 at 9:29 AM, Gedare Bloom <span dir="ltr"><<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Andrew,<br>
<br>
You probably need to rm -r b-beagle and redo everything from there.<br>
The old build is probably still in place and being used. (In theory,<br>
make distclean in b-beagle should work too. But rm is a more certain<br>
way to clean.)<br>
<span class="HOEnZb"><font color="#888888"><br>
Gedare<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Sat, Feb 21, 2015 at 3:27 PM, Andrew Harris <<a href="mailto:andrew.unit@gmail.com">andrew.unit@gmail.com</a>> wrote:<br>
> Hi Joel,<br>
><br>
> Thanks for the response, I don't think I see anything wrong with the<br>
> typing. When I run the configure line I mentioned, and then do make<br>
> install, I actually get a bin/ directory in the "just_a_test" directory that<br>
> I set as the prefix, and it has the following files in it:<br>
> "arm-rtems4.11-difftest arm-rtems4.11-sorttimes cklength eolstrip<br>
> install-if-change packhex rtems-bin2c unhex". It's not until it gets to<br>
> the beagleboneblack step that it seems the prefix isn't propagated.<br>
><br>
> -andrew<br>
><br>
><br>
> On Sat, Feb 21, 2015 at 3:14 PM, Joel Sherrill <<a href="mailto:joel.sherrill@oarcorp.com">joel.sherrill@oarcorp.com</a>><br>
> wrote:<br>
>><br>
>><br>
>><br>
>> On February 21, 2015 2:02:52 PM CST, Andrew Harris <<a href="mailto:andrew.unit@gmail.com">andrew.unit@gmail.com</a>><br>
>> wrote:<br>
>> >Hi Gedare,<br>
>> ><br>
>> >Thanks for the suggestion, I think I understand what you're saying. I<br>
>> >went back to the article, and made a slight modification to the<br>
>> >configure line that was specified; I added a prefix ("just_a_test") to<br>
>> >see what would happen when I did a make install:<br>
>> ><br>
>> >CONSOLE_POLLED=1 ../rtems-src/configure --target=arm-rtems4.11<br>
>> >--enable-rtemsbsp="beagleboneblack" --enable-tests<br>
>> >--prefix=$HOME/development/rtems/just_a_test<br>
>> ><br>
>> >It got pretty far, but I found that there must be an error in one of<br>
>> >the configuration steps below this call, because it looks like the<br>
>> >prefix I specified didn't make it all the way down to the BSP, where it<br>
>> >is still apparently trying to install into /opt/rtems-4.11:<br>
>><br>
>> Double check the typing on the --prefix option. The configure script is<br>
>> acting like it wasn't provided.<br>
>><br>
>><br>
>> >Making install in beagleboneblack<br>
>> >make[2]: Entering directory<br>
>> >`/home/andrew/development/rtems/b-beagle/arm-rtems4.11/c/beagleboneblack'<br>
>> >Making install in .<br>
>> >make[3]: Entering directory<br>
>> >`/home/andrew/development/rtems/b-beagle/arm-rtems4.11/c/beagleboneblack'<br>
>> >make[4]: Entering directory<br>
>> >`/home/andrew/development/rtems/b-beagle/arm-rtems4.11/c/beagleboneblack'<br>
>> >make[4]: Nothing to be done for `install-exec-am'.<br>
>> > /bin/mkdir -p '/opt/rtems-4.11/lib/pkgconfig'<br>
>> >/bin/mkdir: cannot create directory ‘/opt/rtems-4.11’: Permission<br>
>> >denied<br>
>> >make[4]: *** [install-pkgconfigDATA] Error 1<br>
>> >make[4]: Leaving directory<br>
>> >`/home/andrew/development/rtems/b-beagle/arm-rtems4.11/c/beagleboneblack'<br>
>> >make[3]: *** [install-am] Error 2<br>
>> >make[3]: Leaving directory<br>
>> >`/home/andrew/development/rtems/b-beagle/arm-rtems4.11/c/beagleboneblack'<br>
>> >make[2]: *** [install-recursive] Error 1<br>
>> >make[2]: Leaving directory<br>
>> >`/home/andrew/development/rtems/b-beagle/arm-rtems4.11/c/beagleboneblack'<br>
>> >make[1]: *** [install-recursive] Error 1<br>
>> >make[1]: Leaving directory<br>
>> >`/home/andrew/development/rtems/b-beagle/arm-rtems4.11/c'<br>
>> >make: *** [install-recursive] Error 1<br>
>> ><br>
>> >So I'm stuck again; I'm not sure where to look to try to find where the<br>
>> >prefix argument isn't handed off correctly.<br>
>> ><br>
>> ><br>
>> >-andrew<br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> >On Sat, Feb 21, 2015 at 2:20 PM, Gedare Bloom <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>> wrote:<br>
>> ><br>
>> >Hi Andrew,<br>
>> ><br>
>> >Have you installed the compiled RTEMS and BSPs via "make install" e.g.<br>
>> >in your ~/development/rtems/b-beagle directory?<br>
>> ><br>
>> >The waf script will only find BSPs that are installed in the directory<br>
>> >you tell it to look e.g. ~/development/rtems/4.11<br>
>> ><br>
>> >Gedare<br>
>> ><br>
>> ><br>
>> >On Sat, Feb 21, 2015 at 9:48 AM, Andrew Harris <<a href="mailto:andrew.unit@gmail.com">andrew.unit@gmail.com</a>><br>
>> >wrote:<br>
>> >> Hello,<br>
>> >><br>
>> >> Thanks for the useful information. I'm still having a heck of a<br>
>> >time<br>
>> >> getting the examples to build. I can't seem to get my "waf<br>
>> >configure" line<br>
>> >> to work out. I got RTEMS working from the nice article on this site:<br>
>> >><br>
>> >><br>
>><br>
>> > ><a href="http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html" target="_blank">http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html</a><br>
>> >><br>
>> >> But I fear I don't understand now how to specify the waf configure<br>
>> >line.<br>
>> >> I've got it so that it doesn't complain about the RTEMS path, nor<br>
>> >does it<br>
>> >> complain about the RTEMS tools path:<br>
>> >><br>
>> >> ~/development/rtems/rtems-tools/waf configure<br>
>> >> --rtems=$HOME/development/rtems/4.11<br>
>> >> --rtems-tools=$HOME/development/rtems/4.11<br>
>> >><br>
>> >> But I can't seem to figure out how to tell it to use the<br>
>> >beagleboneblack<br>
>> >> BSP. I have added some print statements into the rtems.py file which<br>
>> >I<br>
>> >> believe is used by the waf build system and it doesn't seem to see<br>
>> >any bsps<br>
>> >> at all in the paths I've specified above.<br>
>> >><br>
>> >> However, from the website article, it seems to build in such a way as<br>
>> >to<br>
>> >> create a b-beagle directory, and deep inside that directory I do see<br>
>> >a<br>
>> >> directory that contains a ".pc" file, which I presume is a key file<br>
>> >for the<br>
>> >> BSP:<br>
>> >><br>
>> >><br>
>><br>
>> > >development/rtems/b-beagle/arm-rtems4.11/c/beagleboneblack/arm-rtems4.11-beagleboneblack.pc<br>
>> >><br>
>> >> But I can't seem to figure out how to combine this knowledge with the<br>
>> >> directories that are required for the waf configure step.<br>
>> >><br>
>> >> Has anyone gotten stuck here before? If so, any help would be<br>
>> >appreciated!<br>
>> >><br>
>> >> thanks,<br>
>> >> -andrew<br>
>> >><br>
>> >><br>
>> >><br>
>> >><br>
>> >> On Wed, Feb 18, 2015 at 9:02 AM, Gedare Bloom <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>><br>
>> >wrote:<br>
>> >>><br>
>> >>> Hi Andrew,<br>
>> >>><br>
>> >>> The examples located in testsuites are intended to be compiled with<br>
>> >>> RTEMS and will not work by copying them elsewhere. For compiling an<br>
>> >>> application, you should have a look at the examples-v2.git<br>
>> >repository<br>
>> >>> [1]. That should have more info about using RTEMS_MAKEFILE_PATH, and<br>
>> >>> also has a newer approach to compiling applications for RTEMS that<br>
>> >>> uses the Waf build system. I highly recommend checking out the<br>
>> >>> waf-based approach to compiling applications as it has some great<br>
>> >>> features, albeit at a slight learning curve.<br>
>> >>><br>
>> >>> Gedare<br>
>> >>><br>
>> >>> [1] <a href="https://git.rtems.org/examples-v2/" target="_blank">https://git.rtems.org/examples-v2/</a><br>
>> >>><br>
>> >>> On Tue, Feb 17, 2015 at 8:16 PM, Andrew Harris<br>
>> ><<a href="mailto:andrew.unit@gmail.com">andrew.unit@gmail.com</a>><br>
>> >>> wrote:<br>
>> >>> > Hello, I'm trying to figure out how to start a new RTEMS<br>
>> >application.<br>
>> >>> > I<br>
>> >>> > thought I would start by looking at the ticker example. I copied<br>
>> >the<br>
>> >>> > ticker<br>
>> >>> > example but I am not sure how to compile it. I am not an expert<br>
>> >in<br>
>> >>> > autoconf/automake and could use some assistance on how to get<br>
>> >started.<br>
>> >>> > I<br>
>> >>> > think I figured out how to configure my RTEMS_MAKEFILE_PATH<br>
>> >variable,<br>
>> >>> > but<br>
>> >>> > the only two files in the ticker example are Makefile.am and<br>
>> >>> > Makefile.in,<br>
>> >>> > and I don't know what to do next to build it. Any help would be<br>
>> >>> > appreciated!<br>
>> >>> ><br>
>> >>> > -andrew<br>
>> >>> ><br>
>> >>> > _______________________________________________<br>
>> >>> > users mailing list<br>
>> >>> > <a href="mailto:users@rtems.org">users@rtems.org</a><br>
>> >>> > <a href="http://lists.rtems.org/mailman/listinfo/users" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> users mailing list<br>
>> >> <a href="mailto:users@rtems.org">users@rtems.org</a><br>
>> >> <a href="http://lists.rtems.org/mailman/listinfo/users" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
>><br>
>> --joel<br>
><br>
><br>
</div></div></blockquote></div><br></div>