This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
PATCH: Build testsuite executables with -no-install
- To: java-patches at gcc dot gnu dot org
- Subject: PATCH: Build testsuite executables with -no-install
- From: Jeff Sturm <jsturm at one-point dot com>
- Date: Mon, 4 Jun 2001 23:55:49 -0400 (EDT)
I'm often frustrated while debugging testsuite failures by the wrapper
scripts generated by libtool. After learning more about libtool (thanks
to the New Riders book) I figured this is a good place to use -no-install.
On i686-pc-linux-gnu at least, it prevents creating the wrapper scripts
and makes the testsuite slightly smaller/faster.
Are there any downsides to this?
2001-06-04 Jeff Sturm <jsturm@one-point.com>
* libjava.exp: Add -no-install flag to testsuite builds.
Index: libjava.exp
===================================================================
RCS file: /cvs/gcc/gcc/libjava/testsuite/lib/libjava.exp,v
retrieving revision 1.22.4.4
diff -u -r1.22.4.4 libjava.exp
--- libjava.exp 2001/05/04 19:32:15 1.22.4.4
+++ libjava.exp 2001/06/01 01:23:37
@@ -361,6 +361,7 @@
if {! [info exists opts(no-link)]} {
# Add the --main flag
lappend args "additional_flags=--main=[file rootname [file tail $srcfile]]"
+ lappend args "additional_flags=-no-install"
if { $compile_args != "" } {
lappend args "additional_flags=$compile_args"
}
@@ -590,6 +591,7 @@
} else {
set type executable
lappend largs "additional_flags=--main=$main_name"
+ lappend largs "additional_flags=-no-install"
set executable "${objdir}/$main_name"
set mode link
}