V3 PATCH: Use -rpath, not --rpath, when testing

[Mark Mitchell]

The V3 test script uses `--rpath' when creating an executable linked
against a shared libstdc++.  That works with GNU ld, but not probably
with many other linkers.  (It doesn't work with IRIX ld, in
particular.)

I've changed this to use `-rpath', and V3 is now mostly passing tests
on IRIX.

Since V3 is all libtoolized, why not use libtool here?  The current
scheme isn't going to work well on systems (like Solaris) that don't
use -rpath; Solaris uses -R instead, IIRC.

Tested on i686-pc-linux-gnu and mips-sgi-irix6.5.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

2000-10-29  Mark Mitchell  <mark@codesourcery.com>

	* mkcheck.in (test_file): Use -rpath, rather than --rpath, when
	building shared executables.

Index: mkcheck.in
===================================================================
RCS file: /cvs/gcc/egcs/libstdc++-v3/mkcheck.in,v
retrieving revision 1.27
diff -c -p -r1.27 mkcheck.in
*** mkcheck.in	2000/10/26 07:28:25	1.27
--- mkcheck.in	2000/10/30 00:26:27
*************** test_file()
*** 198,204 ****
      # eventually have to calculate time_t anyhow.  Or 3) just grab two
      # time_t's (no more overhead than grabbing two date(1)'s).
      COMP_TIME_START=$($TEST_DIR/printnow)
!     $CXX $CXX_FLAG $S_FLAG $INC_PATH -L$LIB_PATH -Wl,--rpath -Wl,$LIB_PATH \
           $SRC_NAME -o $EXENAME 2>> $LOG_FILE
      COMP_TIME_END=$($TEST_DIR/printnow)
  
--- 198,204 ----
      # eventually have to calculate time_t anyhow.  Or 3) just grab two
      # time_t's (no more overhead than grabbing two date(1)'s).
      COMP_TIME_START=$($TEST_DIR/printnow)
!     $CXX $CXX_FLAG $S_FLAG $INC_PATH -L$LIB_PATH -Wl,-rpath -Wl,$LIB_PATH \
           $SRC_NAME -o $EXENAME 2>> $LOG_FILE
      COMP_TIME_END=$($TEST_DIR/printnow)