From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15352 invoked by alias); 14 Feb 2014 11:12:39 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 15341 invoked by uid 89); 14 Feb 2014 11:12:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_SEMBACKSCATTER,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: e06smtp12.uk.ibm.com Received: from e06smtp12.uk.ibm.com (HELO e06smtp12.uk.ibm.com) (195.75.94.108) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 14 Feb 2014 11:12:38 +0000 Received: from /spool/local by e06smtp12.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 14 Feb 2014 11:12:34 -0000 Received: from d06dlp01.portsmouth.uk.ibm.com (9.149.20.13) by e06smtp12.uk.ibm.com (192.168.101.142) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 14 Feb 2014 11:12:31 -0000 Received: from b06cxnps4076.portsmouth.uk.ibm.com (d06relay13.portsmouth.uk.ibm.com [9.149.109.198]) by d06dlp01.portsmouth.uk.ibm.com (Postfix) with ESMTP id DC5B917D8077 for ; Fri, 14 Feb 2014 11:12:56 +0000 (GMT) Received: from d06av03.portsmouth.uk.ibm.com (d06av03.portsmouth.uk.ibm.com [9.149.37.213]) by b06cxnps4076.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s1EBCH6V50069622 for ; Fri, 14 Feb 2014 11:12:17 GMT Received: from d06av03.portsmouth.uk.ibm.com (localhost [127.0.0.1]) by d06av03.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s1EBCStC021048 for ; Fri, 14 Feb 2014 04:12:28 -0700 Received: from sandifor-thinkpad.stglab.manchester.uk.ibm.com (sig-9-145-144-119.de.ibm.com [9.145.144.119]) by d06av03.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s1EBCQhM020986 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Fri, 14 Feb 2014 04:12:27 -0700 From: Richard Sandiford To: Steve Ellcey Mail-Followup-To: Steve Ellcey ,"Joseph S. Myers" , , rsandifo@linux.vnet.ibm.com Cc: "Joseph S. Myers" , Subject: Re: [PATCH, testsuite] Fix profile test failures References: <2e4e3d80-6505-4f09-8a24-01e99dcda418@BAMAIL02.ba.imgtec.org> <1392335346.17835.98.camel@ubuntu-sellcey> Date: Fri, 14 Feb 2014 11:12:00 -0000 In-Reply-To: <1392335346.17835.98.camel@ubuntu-sellcey> (Steve Ellcey's message of "Thu, 13 Feb 2014 15:49:06 -0800") Message-ID: <87ppmqrlra.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14021411-8372-0000-0000-000008AB1373 X-SW-Source: 2014-02/txt/msg00899.txt.bz2 Steve Ellcey writes: > On Thu, 2014-02-13 at 23:09 +0000, Joseph S. Myers wrote: >> On Thu, 13 Feb 2014, Steve Ellcey wrote: >> >> > While testing the C++ profiling tests in g++.dg/bprob and using the >> > qemu simulator we discovered that these tests were passing when we ran >> > the testsuite with no extra options but that if we specified some options >> > on the testsuite run then the tests would fail with this message in the >> > c++.log file: >> > >> > rsh: Could not resolve hostname multi-sim/-EL: Name or service not known >> >> That means your board file is buggy. If rsh is not the right way to >> access your target system, you need to implement the board file methods in >> some way other than rsh (possibly some operations should be no-ops, or do >> something directly on the build system, if you have a shared filesystem). > > I thought the bug was that it was using 'multi-sim/-EL' instead of just > 'multi-sim'. I.e. I thought that target was a combination of where the > test was run and what options were used, whereas host was just going to > be where the test was run. I guess I was wrong about that. Using target in itself should be OK. The hostname for rsh/ssh should be [board_info $board hostname] rather than $board itself. So in this case [board_info "multi-sim/-EL" hostname] should be multi-sim. The usual way to set that up is to put: set_board_info hostname multi-sim in multi-sim.exp. Thanks, Richard