mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2024-12-22 06:07:49 +00:00
89273b59af
In currently generated top-level "nano.specs" we resolve paths during toolchain building and then use those pre-defined full paths once the toolchain got built. That's OK until the toolchain is used right were it was built, otherwise paths used in the top-level "nano.specs" become irrelevant and linker fails to find "nano" libs reverting to non-"nano" libs in the default location. See https://github.com/crosstool-ng/crosstool-ng/issues/1491. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> |
||
|---|---|---|
| .. | ||
| build | ||
| override | ||
| upgrade | ||
| compile | ||
| config.guess | ||
| config.rpath | ||
| config.sub | ||
| crosstool-NG.sh | ||
| depcomp | ||
| functions | ||
| install-sh | ||
| ltmain.sh | ||
| missing | ||
| populate.in | ||
| saveSample.sh | ||
| scripts.mk | ||
| show-config.sh | ||
| show-tuple.sh | ||
| toolchain-config.in | ||
| version-check.sh | ||
| xldd.in | ||