CODEWITHSUNDEEP
gcccross-compiling
krokoziabla
krokoziabla

Reputation: 775

bin/arm-none-eabi-gcc vs. arm-none-eabi/bin/gcc

What's the difference between them?

I took this example from CodeSourcery toolchain but I've met similar structure in other toolchains.

Both of them appear to have the same size. On my Linux host the files have different i-nodes, so those are two different files.

Is it just for naming convenience?

I've come across at least one difference although I'm not sure if it is a real difference and not a bug. If I run

<installation path>/bin/arm-none-eabi-gcc -v -xc -

in order to see the default include paths I get some. But if I do the same with

<installation path>/arm-none-eabi/bin/gcc -v -xc -

then the list of paths is empty.

Does anyone know the truth about it?

Upvotes: 2

Views: 1071

Answers (1)

LB--
LB--

Reputation: 2928

In <installation>/bin you have the official executables which should be used, whereas in <installation>/<target>/bin you have executables for internal use only - you should not invoke them, and they should not be in your PATH.

As a reference, there is actually a README.txt in that folder telling you what they are for and why you should not use them or have them in your PATH.

Upvotes: 2

Related Questions