Use the arch-specific target LDFLAGS into the final target LDFLAGS.
Fix a help entry in the CFLAGS_for_target config entry.
/trunk/scripts/crosstool.sh | 4 3 1 0 +++-
/trunk/config/target.in | 2 1 1 0 +-
2 files changed, 4 insertions(+), 2 deletions(-)
1.1 --- a/config/target.in Sat May 24 22:10:51 2008 +0000
1.2 +++ b/config/target.in Sat May 24 22:38:07 2008 +0000
1.3 @@ -244,7 +244,7 @@
1.4 Used to add specific options when compiling libraries of the toolchain,
1.5 that will run on the target (eg. libc.so).
1.6
1.7 - Note that the options above for CPU, tune, arch and FPU will be
1.8 + Note that the options above for ARCH, ABI, CPU, TUNE and FPU will be
1.9 automaticaly used. You don't need to specify them here.
1.10
1.11 Leave blank if you don't know better.
2.1 --- a/scripts/crosstool.sh Sat May 24 22:10:51 2008 +0000
2.2 +++ b/scripts/crosstool.sh Sat May 24 22:38:07 2008 +0000
2.3 @@ -72,8 +72,10 @@
2.4 . "${CT_TOP_DIR}/.config"
2.5
2.6 # Second kludge: merge user-supplied target CFLAGS with architecture-provided
2.7 -# target CFLAGS
2.8 +# target CFLAGS. Do the same for LDFLAGS in case it happens in the future.
2.9 +# Put user-supplied flags at the end, so that they take precedence.
2.10 CT_TARGET_CFLAGS="${CT_ARCH_TARGET_CFLAGS} ${CT_TARGET_CFLAGS}"
2.11 +CT_TARGET_LDFLAGS="${CT_ARCH_TARGET_LDFLAGS} ${CT_TARGET_LDFLAGS}"
2.12
2.13 # Now, build up the variables from the user-configured options.
2.14 CT_KERNEL_FILE="${CT_KERNEL}-${CT_KERNEL_VERSION}"