From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15513 invoked by alias); 24 Apr 2002 23:31:46 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 15466 invoked from network); 24 Apr 2002 23:31:43 -0000 Received: from unknown (HELO gash2.peakpeak.com) (207.174.178.17) by 209.249.29.67 with SMTP; 24 Apr 2002 23:31:43 -0000 Received: from creche.cygnus.com (ta0198.peakpeak.com [204.144.244.198]) by gash2.peakpeak.com (8.9.3/8.9.3) with ESMTP id RAA14889; Wed, 24 Apr 2002 17:31:26 -0600 Received: (from tromey@localhost) by creche.cygnus.com (8.9.3/8.9.3) id RAA12993; Wed, 24 Apr 2002 17:37:44 -0600 To: Hans-Peter Nilsson Cc: , , Subject: Re: Cross-testing: check-target-libstdc++-v3 with dejagnu in build tree. References: From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom X-Zippy: Do you think the ``Monkees'' should get gas on odd or even days? Date: Wed, 24 Apr 2002 16:35:00 -0000 In-Reply-To: Hans-Peter Nilsson's message of "Tue, 23 Apr 2002 14:42:00 -0400 (EDT)" Message-ID: <871yd44qig.fsf@creche.redhat.com> X-SW-Source: 2002-04/txt/msg01270.txt.bz2 >>>>> ">" == Hans-Peter Nilsson writes: >> 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. Yes. This code was written a long time ago -- I think it was 1996 -- and as far as I know hasn't changed substantially since then. Back then I knew nothing about target libraries or multilibbing, so I ignored those features. >> 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. Actually, doing it by hand is a hack. This isn't an exported name, so it could change from release to release. Someday it will (when we start moving internal targets to their own namespace). >> I don't really know how or if the test should be tweaked to deal >> with the case where libstdc++-v3 is a multilib. That's the issue. Someone has to just sit down and figure out how we can get information about the "real" top-of-tree, and then put this into dejagnu.am. Could you submit an automake PR for this problem? That way we can at least track it. You can find Gnats by following links from the home page: http://sources.redhat.com/automake/ Thanks. Tom