392b0a26f5
It makes no sense to default to an arbitrary path. In addition, it in fact works correctly when it is empty. In that case, the toolchain will be searched in PATH. Update the help text to explain the above, and also that the compiler is supposed to be in the bin subdirectory. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> |
||
|---|---|---|
| .. | ||
| toolchain-external-codescape-img-mips | ||
| toolchain-external-codescape-mti-mips | ||
| toolchain-external-codesourcery-aarch64 | ||
| toolchain-external-codesourcery-amd64 | ||
| toolchain-external-codesourcery-arm | ||
| toolchain-external-codesourcery-mips | ||
| toolchain-external-codesourcery-niosII | ||
| toolchain-external-custom | ||
| toolchain-external-linaro-aarch64 | ||
| toolchain-external-linaro-arm | ||
| toolchain-external-linaro-armeb | ||
| toolchain-external-synopsys-arc | ||
| Config.in | ||
| pkg-toolchain-external.mk | ||
| toolchain-external.mk | ||