From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27002 invoked by alias); 19 Aug 2004 16:07:21 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26745 invoked from network); 19 Aug 2004 16:07:18 -0000 Received: from unknown (HELO smtp6.mindspring.com) (207.69.200.110) by sourceware.org with SMTP; 19 Aug 2004 16:07:18 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp6.mindspring.com with esmtp (Exim 3.33 #1) id 1BxpRW-0004IG-00; Thu, 19 Aug 2004 12:07:10 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id C86334B102; Thu, 19 Aug 2004 12:07:25 -0400 (EDT) Date: Thu, 19 Aug 2004 16:07:00 -0000 From: Michael Chastain To: drow@false.org Subject: Re: [rfa/doco] Test Suite: build != host Cc: gdb-patches@sources.redhat.com, eliz@gnu.org Message-ID: <4124D03D.nail4DA118KPV@mindspring.com> References: <4124776A.nailCD81LG97@mindspring.com> <20040819132135.GA19467@nevyn.them.org> In-Reply-To: <20040819132135.GA19467@nevyn.them.org> User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00587.txt.bz2 Daniel Jacobowitz wrote: > I'd just like to say... one of the few examples you had in favor of > build != host testing was crosstool. Whoever gave you that example was > mistaken; crosstest.sh only supports host != target, so people are > probably -not- testing gcc with build != host. Rats, you are right. Or, rather, cool! You are right! I got my info from: http://kegel.com/crosstool/current/doc/dejagnu-remote-howto.html And somehow I got the impression that it was using --host. Which is just plain wrong; it's all about --target_board. > I still think this requirement is a bad idea, but it's your call. I'm not happy either way. I'm working towards a goal where anybody can run the doco; run the test bed on any configuration supported in the doco; and it always works and is useful. Like a real computer program! One very very hard part is figuring out how to co-operate with all the contributors and still do wrenching infrastructure upgrades. Michael