Skip to main content

[RTEMS/RSB] rtems-source-builder: The installation of cross toolchains for gdb 7.9 to 7.11

This is about the error in RSB for RTEMS 4.12 on Ubuntu 14.04 LTS. Most likely, we can directly follow the tutorial here: https://devel.rtems.org/wiki/Developer/Tools/RSB Or deeply refer to the document https://docs.rtems.org/rsb/#_why_build_from_source Please note that the version of this document is still for 4.11. You have to change it accordingly to 4.12. If there is any one who has this error message before (for gdb):

checking whether to use python... yes
checking for python... /usr/local/bin/python
checking for python2.7... no
configure: error: python is missing or unusable

However, you think you definitely have python2.7 in your system, either you used sudo apt-get install or built the source code by yourself.

By referring to http://askubuntu.com/questions/513626/cannot-compile-gdb7-8-with-python-support, we can see that the automatic configuration will check if the environment of your host can compile that simple C program.
Therefore, I focus on the problem that why I cannot compile that simple C program.


By reading a ton of similar solution, I notice that install Python-dev cannot solve my problem.
For example, here, http://stackoverflow.com/questions/21530577/fatal-error-python-h-no-such-file-or-directory


However, I fail still. I will find the solution but maybe the above information is useful for some folks.

----------------Alternatives----------------
Instead of hanging on the Python 2.7, the alternative way is directly assigned python3 to compile gdb. Go to
rtems/rtems-source-builder/source-builder/config/gdb-7-1.cfg

and change the end of line 64 or the line for the default without path:
using python3
 --with-python=/usr/bin/python3 
You should change it to your destination accordingly.

Comments

Popular posts from this blog

RSB+RTEMS 5/6 with QEMU-SMP (ARM realview_pbx_a9_qemu as example)

Since I got a request regarding this blog  written in 2016, summarizing again the complete flow with the latest version of RTEMS could be a good idea. Prepare a suitable workspace according to the adopted operating system on your host ( https://docs.rtems.org/branches/master/user/hosts/index.html ):  sudo apt-get build-dep build-essential gcc-defaults g++ gdb git unzip pax bison flex texinfo unzip python3-dev libpython-dev libncurses5-dev zlib1g-dev Checkout RSB and build: git clone git://git.rtems.org/rtems-source-builder.git rsb change directory to rsb/rtems/ and type ../source-builder/sb-set-builder --prefix=<the path you like to store the built toolchains> <the name of bsp> For example, to use QEMU, I need toolchains for ARM, so: ../source-builder/sb-set-builder --prefix=/home/kh.chen/respository/build/. 6/rtems-arm This will take a while. Please ensure your connection is reliable. Add the built folder into your PATH. For example, you can add one line in ~/.bas...

[Gem5] Full system Simulation with Official Kernel

I follow the youtube provided by Gem5 to get the inspiration. (http://gem5.org/Running_gem5#Full_System_.28FS.29_Mode) I download the file here: http://www.gem5.org/dist/current/arm/ with http://www.gem5.org/dist/current/arm/aarch-system-20170616.tar.xz Then Set up M5_PATH as the place I extract the files: "/home/khchen/full_system_images/" If the setting is correct, assigning the disk-image will finish the rest of setting for dtb and kernel specifications. So far I can only use this img (aarch32-ubuntu-natty-headless.img) as my disk-image to run up to the login interface of the ubuntu: build/ARM/gem5.opt configs/example/fs.py --disk-image=/home/khchen/full_system_images/disks/aarch32-ubuntu-natty-headless.img With the other imgs, for example like "aarch64-ubuntu-trusty-headless.img", I think the kernel and the dtb should be given manually, because it will automatically load something with aarch32 prefix which doesn't make sense: info: kernel ...

Efficient Computation of Deadline-Miss Probability and Potential Pitfalls

Fortunately, I will attend the DATE 2019 conference to present my work. The title of my work is: Efficient Computation of Deadline-Miss Probability and Potential Pitfalls This work is regarding the approximation of Deadline-Miss probability for soft real-time systems. The abstract is as the following: In soft real-time systems, rare deadline misses are often tolerable by the applications. Towards this, probabilistic arguments and analyses are applicable to the timing analyses of this class of systems, as demonstrated in many existing researches. Convolution-based analyses allow to derive tight deadline-miss probabilities, but suffer from a high time complexity. Among the analytical approaches, which result in a significantly faster runtime than the convolution-based approaches, the Chernoff bounds provide the tightest results. In this paper, we show that calculating the deadline-miss probability using Chernoff bounds can be solved by considering an equivalent convex optimization ...