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

Post a Comment

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...
Post a Comment
Read more

[LEGO nxt] Install the Enhanced NXT firmware and Upload the OSEK excutable file with Ubuntu 64bits 14.04 in 2015

This tutorial is referred from Install the Enhanced NXT firmware on NXT . I think this is the critical part to capture the idea from the tutorial for Windows. I have tried many ways to conquer the problem of libnxt3.0, however, I still have some problems on the compilation of fwflash or something else. Though the tutorial for Windows is doable, my preference is to build up everything with Linux environment. Fortunately, I notice that NxTTool in the tutorial for Windows is really powerful. We can handle the firmware updating by using NxTTool in Linux as well! I also refer to this Japanese Blog , which inspire me a lot. As usual, install the required packages: sudo apt-get install libusb-dev:i386 libusb-0.1-4 subversion fpc Please note, here is the case for 64bits user that I change libusb-dev to libusb-dev:i386 comparing to the original tutorial. Instead of using libnxt to do the uploading, here I follow that JP Blog to get the latest version of bricxcc: (The url in blog i...
Post a Comment
Read more

Virtualenv experience or alternatives

Today I have a project which requires several packages on my python. However, due to whatever reason, I have a lot of different versions of python. Before I thought, it was fine to just install and maintain each by each. Maybe it is time to learn how to use virtualenv. (alternatively, you can use module). I first got some quick ideas from here: https://stackoverflow.com/questions/10763440/how-to-install-python3-version-of-package-via-pip-on-ubuntu The magic virtualenv does is that, it copies a series of your python binaries, include, pip, etc., into a folder. The prepared activate script does that, add the export folder into the general variable PATH at its beginning. By doing so, the targeted version of python will be the first target that will be executed. To enable virtualenv, source the position of the above folder/bin/activate To leave the virtualenv, just type deactivate, as it is defined when you load the activate script. For example, I call virtualenv in my home ...
Post a Comment
Read more