This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch, testsuite] set GCC_EXEC_PREFIX *before* building testglue.c
- From: DJ Delorie <dj at redhat dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Fri, 14 Aug 2009 14:57:28 -0400
- Subject: [patch, testsuite] set GCC_EXEC_PREFIX *before* building testglue.c
I suspect this may be obvious, but that doesn't mean there aren't
hidden side-effects. When you test in-tree with a cross target
requiring a status wrapper, the status wrapper can't be built because
GCC_EXEC_PREFIX hasn't been set yet. This sets it if needed. Ok to
apply?
* lib/wrapper.exp (${tool}_maybe_build_wrapper): Set up
GCC_EXEC_PREFIX before building the wrapper.
2009-08-13 Janus Weil <janus@gcc.gnu.org>
Index: lib/wrapper.exp
===================================================================
--- lib/wrapper.exp (revision 150735)
+++ lib/wrapper.exp (working copy)
@@ -13,23 +13,26 @@
# You should have received a copy of the GNU General Public License
# along with GCC; see the file COPYING3. If not see
# <http://www.gnu.org/licenses/>.
# This file contains GCC-specifics for status wrappers for test programs.
+load_lib target-libpath.exp
+
# ${tool}_maybe_build_wrapper -- Build wrapper object if the target
# needs it. FILENAME is the path to the wrapper file. If there are
# additional arguments, they are command-line options to provide to
# the compiler when compiling FILENAME.
proc ${tool}_maybe_build_wrapper { filename args } {
global gluefile wrap_flags
if { [target_info needs_status_wrapper] != "" \
&& [target_info needs_status_wrapper] != "0" \
&& ![info exists gluefile] } {
+ set_ld_library_path_env_vars
set saved_wrap_compile_flags [target_info wrap_compile_flags]
set flags [join $args " "]
# The wrapper code may contain code that gcc objects on. This
# became true for dejagnu-1.4.4. The set of warnings and code
# that gcc objects on may change, so just make sure -w is always
# passed to turn off all warnings.