diff options
| author | Alexey Neyman <stilor@att.net> | 2015-10-27 21:42:11 -0700 |
|---|---|---|
| committer | Alexey Neyman <stilor@att.net> | 2015-10-27 23:58:41 -0700 |
| commit | 444db621a3e69247c958f684fae823038c7db8f8 (patch) | |
| tree | bbec85dff132b224c62d7e858ac991afd74aa727 /patches/gcc/4.4.0/370-bootstrap-target_lib_path.patch | |
| parent | 580f300ad9fbc9abbb6fcb1f037c352f0981b091 (diff) | |
| download | crosstool-ng-444db621a3e69247c958f684fae823038c7db8f8.tar.gz crosstool-ng-444db621a3e69247c958f684fae823038c7db8f8.tar.bz2 crosstool-ng-444db621a3e69247c958f684fae823038c7db8f8.zip | |
Disable cross-gdb in nios2-elf-mingw32.
Building cross-gdb in canadian cross requires expat/ncurses for the
host. Currently, 300-gdb.sh only builds expat/ncurses for the target
(for native-gdb). For cross-gdb on regular cross (build==host), expat
and ncurses are expected to be provided by the host.
There are two approaches possible:
- If building for canadian cross, build expat/ncurses for cross-gdb
just as the native-gdb does.
- Promote expat/ncurses to first class citizens and build them as
companion libs during the build of the build-to-host toolchain.
I am leaning towards the latter approach - it would also allow to
specify the versions for expat/ncurses rather than have them hardcoded
in 300-gdb.sh - but would appreciate feedback.
Signed-off-by: Alexey Neyman <stilor@att.net>
Diffstat (limited to 'patches/gcc/4.4.0/370-bootstrap-target_lib_path.patch')
0 files changed, 0 insertions, 0 deletions