<div dir="ltr">Please take me off the mail list.<div><br></div><div>Thanks</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Feb 1, 2015 at 7:30 PM, <span dir="ltr"><<a href="mailto:users-request@rtems.org" target="_blank">users-request@rtems.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send users mailing list submissions to<br>
<a href="mailto:users@rtems.org">users@rtems.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.rtems.org/mailman/listinfo/users" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:users-request@rtems.org">users-request@rtems.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:users-owner@rtems.org">users-owner@rtems.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: ARM Getting Started Assistance: Beagleboard, Zedboard, or<br>
STM32F4Discovery? (Ben Gras)<br>
2. Re: ARM Getting Started Assistance: Beagleboard, Zedboard, or<br>
STM32F4Discovery? (Joel Sherrill)<br>
3. Re: ARM Getting Started Assistance: Beagleboard, Zedboard, or<br>
STM32F4Discovery? (Jonathan Brandmeyer)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 2 Feb 2015 00:40:45 +0100<br>
From: Ben Gras <<a href="mailto:beng@shrike-systems.com">beng@shrike-systems.com</a>><br>
To: Jonathan Brandmeyer <<a href="mailto:jonathan.brandmeyer@gmail.com">jonathan.brandmeyer@gmail.com</a>><br>
Cc: "<a href="mailto:users@rtems.org">users@rtems.org</a>" <<a href="mailto:users@rtems.org">users@rtems.org</a>><br>
Subject: Re: ARM Getting Started Assistance: Beagleboard, Zedboard, or<br>
STM32F4Discovery?<br>
Message-ID:<br>
<<a href="mailto:CAK%2BHGR5t%2BD4hA-GL0sU8uOtAovJuKDrULqzj5dGgZ83ZPWt5Mg@mail.gmail.com">CAK+HGR5t+D4hA-GL0sU8uOtAovJuKDrULqzj5dGgZ83ZPWt5Mg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Dear all,<br>
<br>
I took a quick look at why the beagle bsp fails to link. It seems<br>
there is a multilib interaction I don't really understand that is<br>
causing the symbol to be missing. (The symbol appears in some library<br>
arch variants and not in others.) I'm not too familiar with how that<br>
works so I can't find a clean solution right now.<br>
<br>
If possible in your scenario, rebuilding the beagle bsp without the<br>
multilib option should work as a workaround for now. You can run the<br>
code on a linaro qemu fork that implements the bbxm if you don't have<br>
the hw.<br>
<br>
Info on how to do that is at my blog post on the subject,<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>
Let me know if I can help there.<br>
<br>
<br>
On Sun, Feb 1, 2015 at 10:56 PM, Jonathan Brandmeyer<br>
<<a href="mailto:jonathan.brandmeyer@gmail.com">jonathan.brandmeyer@gmail.com</a>> wrote:<br>
> I've been doing embedded programming on "proprietary" small RTOS like<br>
> FreeRTOS, ChibiOS, and DSP/BIOS for about a decade, as well as POSIX<br>
> programming on Linux systems. I'm interested in using RTEMS as a<br>
> full-featured POSIX RTOS, to see if it is a portable alternative to<br>
> the other proprietary RTOS out there. Unfortunately, all of my<br>
> attempts to get started using the standard documentation have failed<br>
> miserably. If anyone has successfully gotten any of these BSP's to<br>
> actually work, it would be very helpful.<br>
><br>
> My host OS is Debian Testing, on x86_64. Source code was checked out<br>
> of git from the mainline sources on <a href="http://rtems.org" target="_blank">rtems.org</a>.<br>
><br>
> I've successfully built a toolchain using the rtems-source-builder,<br>
> according to its instructions, with no obvious errors:<br>
><br>
> $ ./source-builder/sb-check<br>
> $ cd rtems && ../source-builder/sb-set-builder 4.11/rtems-arm.bset<br>
> --prefix=$HOME/Programs/rtems_4_11 --log=rtems-user-log.txt<br>
><br>
> Recent builds of GCC, the autotools and other standard programs all<br>
> get successfully installed to my designated --prefix.<br>
><br>
> Next I attempt to build RTEMS for the arm target, and things start to fail.<br>
><br>
> $ export PATH=$HOME/Programs/rtems_4_11:$PATH<br>
> $ cd rtems-git && ./bootstrap && cd ../<br>
> $ mkdir build_rtems_arm && cd build_rtems_arm<br>
> $ ../rtems-git/configure --target=arm-rtems4.11<br>
> --prefix=$HOME/Programs/rtems_4_11 --enable-posix --enable-networking<br>
> --enable-cxx --enable-tests --enable-multilib<br>
> --enable-rtemsbsp="stm32f4 beagleboneblack xilinx_zynq_a9_qemu<br>
> xilinx_zynq_zedboard armcortexa9"<br>
> $ make -j8 all<br>
><br>
> I've picked the stm32f4 and xilinx BSP's because I actually own those.<br>
> Well, I own a microzed, but I'm hoping that I can port the zedboard<br>
> BSP to the microzed without too much difficulty. Failing that, the<br>
> armcortexa9 target should support some level of generic qemu. I hope.<br>
><br>
> In the "wishlist" category, it would be nice if the recursive<br>
> Makefiles were written to use the make jobserver for parallel process<br>
> control. As it stands, the build is almost entirely serial. A little<br>
> inconvenient, but not fatal.<br>
><br>
> The first thing that goes seriously wrong, is that the beagleboneblack<br>
> bsp doesn't link. All of its example programs fail to link due to the<br>
> missing symbol _CPU_Thread_Idle_body.<br>
><br>
> The next thing to go wrong is that some of the test programs (other<br>
> than examples themselves) on the stm32f4 and xilinx targets fail to<br>
> build. Each of these Makefiles have a set of steps like this:<br>
><br>
> $(PAX) = # empty assignment<br>
> sometarget: someprereqs<br>
> $(PAX) -w -f $@ $<<br>
><br>
> I don't know what program $(PAX) is supposed to be referencing, but<br>
> since it is an empty variable, the program w(1) gets executed instead.<br>
> Instead of creating a tar file from a .o file, it describes the<br>
> current machine load to the console, producing an error sequence like:<br>
> make[6]: Entering directory<br>
> '/home/jonathan/src/build_rtems_arm/arm-rtems4.11/c/stm32f4/testsuites/libtests/dl01'<br>
> w -f dl.tar dl-o1.o<br>
> 21:59:30 up 31 days, 11:10, 3 users, load average: 1.83, 2.49, 2.08<br>
> USER TTY LOGIN@ IDLE JCPU PCPU WHAT<br>
> ../../../../../../tools/build/rtems-bin2c -C dl.tar dl-tar.c<br>
> ../../../../../../tools/build/rtems-bin2c -H dl.tar dl-tar.h<br>
> cannot open dl.tar for reading<br>
> Makefile:645: recipe for target 'dl-tar.c' failed<br>
> make[6]: *** [dl-tar.c] Error 1<br>
> make[6]: *** Waiting for unfinished jobs....<br>
> # trimmed: Make continues to unwind its recursive invocations.<br>
><br>
> OK, so I cut out the beaglebone bsp, and reduce the testsuite down to<br>
> demonstration samples (starting from a fresh build directory):<br>
> $ ../rtems-git/configure --target=arm-rtems4.11<br>
> --prefix=$HOME/Programs/rtems_4_11 --enable-posix --enable-networking<br>
> --enable-cxx --enable-tests=samples --enable-multilib<br>
> --enable-rtemsbsp="stm32f4 xilinx_zynq_a9_qemu xilinx_zynq_zedboard<br>
> armcortexa9"<br>
> $ make -j8 all<br>
> $ make install<br>
><br>
> This build at least completes. However, the sample test programs<br>
> don't run. Using the armcortexa9 bsp:<br>
><br>
> jonathan@pheonix:~/src/build_rtems_arm$ arm-rtems4.11-gdb<br>
> ./arm-rtems4.11/c/armcortexa9/testsuites/samples/ticker/ticker.exe<br>
> GNU gdb (GDB) 7.8.1<br>
> Copyright (C) 2014 Free Software Foundation, Inc.<br>
> License GPLv3+: GNU GPL version 3 or later <<a href="http://gnu.org/licenses/gpl.html" target="_blank">http://gnu.org/licenses/gpl.html</a>><br>
> This is free software: you are free to change and redistribute it.<br>
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br>
> and "show warranty" for details.<br>
> This GDB was configured as "--host=x86_64-linux-gnu --target=arm-rtems4.11".<br>
> Type "show configuration" for configuration details.<br>
> For bug reporting instructions, please see:<br>
> <<a href="http://www.gnu.org/software/gdb/bugs/" target="_blank">http://www.gnu.org/software/gdb/bugs/</a>>.<br>
> Find the GDB manual and other documentation resources online at:<br>
> <<a href="http://www.gnu.org/software/gdb/documentation/" target="_blank">http://www.gnu.org/software/gdb/documentation/</a>>.<br>
> For help, type "help".<br>
> Type "apropos word" to search for commands related to "word"...<br>
> Reading symbols from<br>
> ./arm-rtems4.11/c/armcortexa9/testsuites/samples/ticker/ticker.exe...done.<br>
> (gdb) target sim<br>
> Connected to the simulator.<br>
> (gdb) load<br>
> Loading section .start, size 0x1e4 vma 0x0<br>
> Loading section .text, size 0x14eb0 vma 0x1e4<br>
> Loading section .init, size 0x18 vma 0x15094<br>
> Loading section .fini, size 0x18 vma 0x150ac<br>
> Loading section .rodata, size 0x1150 vma 0x150c4<br>
> Loading section .ARM.exidx, size 0x8 vma 0x16214<br>
> Loading section .eh_frame, size 0x48 vma 0x1621c<br>
> Loading section .init_array, size 0x4 vma 0x16264<br>
> Loading section .fini_array, size 0x4 vma 0x16268<br>
> Loading section .jcr, size 0x4 vma 0x1626c<br>
> Loading section .data, size 0x5c0 vma 0x166b0<br>
> Start address 0x40<br>
> Transfer rate: 737664 bits in <1 sec.<br>
> (gdb) run<br>
> Starting program:<br>
> /home/jonathan/src/build_rtems_arm/arm-rtems4.11/c/armcortexa9/testsuites/samples/ticker/ticker.exe<br>
> [Inferior 1 (process 42000) exited with code 0110]<br>
> (gdb) quit<br>
><br>
> Similar (same?) problem with qemu on the xilinx_zynq_a9_qemu bsp:<br>
><br>
> jonathan@pheonix:~/src/build_rtems_arm$ qemu-system-arm -S -s<br>
> -no-reboot -serial mon:stdio -serial /dev/null -net none -nographic -M<br>
> xilinx-zynq-a9 -m 256M -kernel<br>
> ./arm-rtems4.11/c/xilinx_zynq_a9_qemu/testsuites/samples/ticker/ticker.exe<br>
> Warning: nic cadence_gem.0 has no peer<br>
> Warning: nic cadence_gem.1 has no peer<br>
><br>
> The nic warnings should be harmless since I've specified explicitly<br>
> disabling the network interface. Nevertheless, QEMU just halts here<br>
> with no output whatsoever. It must be killed externally. In this<br>
> case, qemu-system-arm is v2.1+dfsg-11 as packaged by the Debian<br>
> project. A fresh build of qemu directly from their Git repository has<br>
> the same result.<br>
><br>
> So yeah. I would appreciate any help in getting these targets to<br>
> build. I understand that I'm working with the development repository,<br>
> and some measure of breakage and instability is to be expected. It<br>
> also seems that my most preferred target (the Zynq) has the steepest<br>
> hill to climb according to the mailing list archives. But since the<br>
> BSP's that I want to use are only present in the 4.11 development<br>
> series, here I am.<br>
><br>
> Sincerely,<br>
> Jonathan Brandmeyer<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>
Message: 2<br>
Date: Sun, 1 Feb 2015 16:53:52 -0700<br>
From: Joel Sherrill <<a href="mailto:joel.sherrill@oarcorp.com">joel.sherrill@oarcorp.com</a>><br>
To: Ben Gras <<a href="mailto:beng@shrike-systems.com">beng@shrike-systems.com</a>>, Jonathan Brandmeyer<br>
<<a href="mailto:jonathan.brandmeyer@gmail.com">jonathan.brandmeyer@gmail.com</a>><br>
Cc: "<a href="mailto:users@rtems.org">users@rtems.org</a>" <<a href="mailto:users@rtems.org">users@rtems.org</a>><br>
Subject: Re: ARM Getting Started Assistance: Beagleboard, Zedboard, or<br>
STM32F4Discovery?<br>
Message-ID: <<a href="mailto:10FCCAB7-EEBA-46DD-9716-63610F1218BF@oarcorp.com">10FCCAB7-EEBA-46DD-9716-63610F1218BF@oarcorp.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
<br>
<br>
On February 1, 2015 4:40:45 PM MST, Ben Gras <<a href="mailto:beng@shrike-systems.com">beng@shrike-systems.com</a>> wrote:<br>
>Dear all,<br>
><br>
>I took a quick look at why the beagle bsp fails to link. It seems<br>
>there is a multilib interaction I don't really understand that is<br>
>causing the symbol to be missing. (The symbol appears in some library<br>
>arch variants and not in others.) I'm not too familiar with how that<br>
>works so I can't find a clean solution right now.<br>
<br>
Building multilib is rather useless to most people. It builds the cpukit for every arm CPU variant GCC knows. In this case, the error is in a variant we don't have a BSP for. You only need one of the variants. More below.<br>
<br>
Build rtems for a single BSP and drop the multilib option. For some BSPs, you might see an issue linking a dynamic loading test. I saw it on the Pi last week but the other test ran.<br>
<br>
>If possible in your scenario, rebuilding the beagle bsp without the<br>
>multilib option should work as a workaround for now. You can run the<br>
>code on a linaro qemu fork that implements the bbxm if you don't have<br>
>the hw.<br>
><br>
>Info on how to do that is at my blog post on the subject,<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>
>Let me know if I can help there.<br>
><br>
><br>
>On Sun, Feb 1, 2015 at 10:56 PM, Jonathan Brandmeyer<br>
><<a href="mailto:jonathan.brandmeyer@gmail.com">jonathan.brandmeyer@gmail.com</a>> wrote:<br>
>> I've been doing embedded programming on "proprietary" small RTOS like<br>
>> FreeRTOS, ChibiOS, and DSP/BIOS for about a decade, as well as POSIX<br>
>> programming on Linux systems. I'm interested in using RTEMS as a<br>
>> full-featured POSIX RTOS, to see if it is a portable alternative to<br>
>> the other proprietary RTOS out there. Unfortunately, all of my<br>
>> attempts to get started using the standard documentation have failed<br>
>> miserably. If anyone has successfully gotten any of these BSP's to<br>
>> actually work, it would be very helpful.<br>
>><br>
>> My host OS is Debian Testing, on x86_64. Source code was checked out<br>
>> of git from the mainline sources on <a href="http://rtems.org" target="_blank">rtems.org</a>.<br>
>><br>
>> I've successfully built a toolchain using the rtems-source-builder,<br>
>> according to its instructions, with no obvious errors:<br>
>><br>
>> $ ./source-builder/sb-check<br>
>> $ cd rtems && ../source-builder/sb-set-builder 4.11/rtems-arm.bset<br>
>> --prefix=$HOME/Programs/rtems_4_11 --log=rtems-user-log.txt<br>
<br>
The rtems $prefix/bin should be at the head of your PATH. Especially when you bootstrap RTEMS.<br>
<br>
>> Recent builds of GCC, the autotools and other standard programs all<br>
>> get successfully installed to my designated --prefix.<br>
>><br>
>> Next I attempt to build RTEMS for the arm target, and things start to<br>
>fail.<br>
>><br>
>> $ export PATH=$HOME/Programs/rtems_4_11:$PATH<br>
>> $ cd rtems-git && ./bootstrap && cd ../<br>
>> $ mkdir build_rtems_arm && cd build_rtems_arm<br>
>> $ ../rtems-git/configure --target=arm-rtems4.11<br>
>> --prefix=$HOME/Programs/rtems_4_11 --enable-posix --enable-networking<br>
>> --enable-cxx --enable-tests --enable-multilib<br>
>> --enable-rtemsbsp="stm32f4 beagleboneblack xilinx_zynq_a9_qemu<br>
>> xilinx_zynq_zedboard armcortexa9"<br>
>> $ make -j8 all<br>
<br>
<br>
>> I've picked the stm32f4 and xilinx BSP's because I actually own<br>
>those.<br>
>> Well, I own a microzed, but I'm hoping that I can port the zedboard<br>
>> BSP to the microzed without too much difficulty. Failing that, the<br>
>> armcortexa9 target should support some level of generic qemu. I<br>
>hope.<br>
>><br>
>> In the "wishlist" category, it would be nice if the recursive<br>
>> Makefiles were written to use the make jobserver for parallel process<br>
>> control. As it stands, the build is almost entirely serial. A<br>
>little<br>
>> inconvenient, but not fatal.<br>
<br>
There is a much faster replacement build system being worked on. We are trying to wrap up outstanding tickets and branch before switching.<br>
<br>
>> The first thing that goes seriously wrong, is that the<br>
>beagleboneblack<br>
>> bsp doesn't link. All of its example programs fail to link due to<br>
>the<br>
>> missing symbol _CPU_Thread_Idle_body.<br>
<br>
Multilib issue I am sure. I build all bsps fairly regularly and the beagle builds without that option.<br>
<br>
>> The next thing to go wrong is that some of the test programs (other<br>
>> than examples themselves) on the stm32f4 and xilinx targets fail to<br>
>> build. Each of these Makefiles have a set of steps like this:<br>
>><br>
>> $(PAX) = # empty assignment<br>
>> sometarget: someprereqs<br>
>> $(PAX) -w -f $@ $<<br>
>><br>
>> I don't know what program $(PAX) is supposed to be referencing, but<br>
>> since it is an empty variable, the program w(1) gets executed<br>
>instead.<br>
>> Instead of creating a tar file from a .o file, it describes the<br>
>> current machine load to the console, producing an error sequence<br>
>like:<br>
>> make[6]: Entering directory<br>
>><br>
>'/home/jonathan/src/build_rtems_arm/arm-rtems4.11/c/stm32f4/testsuites/libtests/dl01'<br>
>> w -f dl.tar dl-o1.o<br>
>> 21:59:30 up 31 days, 11:10, 3 users, load average: 1.83, 2.49,<br>
>2.08<br>
>> USER TTY LOGIN@ IDLE JCPU PCPU WHAT<br>
>> ../../../../../../tools/build/rtems-bin2c -C dl.tar dl-tar.c<br>
>> ../../../../../../tools/build/rtems-bin2c -H dl.tar dl-tar.h<br>
>> cannot open dl.tar for reading<br>
>> Makefile:645: recipe for target 'dl-tar.c' failed<br>
>> make[6]: *** [dl-tar.c] Error 1<br>
>> make[6]: *** Waiting for unfinished jobs....<br>
>> # trimmed: Make continues to unwind its recursive invocations.<br>
<br>
You don't appear to have tar installed. Pax is the FOSS tar implementation. If you loom in the logs, there is probably a message about what it looked for.<br>
<br>
>><br>
>> OK, so I cut out the beaglebone bsp, and reduce the testsuite down to<br>
>> demonstration samples (starting from a fresh build directory):<br>
>> $ ../rtems-git/configure --target=arm-rtems4.11<br>
>> --prefix=$HOME/Programs/rtems_4_11 --enable-posix --enable-networking<br>
>> --enable-cxx --enable-tests=samples --enable-multilib<br>
>> --enable-rtemsbsp="stm32f4 xilinx_zynq_a9_qemu xilinx_zynq_zedboard<br>
>> armcortexa9"<br>
>> $ make -j8 all<br>
>> $ make install<br>
>><br>
>> This build at least completes. However, the sample test programs<br>
>> don't run. Using the armcortexa9 bsp:<br>
>><br>
>> jonathan@pheonix:~/src/build_rtems_arm$ arm-rtems4.11-gdb<br>
>> ./arm-rtems4.11/c/armcortexa9/testsuites/samples/ticker/ticker.exe<br>
>> GNU gdb (GDB) 7.8.1<br>
>> Copyright (C) 2014 Free Software Foundation, Inc.<br>
>> License GPLv3+: GNU GPL version 3 or later<br>
><<a href="http://gnu.org/licenses/gpl.html" target="_blank">http://gnu.org/licenses/gpl.html</a>><br>
>> This is free software: you are free to change and redistribute it.<br>
>> There is NO WARRANTY, to the extent permitted by law. Type "show<br>
>copying"<br>
>> and "show warranty" for details.<br>
>> This GDB was configured as "--host=x86_64-linux-gnu<br>
>--target=arm-rtems4.11".<br>
>> Type "show configuration" for configuration details.<br>
>> For bug reporting instructions, please see:<br>
>> <<a href="http://www.gnu.org/software/gdb/bugs/" target="_blank">http://www.gnu.org/software/gdb/bugs/</a>>.<br>
>> Find the GDB manual and other documentation resources online at:<br>
>> <<a href="http://www.gnu.org/software/gdb/documentation/" target="_blank">http://www.gnu.org/software/gdb/documentation/</a>>.<br>
>> For help, type "help".<br>
>> Type "apropos word" to search for commands related to "word"...<br>
>> Reading symbols from<br>
>><br>
>./arm-rtems4.11/c/armcortexa9/testsuites/samples/ticker/ticker.exe...done.<br>
>> (gdb) target sim<br>
>> Connected to the simulator.<br>
>> (gdb) load<br>
>> Loading section .start, size 0x1e4 vma 0x0<br>
>> Loading section .text, size 0x14eb0 vma 0x1e4<br>
>> Loading section .init, size 0x18 vma 0x15094<br>
>> Loading section .fini, size 0x18 vma 0x150ac<br>
>> Loading section .rodata, size 0x1150 vma 0x150c4<br>
>> Loading section .ARM.exidx, size 0x8 vma 0x16214<br>
>> Loading section .eh_frame, size 0x48 vma 0x1621c<br>
>> Loading section .init_array, size 0x4 vma 0x16264<br>
>> Loading section .fini_array, size 0x4 vma 0x16268<br>
>> Loading section .jcr, size 0x4 vma 0x1626c<br>
>> Loading section .data, size 0x5c0 vma 0x166b0<br>
>> Start address 0x40<br>
>> Transfer rate: 737664 bits in <1 sec.<br>
>> (gdb) run<br>
>> Starting program:<br>
>><br>
>/home/jonathan/src/build_rtems_arm/arm-rtems4.11/c/armcortexa9/testsuites/samples/ticker/ticker.exe<br>
>> [Inferior 1 (process 42000) exited with code 0110]<br>
>> (gdb) quit<br>
<br>
<br>
The simulator in gdb does not support all the instructions for all the arm models. Not sure if this is the issue but with cortex seems likely from memory.<br>
<br>
>> Similar (same?) problem with qemu on the xilinx_zynq_a9_qemu bsp:<br>
>><br>
>> jonathan@pheonix:~/src/build_rtems_arm$ qemu-system-arm -S -s<br>
>> -no-reboot -serial mon:stdio -serial /dev/null -net none -nographic<br>
>-M<br>
>> xilinx-zynq-a9 -m 256M -kernel<br>
>><br>
>./arm-rtems4.11/c/xilinx_zynq_a9_qemu/testsuites/samples/ticker/ticker.exe<br>
>> Warning: nic cadence_gem.0 has no peer<br>
>> Warning: nic cadence_gem.1 has no peer<br>
>><br>
>> The nic warnings should be harmless since I've specified explicitly<br>
>> disabling the network interface. Nevertheless, QEMU just halts here<br>
>> with no output whatsoever. It must be killed externally. In this<br>
>> case, qemu-system-arm is v2.1+dfsg-11 as packaged by the Debian<br>
>> project. A fresh build of qemu directly from their Git repository<br>
>has<br>
>> the same result.<br>
<br>
Qemu is an interesting project which doesn't seem to merge patches in a timely manner. Very likely unless you use the RSB to build a qemu, you want get the needed patches. As Ben mentioned Linaro's qemu works for the Beagle. I think the rsb works for realview and zynq. Not sure for beagle.<br>
<br>
>> So yeah. I would appreciate any help in getting these targets to<br>
>> build. I understand that I'm working with the development<br>
>repository,<br>
>> and some measure of breakage and instability is to be expected. It<br>
>> also seems that my most preferred target (the Zynq) has the steepest<br>
>> hill to climb according to the mailing list archives. But since the<br>
>> BSP's that I want to use are only present in the 4.11 development<br>
>> series, here I am.<br>
>><br>
>> Sincerely,<br>
>> Jonathan Brandmeyer<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>
>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>
------------------------------<br>
<br>
Message: 3<br>
Date: Sun, 1 Feb 2015 17:30:46 -0700<br>
From: Jonathan Brandmeyer <<a href="mailto:jonathan.brandmeyer@gmail.com">jonathan.brandmeyer@gmail.com</a>><br>
To: "<a href="mailto:users@rtems.org">users@rtems.org</a>" <<a href="mailto:users@rtems.org">users@rtems.org</a>><br>
Subject: Re: ARM Getting Started Assistance: Beagleboard, Zedboard, or<br>
STM32F4Discovery?<br>
Message-ID:<br>
<CAGe17FtMMO02-Zq6=<a href="mailto:8LF-ZGhCoGx-8kb7kEcdL0op7XSXP%2Bkdw@mail.gmail.com">8LF-ZGhCoGx-8kb7kEcdL0op7XSXP+kdw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
><br>
> The simulator in gdb does not support all the instructions for all the arm models. Not sure if this is the issue but with cortex seems likely from memory.<br>
><br>
>>> Similar (same?) problem with qemu on the xilinx_zynq_a9_qemu bsp:<br>
>>><br>
>>> jonathan@pheonix:~/src/build_rtems_arm$ qemu-system-arm -S -s<br>
>>> -no-reboot -serial mon:stdio -serial /dev/null -net none -nographic<br>
>>-M<br>
>>> xilinx-zynq-a9 -m 256M -kernel<br>
>>><br>
>>./arm-rtems4.11/c/xilinx_zynq_a9_qemu/testsuites/samples/ticker/ticker.exe<br>
>>> Warning: nic cadence_gem.0 has no peer<br>
>>> Warning: nic cadence_gem.1 has no peer<br>
>>><br>
>>> The nic warnings should be harmless since I've specified explicitly<br>
>>> disabling the network interface. Nevertheless, QEMU just halts here<br>
>>> with no output whatsoever. It must be killed externally. In this<br>
>>> case, qemu-system-arm is v2.1+dfsg-11 as packaged by the Debian<br>
>>> project. A fresh build of qemu directly from their Git repository<br>
>>has<br>
>>> the same result.<br>
><br>
> Qemu is an interesting project which doesn't seem to merge patches in a timely manner. Very likely unless you use the RSB to build a qemu, you want get the needed patches. As Ben mentioned Linaro's qemu works for the Beagle. I think the rsb works for realview and zynq. Not sure for beagle.<br>
<br>
Unfortunately, qemu doesn't build via the RSB. RSB references some<br>
patches that 404 out right now (log attached).<br>
$ ../source-builder/sb-set-builder --prefix=$HOME/Programs/rtems_4_11<br>
devel/qemu.bset<br>
<br>
<br>
-Jonathan<br>
-------------- next part --------------<br>
RTEMS Tools Project - Source Builder Error Report<br>
Build: error: downloading <a href="https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-play.patch" target="_blank">https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-play.patch</a>: all paths have failed, giving up<br>
Command Line: ../source-builder/sb-set-builder --prefix=/home/jonathan/Programs/rtems_4_11 devel/qemu.bset<br>
Python: 2.7.8 (default, Oct 18 2014, 12:50:18) [GCC 4.9.1]<br>
git://<a href="http://git.rtems.org/rtems-source-builder/origin/712516ac1eceb988b06ae1df0ab53f7d27bbfd23-modified" target="_blank">git.rtems.org/rtems-source-builder/origin/712516ac1eceb988b06ae1df0ab53f7d27bbfd23-modified</a><br>
Linux jonathan-laptop-lenovo 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64<br>
Tail of the build log:<br>
/usr/bin/install -c -m 644 ../../glib-2.39.3/po/<a href="http://Makefile.in.in" target="_blank">Makefile.in.in</a> \<br>
/home/jonathan/src/rtems-source-builder/rtems/build/tmp/glib-2.39.3-x86_64-linux-gnu-1-root-jonathan/home/jonathan/Programs/rtems_4_11/share/glib-2.0/gettext/po/<a href="http://Makefile.in.in" target="_blank">Makefile.in.in</a>; \<br>
else \<br>
: ; \<br>
fi<br>
make[2]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/po'<br>
Making install in docs<br>
make[2]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs'<br>
Making install in reference<br>
make[3]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference'<br>
Making install in glib<br>
make[4]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/glib'<br>
make[5]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/glib'<br>
make[5]: Nothing to be done for 'install-exec-am'.<br>
Nothing to install<br>
/bin/mkdir -p '/home/jonathan/src/rtems-source-builder/rtems/build/tmp/glib-2.39.3-x86_64-linux-gnu-1-root-jonathan/home/jonathan/Programs/rtems_4_11/share/man/man1'<br>
/usr/bin/install -c -m 644 ../../../../glib-2.39.3/docs/reference/glib/glib-gettextize.1 ../../../../glib-2.39.3/docs/reference/glib/gtester.1 ../../../../glib-2.39.3/docs/reference/glib/gtester-report.1 '/home/jonathan/src/rtems-source-builder/rtems/build/tmp/glib-2.39.3-x86_64-linux-gnu-1-root-jonathan/home/jonathan/Programs/rtems_4_11/share/man/man1'<br>
make[5]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/glib'<br>
make[4]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/glib'<br>
Making install in gobject<br>
make[4]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gobject'<br>
make[5]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gobject'<br>
make[5]: Nothing to be done for 'install-exec-am'.<br>
Nothing to install<br>
/bin/mkdir -p '/home/jonathan/src/rtems-source-builder/rtems/build/tmp/glib-2.39.3-x86_64-linux-gnu-1-root-jonathan/home/jonathan/Programs/rtems_4_11/share/man/man1'<br>
/usr/bin/install -c -m 644 ../../../../glib-2.39.3/docs/reference/gobject/glib-mkenums.1 ../../../../glib-2.39.3/docs/reference/gobject/glib-genmarshal.1 ../../../../glib-2.39.3/docs/reference/gobject/gobject-query.1 '/home/jonathan/src/rtems-source-builder/rtems/build/tmp/glib-2.39.3-x86_64-linux-gnu-1-root-jonathan/home/jonathan/Programs/rtems_4_11/share/man/man1'<br>
make[5]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gobject'<br>
make[4]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gobject'<br>
Making install in gio<br>
make[4]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio'<br>
Making install in gdbus-object-manager-example<br>
make[5]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio/gdbus-object-manager-example'<br>
make[6]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio/gdbus-object-manager-example'<br>
make[6]: Nothing to be done for 'install-exec-am'.<br>
Nothing to install<br>
make install-data-hook<br>
make[7]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio/gdbus-object-manager-example'<br>
rm -rf /home/jonathan/src/rtems-source-builder/rtems/build/tmp/glib-2.39.3-x86_64-linux-gnu-1-root-jonathan/home/jonathan/Programs/rtems_4_11/share/gtk-doc/html/gdbus-object-manager-example<br>
make[7]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio/gdbus-object-manager-example'<br>
make[6]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio/gdbus-object-manager-example'<br>
make[5]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio/gdbus-object-manager-example'<br>
make[5]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio'<br>
make[6]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio'<br>
make[6]: Nothing to be done for 'install-exec-am'.<br>
Nothing to install<br>
/bin/mkdir -p '/home/jonathan/src/rtems-source-builder/rtems/build/tmp/glib-2.39.3-x86_64-linux-gnu-1-root-jonathan/home/jonathan/Programs/rtems_4_11/share/man/man1'<br>
/usr/bin/install -c -m 644 ../../../../glib-2.39.3/docs/reference/gio/gapplication.1 ../../../../glib-2.39.3/docs/reference/gio/gio-querymodules.1 ../../../../glib-2.39.3/docs/reference/gio/glib-compile-schemas.1 ../../../../glib-2.39.3/docs/reference/gio/glib-compile-resources.1 ../../../../glib-2.39.3/docs/reference/gio/gsettings.1 ../../../../glib-2.39.3/docs/reference/gio/gresource.1 ../../../../glib-2.39.3/docs/reference/gio/gdbus.1 ../../../../glib-2.39.3/docs/reference/gio/gdbus-codegen.1 '/home/jonathan/src/rtems-source-builder/rtems/build/tmp/glib-2.39.3-x86_64-linux-gnu-1-root-jonathan/home/jonathan/Programs/rtems_4_11/share/man/man1'<br>
make[6]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio'<br>
make[5]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio'<br>
make[4]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference/gio'<br>
make[4]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference'<br>
make[5]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference'<br>
make[5]: Nothing to be done for 'install-exec-am'.<br>
make[5]: Nothing to be done for 'install-data-am'.<br>
make[5]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference'<br>
make[4]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference'<br>
make[3]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs/reference'<br>
make[3]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs'<br>
make[4]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs'<br>
make[4]: Nothing to be done for 'install-exec-am'.<br>
make[4]: Nothing to be done for 'install-data-am'.<br>
make[4]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs'<br>
make[3]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs'<br>
make[2]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/docs'<br>
Making install in tests<br>
make[2]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests'<br>
make install-recursive<br>
make[3]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests'<br>
Making install in gobject<br>
make[4]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/gobject'<br>
make install-am<br>
make[5]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/gobject'<br>
make[6]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/gobject'<br>
make[6]: Nothing to be done for 'install-exec-am'.<br>
make[6]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/gobject'<br>
make[5]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/gobject'<br>
make[4]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/gobject'<br>
Making install in refcount<br>
make[4]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/refcount'<br>
make install-am<br>
make[5]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/refcount'<br>
make[6]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/refcount'<br>
make[6]: Nothing to be done for 'install-exec-am'.<br>
make[6]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/refcount'<br>
make[5]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/refcount'<br>
make[4]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests/refcount'<br>
make[4]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests'<br>
make[5]: Entering directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests'<br>
make[5]: Nothing to be done for 'install-exec-am'.<br>
make[5]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests'<br>
make[4]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests'<br>
make[3]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests'<br>
make[2]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build/tests'<br>
make[1]: Leaving directory '/home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1/build'<br>
+ cd /home/jonathan/src/rtems-source-builder/rtems/build/glib-2.39.3-x86_64-linux-gnu-1<br>
==> %clean:<br>
+ echo ==> %clean:<br>
copy: /home/jonathan/src/rtems-source-builder/rtems/build/tmp/glib-2.39.3-x86_64-linux-gnu-1-root-jonathan => /home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan/devel/qemu.bset<br>
config: devel/qemu-git-1.cfg<br>
package: qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1<br>
script: 1: #!/bin/sh<br>
script: 2: # ___build_pre in as set up in defaults.py<br>
script: 3: # Save the original path away.<br>
script: 4: export SB_ORIG_PATH=${PATH}<br>
script: 5: # Directories<br>
script: 6: SB_PREFIX="/home/jonathan/Programs/rtems_4_11"<br>
script: 7: SB_PREFIX_CLEAN=$(echo "/home/jonathan/Programs/rtems_4_11" | /bin/sed -e 's/^\///')<br>
script: 8: SB_SOURCE_DIR="/home/jonathan/src/rtems-source-builder/rtems/sources"<br>
script: 9: SB_BUILD_DIR="/home/jonathan/src/rtems-source-builder/rtems/build/qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1"<br>
script: 10: # host == build, use build; host != build , host uses host and build uses build<br>
script: 11: SB_HOST_CFLAGS="-O2 -pipe "<br>
script: 12: SB_HOST_CXXFLAGS="-O2 -pipe "<br>
script: 13: SB_HOST_LDFLAGS="-L/home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan/devel/qemu.bset/${SB_PREFIX_CLEAN}/lib"<br>
script: 14: SB_BUILD_CFLAGS="-O2 -pipe -I/home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan/devel/qemu.bset/${SB_PREFIX_CLEAN}/include"<br>
script: 15: SB_BUILD_CXXFLAGS="-O2 -pipe -I/home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan/devel/qemu.bset/${SB_PREFIX_CLEAN}/include"<br>
script: 16: SB_BUILD_LDFLAGS="-L/home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan/devel/qemu.bset/${SB_PREFIX_CLEAN}/lib"<br>
script: 17: SB_CFLAGS="${SB_BUILD_CFLAGS} "<br>
script: 18: SB_CXXFLAGS="${SB_BUILD_CXXFLAGS} "<br>
script: 19: SB_ARCH="x86_64"<br>
script: 20: SB_OS="linux"<br>
script: 21: export SB_SOURCE_DIR SB_BUILD_DIR SB_ARCH SB_OS<br>
script: 22: export SB_HOST_CFLAGS SB_HOST_CXXFLAGS SB_HOST_LDFLAGS<br>
script: 23: export SB_BUILD_CFLAGS SB_BUILD_CXXFLAGS SB_BUILD_LDFLAGS<br>
script: 24: export SB_CFLAGS SB_CXXFLAGS<br>
script: 25: # Documentation<br>
script: 26: SB_DOC_DIR="/home/jonathan/Programs/rtems_4_11/share/doc"<br>
script: 27: export SB_DOC_DIR<br>
script: 28: # Packages<br>
script: 29: SB_PACKAGE_NAME="qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1"<br>
script: 30: SB_PACKAGE_BUILDNAME="qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1"<br>
script: 31: SB_PACKAGE_VERSION="d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed"<br>
script: 32: SB_PACKAGE_RELEASE="1"<br>
script: 33: export SB_PACKAGE_NAME SB_PACKAGE_VERSION SB_PACKAGE_RELEASE<br>
script: 34: # Build directories<br>
script: 35: export SB_PREFIX<br>
script: 36: SB_BUILD_DIR="/home/jonathan/src/rtems-source-builder/rtems/build/qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1"<br>
script: 37: SB_BUILD_ROOT="/home/jonathan/src/rtems-source-builder/rtems/build/tmp/qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1-root-jonathan"<br>
script: 38: SB_BUILD_ROOT_BINDIR="/home/jonathan/src/rtems-source-builder/rtems/build/tmp/qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1-root-jonathan/${SB_PREFIX_CLEAN}/bin"<br>
script: 39: export SB_BUILD_ROOT SB_BUILD_DIR SB_BUILD_ROOT_BINDIR<br>
script: 40: SB_BUILD_CXC_DIR="/home/jonathan/src/rtems-source-builder/rtems/build/qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1-cxc"<br>
script: 41: SB_BUILD_CXC_ROOT="/home/jonathan/src/rtems-source-builder/rtems/build/tmp/qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1-jonathan-cxc"<br>
script: 42: SB_BUILD_CXC_ROOT_BINDIR="/home/jonathan/src/rtems-source-builder/rtems/build/tmp/qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1-jonathan-cxc/${SB_PREFIX_CLEAN}/bin"<br>
script: 43: export SB_BUILD_CXC_ROOT SB_BUILD_CXC_DIR SB_BUILD_CXC_ROOT_BINDIR<br>
script: 44: SB_TMPROOT="/home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan/devel/qemu.bset"<br>
script: 45: SB_TMPPREFIX="/home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan/devel/qemu.bset/${SB_PREFIX_CLEAN}"<br>
script: 46: SB_TMPBINDIR="/home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan/devel/qemu.bset/${SB_PREFIX_CLEAN}/bin"<br>
script: 47: export SB_TMPROOT SB_TMPPREFIX SB_TMPBINDIR<br>
script: 48: SB_TMPCXCROOT="/home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan/devel/qemu.bset"<br>
script: 49: SB_TMPCXCPREFIX="/home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan-cxc/devel/qemu.bset/${SB_PREFIX_CLEAN}"<br>
script: 50: SB_TMPCXCBINDIR="/home/jonathan/src/rtems-source-builder/rtems/build/tmp/sb-jonathan-cxc/devel/qemu.bset/${SB_PREFIX_CLEAN}/bin"<br>
script: 51: export SB_TMPCXCROOT SB_TMPCXCPREFIX SB_TMPCXCBINDIR<br>
script: 52: # Extra path support<br>
script: 53: SB_EXTRAPATH="/home/jonathan/src/rtems-source-builder/source-builder"<br>
script: 54: # The compiler flags<br>
script: 55:<br>
script: 56:<br>
script: 57: export CFLAGS_FOR_TARGET<br>
script: 58: export CXXFLAGS_FOR_TARGET<br>
script: 59: # Set up the path. Put the CXC path first.<br>
script: 60: if test -n "${SB_TMPBINDIR}" ; then<br>
script: 61: PATH="${SB_TMPBINDIR}:$PATH"<br>
script: 62: fi<br>
script: 63: if test -n "${SB_TMPCXCBINDIR}" ; then<br>
script: 64: PATH="${SB_TMPCXCBINDIR}:$PATH"<br>
script: 65: fi<br>
script: 66: if test -n "${SB_EXTRAPATH}" ; then<br>
script: 67: PATH="${SB_EXTRAPATH}:$PATH"<br>
script: 68: fi<br>
script: 69:<br>
script: 70:<br>
script: 71: export PATH<br>
script: 72: # Default environment set up.<br>
script: 73: LANG=C<br>
script: 74: export LANG<br>
script: 75: unset DISPLAY || :<br>
script: 76: umask 022<br>
script: 77: cd "/home/jonathan/src/rtems-source-builder/rtems/build/qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1"<br>
script: 78: echo "=> qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1:"<br>
script: 79: echo "==> %prep:"<br>
script: 80: build_top=$(pwd)<br>
script: 81: source_dir_qemu="qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed"<br>
source setup: qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1: source qemu -q -n qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed<br>
making dir: /home/jonathan/src/rtems-source-builder/rtems/sources/git<br>
git: clone: git://<a href="http://git.qemu-project.org/qemu.git" target="_blank">git.qemu-project.org/qemu.git</a> -> sources/git/qemu.git<br>
git: pull: git://<a href="http://git.qemu-project.org/qemu.git" target="_blank">git.qemu-project.org/qemu.git</a><br>
git: checkout: git://<a href="http://git.qemu-project.org/qemu.git" target="_blank">git.qemu-project.org/qemu.git</a> => d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed<br>
git: submodule: git://<a href="http://git.qemu-project.org/qemu.git" target="_blank">git.qemu-project.org/qemu.git</a> <= dtc<br>
script: 82: cd /home/jonathan/src/rtems-source-builder/rtems/build/qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed-x86_64-linux-gnu-1<br>
script: 83: /bin/rm -rf qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed<br>
script: 84: ln -s /home/jonathan/src/rtems-source-builder/rtems/sources/git/qemu.git ${source_dir_qemu}<br>
script: 85: cd qemu-d5b4dc3b50175f0c34f3cf4b053e123fb37f5aed<br>
script: 86: /bin/chmod -R a+rX,g-w,o-w .<br>
making dir: /home/jonathan/src/rtems-source-builder/rtems/patches<br>
download: <a href="http://patchwork.ozlabs.org/patch/406903/raw" target="_blank">http://patchwork.ozlabs.org/patch/406903/raw</a> -> patches/Provide-the-missing-LIBUSB_LOG_LEVEL_-for-older-libusb-or-FreeBSD.-Providing-just-the-needed-value-as-a-defined..patch<br>
checksums: Provide-the-missing-LIBUSB_LOG_LEVEL_-for-older-libusb-or-FreeBSD.-Providing-just-the-needed-value-as-a-defined..patch: 0b1f163808efd1e86ab858053d5df71d => 0b1f163808efd1e86ab858053d5df71d<br>
script: 87: /bin/cat /home/jonathan/src/rtems-source-builder/rtems/patches/Provide-the-missing-LIBUSB_LOG_LEVEL_-for-older-libusb-or-FreeBSD.-Providing-just-the-needed-value-as-a-defined..patch | /usr/bin/patch -p1<br>
making dir: /home/jonathan/src/rtems-source-builder/rtems/patches<br>
download: <a href="https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-play.patch" target="_blank">https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-play.patch</a> -> patches/0001-LEON3-Add-emulation-of-AMBA-plug-play.patch<br>
download: <a href="https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-play.patch" target="_blank">https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-play.patch</a>: error: HTTP Error 404: Not Found<br>
error: downloading <a href="https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-play.patch" target="_blank">https://gaisler.org/qemu/0001-LEON3-Add-emulation-of-AMBA-plug-play.patch</a>: all paths have failed, giving up<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<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>
End of users Digest, Vol 101, Issue 2<br>
*************************************<br>
</blockquote></div><br></div>