Here is the reason why:

The point was that the configure and make steps worked because the PATH was prepended with the location of the toolchain (e.g. gcc)

But sudo does not propagate the variables. Hence sudo make install ran commands with the wrong toolchain (the old gcc for instance).

One solution is to just use su

su # make install 

Here is the reason why:

The point was that the configure and make steps worked because the PATH was prepended with the location of the toolchain (e.g. gcc)

But sudo does not propagate the variables. Hence sudo make install ran commands with the wrong toolchain (the old gcc for instance).

One solution is to just use su

su # make install 

The point was that the configure and make steps worked because the PATH was prepended with the location of the toolchain (e.g. gcc)

But sudo does not propagate the variables. Hence sudo make install ran commands with the wrong toolchain (the old gcc for instance).

One solution is to just use su

su # make install 

Here is the reason why:

The point was that the configure and make steps worked because the PATH was prepended with the location of the toolchain (e.g. gcc)

But sudo does not propagate the variables. Hence sudo make install ran commands with the wrong toolchain (the old gcc for instance).

One solution is to just use su

su # make install