DEPRECATED > GNU ARM Eclipse / Support requests / #54 Cannot set toolchain path

Federico - 2014-05-09

A quick correction. The places where the toolchains are installed are:
/opt/CodeSourcery/Sourcery_G++_Lite/arm-2010q1/
/opt/CodeSourcery/Sourcery_G++_Lite/arm-2013.11/

The subsequent /bin is of course the path for the compiler.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-05-09

be sure you remove all environment PATH variable settings and allow only the plug-in to manage the path, otherwise you'll have problems.

I suggest you experiment on a new, empty workspace, with freshly generated projects.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Federico - 2014-05-12

Thanks for the quick reply. I found an unwanted PATH variable setting in Ubuntu and I deleted it, I deleted the workspace to start again with an empty one, and reverted the project (unluckily I have to make the existing one working) and imported it again. Still the same error occurs, as before...
Is there any verbose/debug option to help me in finding which "hidden" setting is misleading the compiler?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-05-12

I'm afraid you are systematically doing something wrong. please follow the installation steps available from the documentation pages and install the recommended toolchain.

once this one works properly, you can repeat the steps for code sourcery g++ lite.

one important note, if running on 64-bit machines, install the required 32-bit libraries, otherwise the compiler cannot be executed.

invoke the compiler manually as recommended, to be sure it properly starts, before trying to use it from Eclipse.

Last edit: Liviu Ionescu (ilg) 2014-05-12

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Federico - 2014-05-15

Thank you for the suggestions, it seems that toolchains are not functional. After decompressing the tarball for the reccomended toolchain (in same folder as the Codesourcesy ones), the direct invokation of the compiler gives negative response:

Suggested toolchain, suggested verification command:
root@federico-VirtualBox:/opt/gcc-arm-none-eabi-4_8-2014q1# arm-none-eabi-gcc --version
The program 'arm-none-eabi-gcc' is currently not installed. You can install it by typing:
apt-get install gcc-arm-none-eabi

Previous toolchain, various commands:
root@federico-VirtualBox:/opt/CodeSourcery/Sourcery_G++_Lite/arm-2010q1# arm-none-eabi-gcc --version
The program 'arm-none-eabi-gcc' is currently not installed. You can install it by typing:
apt-get install gcc-arm-none-eabi
root@federico-VirtualBox:/opt/CodeSourcery/Sourcery_G++_Lite/arm-2010q1# arm-none-eabi-g++ -v
The program 'arm-none-eabi-g++' is currently not installed. You can install it by typing:
apt-get install gcc-arm-none-eabi
root@federico-VirtualBox:/opt/CodeSourcery/Sourcery_G++_Lite/arm-2010q1# arm-none-linux-gnueabi-gcc -v
arm-none-linux-gnueabi-gcc: command not found

I discovered that this virtual machine had at first the Sourcery 2010q1 toolchain installed (when the compiler was invoked directly it worked due to Ubuntu environment settings automatically done) and then removed.
When I started working on this machine I decompressed (no automatic installer used) the two Sourcery toolchains in different locations, but did not any direct verification of their funcitonality, going directly through Eclipse.
Now that I deleted the Ubuntu enviroment setting, addedd the reccomended toolchain (just decopressing following the instructions), verified that lib32 are correctly installed (lib32bz2-1.0 found), the verification fails...
Should I do the apt-get install gcc-arm-none-eabi? I'm afraid it will install beyond my control (settings PATH variables, unfriendly installation, difficulties to get rid of it path and so on) that I prefer to ask for some suggestion - even if I understand that is beyond your scope.

Any suggestion would be really welcome though, since I cannot go further in using the GNU Eclpse ARM in this situation.

Thanks again

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-05-15

You have a path problem. Please try the following:

remove ALL toolchain path references from any system or user profiles

as suggested in the documentation, start the compiler using the full path, for example

$ /opt/gcc-arm-none-eabi-4_8-2014q1/bin/arm-none-eabi-gcc --version

(mind the /bin part)

If the compiler does not start properly, you might need to install 2 specific 32-bit libraries (see the toolchain README file for details); the fact that you have lib32bz2 installed is not an indication that all 32-bit libraries are available.

After you check that the toolchain starts properly, Eclipse will also start it, assuming you provide the correct toolchain path (down to the last /bin part).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Federico - 2014-05-15

I did not have time to finish the suggested commands, but I can tell that both gcc and g++ check of the launchpad toolchain, using full path reference, are working but compiling gives me an error of "missing semaphore.h" (which should be already present in Linux environment). No further inbestigation of this. For Coudesourcery toolchains, gcc check is ok but not g++. It will take me some days to verify again all, including the lib32.

Thanks you for the patience it takes, and regards

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-05-15

ok, good luck.

I suggest we close this ticket since the reported problems are no longer due to the plug-ins.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Federico - 2014-05-20

I succeeded in compiling the project, here is what happened, maybe someone is interested.
- No additional references to toolchain path was existing neither in.bashrc or profile
- ia32-libs are not available for Ubuntu 13.10 and later, so I tried these (do not know if some can be skipped):
sudo apt-get install libgtk2.0-0:i386 libxtst6:i386 gtk2-engines-murrine:i386 \lib32stdc++6 libxt6:i386 libdbus-glib-1-2:i386 libasound2:i386

sudo apt-get install libc6:i386 libgcc1:i386 gcc-4.6-base:i386 libstdc++5:i386 libstdc++6:i386 libncurses5:i386

sudo apt-get install lib32z1 lib32ncurses5 lib32bz2-1.0

After a lot of different combinations, it seems that setting Eclipse build environment variable (from Windows menu -> preferences) and then import the project solved the problem.
Any trying to assign the correct toolchain after import (either via Eclipse variable or via project properties -> toolchain setting as gobal as well as local, for any toolchain available) did not have success (it could give error in not findinding the toolchain, not finding the make command, or not finding the semaphore.h file).
An Eclipse error maybe?

I noticed also a possible source of conflicts when, under project properties, build, environment, it's pressed Apply button even without any change just to check the values present. This will create another instance of the PATH variable. In fact, checking again the PATH value will un-grey the Delete button (and deleting will show the already existing variable) or will append another time the toolchain path to the variable value. Don't know which instance will overshadow the other or if they will conflict, because compilation was not working even after a correction.

Thanks for your support

Last edit: Federico 2014-05-20

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-05-20

ia32-libs are not available for Ubuntu 13.10 and later, so I tried these ...

looks like you completely messed your environment. if you are using the recommended toolchain, the accompanying readme clearly states what 32 bit libraries are required. you install them, check if the compiler starts in a terminal, and if so, go to Eclipse. it just works.

another instance of the PATH variable

unless you know exactly what you are doing, please do not manually change the project environment PATH, since this might invalidate the automatic use of the toolchain path.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Federico - 2014-05-22

Well, when I followed the blog instructions for ia32-libs, Ubuntu suggested: lib32z1 lib32ncurses5 lib32bz2-1.0. And official toolchain is really vague in the README: "For 64 bit system, 32 bit libc and libncurses are required to run the tools."
Which is not actually telling anything. So, was the problem due to 32 bit libraries?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-05-22

So, was the problem due to 32 bit libraries?

most probably

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Liviu Ionescu (ilg) - 2014-07-04

status: open --> closed

assigned_to: Liviu Ionescu (ilg)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Cannot set toolchain path

A family of Eclipse CDT extensions and tools for GNU ARM development.

Group

Searches

Help

#54 Cannot set toolchain path

Discussion