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