public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: <bug-automake@gnu.org>,  <gcc@gcc.gnu.org>,  <libstdc++@gcc.gnu.org>
Subject: Cross-testing: check-target-libstdc++-v3 with dejagnu in build tree.
Date: Tue, 23 Apr 2002 11:53:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.30.0204231436330.11541-100000@dair.pair.com> (raw)

I use this patch locally so I can make check-target-libstdc++-v3
with dejagnu in the build tree, using the dejagnu at sourceware
(cf. <URL:http://gcc.gnu.org/simtest-howto.html>) which was
recently synched with FSF dejagnu (thanks to Nick Clifton).

The patch is no good as is, since Makefile.in in
libstdc++-v3/testsuite is generated from Makefile.am, and this
check-DEJAGNU rule is an automake-generated thingy.  I think it
exposes a problem with automake, which seems to by default
assume that libraries are only tested as host libraries, in
which case the library dir is one .. closer to the host expect
build dir.

IIRC the automake documented remedy is to enter the
check-DEJAGNU rule manually in Makefile.am, but I think the
automake-generated rule needs fixing too.  It seems "automake
1.4-p5" was used to generate this Makefile.in (please forgive me
for not digging deeper, particularly into newer automake
versions).  I don't really know how or if the test should be
tweaked to deal with the case where libstdc++-v3 is a multilib.

Thoughts?

Index: Makefile.in
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/testsuite/Makefile.in,v
retrieving revision 1.20.2.2
diff -p -c -r1.20.2.2 Makefile.in
*** Makefile.in	2 Apr 2002 02:47:07 -0000	1.20.2.2
--- Makefile.in	23 Apr 2002 18:16:04 -0000
*************** RUNTESTDEFAULTFLAGS = --tool $(DEJATOOL)
*** 212,218 ****
  check-DEJAGNU: site.exp
  	srcdir=`cd $(srcdir) && pwd`; export srcdir; \
  	EXPECT=$(EXPECT); export EXPECT; \
! 	if [ -f $(top_builddir)/../expect/expect ]; then \
  	  TCL_LIBRARY=`cd $(top_srcdir)/../tcl/library && pwd`; \
  	  export TCL_LIBRARY; \
  	fi; \
--- 212,219 ----
  check-DEJAGNU: site.exp
  	srcdir=`cd $(srcdir) && pwd`; export srcdir; \
  	EXPECT=$(EXPECT); export EXPECT; \
! 	if [ -f $(top_builddir)/../expect/expect ] \
! 	   || [ -f $(top_builddir)/../../expect/expect ]; then \
  	  TCL_LIBRARY=`cd $(top_srcdir)/../tcl/library && pwd`; \
  	  export TCL_LIBRARY; \
  	fi; \

brgds, H-P

             reply	other threads:[~2002-04-23 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 11:53 Hans-Peter Nilsson [this message]
2002-04-24 16:35 ` Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.BSF.4.30.0204231436330.11541-100000@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=bug-automake@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).