diff options
| author | Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> | 2011-10-14 22:44:24 +0200 |
|---|---|---|
| committer | Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> | 2011-10-14 22:44:24 +0200 |
| commit | e2b9a81da34023db468b61caecf1b4799016f174 (patch) | |
| tree | 6bdb3dc39eb5a490d49823b07b336a260cb0a6f9 /config/debug | |
| parent | 6e00f49ab44487694fd0e68a3f4b2c4f43f72afe (diff) | |
| download | crosstool-ng-e2b9a81da34023db468b61caecf1b4799016f174.tar.gz crosstool-ng-e2b9a81da34023db468b61caecf1b4799016f174.tar.bz2 crosstool-ng-e2b9a81da34023db468b61caecf1b4799016f174.zip | |
scripts: check host features with host compiler
Currently, we check host feature in ./configure. This works only for
cross toolchains, but not for canadian toolchains. ./configure has
absolutely no way to know what the host for the toolchain will be;
only the build scripts know.
So, move the headers & libraries checks from ./configure to the build
scripts, early enough in the build, but not before we know the host
compiler and other tools.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Diffstat (limited to 'config/debug')
| -rw-r--r-- | config/debug/gdb.in.cross | 12 | ||||
| -rw-r--r-- | config/debug/gdb.in.native | 4 |
2 files changed, 1 insertions, 15 deletions
diff --git a/config/debug/gdb.in.cross b/config/debug/gdb.in.cross index 633def38..d9e80d4b 100644 --- a/config/debug/gdb.in.cross +++ b/config/debug/gdb.in.cross @@ -3,18 +3,10 @@ config STATIC_TOOLCHAIN select GDB_CROSS_STATIC if GDB_CROSS -comment "Cross-gdb - disabled (requires expat; re-run ./configure to enable)" - depends on !CONFIGURE_has_expat - -comment "Static cross-gdb - disabled (requires static expat; re-run ./configure to enable)" - depends on STATIC_TOOLCHAIN && !CONFIGURE_has_static_expat - config GDB_CROSS bool prompt "Cross-gdb" default y - depends on CONFIGURE_has_expat - depends on !STATIC_TOOLCHAIN || CONFIGURE_has_static_expat select GDB_GDBSERVER if ! BARE_METAL help Build and install a cross-gdb for the target, to run on host. @@ -24,8 +16,7 @@ if GDB_CROSS config GDB_CROSS_STATIC bool prompt "Build a static cross gdb" - depends on CONFIGURE_static_link_ok - depends on CONFIGURE_has_static_expat + select WANTS_STATIC_LINK help A static cross gdb can be usefull if you debug on a machine that is not the one that is used to compile the toolchain. @@ -36,7 +27,6 @@ config GDB_CROSS_STATIC config GDB_CROSS_PYTHON bool prompt "Enable python scripting" - depends on CONFIGURE_has_python depends on ! GDB_CROSS_STATIC default y help diff --git a/config/debug/gdb.in.native b/config/debug/gdb.in.native index a4144b43..8d2159af 100644 --- a/config/debug/gdb.in.native +++ b/config/debug/gdb.in.native @@ -10,13 +10,9 @@ config GDB_NATIVE if GDB_NATIVE -config GDB_NATIVE_NO_STATIC - bool - config GDB_NATIVE_STATIC bool prompt "Build a static native gdb" - depends on ! GDB_NATIVE_NO_STATIC help In case you have trouble with dynamic loading of shared libraries, you will find that a static gdb comes in handy. |