scripts: check for, and warn about an unset CT_PREFIX_DIR

The user shall provide a directory to install the toolchain into.
If he/she does not, this is an error, and shall be detected properly,
rather than relying on failure down the road.

Thanks to "Pedro I. Sanchez" <psanchez@colcan.ca> for pointing out
the issue:
  http://sourceware.org/ml/crossgcc/2009-12/msg00011.html
(transplanted from e94f4ffddd1d07b3841160db71694cd19fda6b03)
This commit is contained in:
Yann E. MORIN" 2009-12-19 12:44:21 +01:00
parent 5b4be4bafd
commit f96424f56f

View File

@ -134,6 +134,9 @@ CT_DoBuildTargetTuple
# then rescan the options file now: # then rescan the options file now:
. .config . .config
# Sanity check some directories
CT_TestAndAbort "'CT_PREFIX_DIR' is not set: where should I install?" -z "${CT_PREFIX_DIR}"
# Second kludge: merge user-supplied target CFLAGS with architecture-provided # Second kludge: merge user-supplied target CFLAGS with architecture-provided
# target CFLAGS. Do the same for LDFLAGS in case it happens in the future. # target CFLAGS. Do the same for LDFLAGS in case it happens in the future.
# Put user-supplied flags at the end, so that they take precedence. # Put user-supplied flags at the end, so that they take precedence.