From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8137 invoked by alias); 7 Nov 2012 10:38:39 -0000 Received: (qmail 8104 invoked by uid 22791); 7 Nov 2012 10:38:38 -0000 X-SWARE-Spam-Status: No, hits=-4.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-lb0-f175.google.com (HELO mail-lb0-f175.google.com) (209.85.217.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 07 Nov 2012 10:38:30 +0000 Received: by mail-lb0-f175.google.com with SMTP id y2so1170027lbk.20 for ; Wed, 07 Nov 2012 02:38:29 -0800 (PST) Received: by 10.152.105.44 with SMTP id gj12mr3846137lab.19.1352284708957; Wed, 07 Nov 2012 02:38:28 -0800 (PST) Received: from [10.15.38.163] ([92.103.127.250]) by mx.google.com with ESMTPS id b8sm7905773lbn.8.2012.11.07.02.38.27 (version=SSLv3 cipher=OTHER); Wed, 07 Nov 2012 02:38:28 -0800 (PST) Message-ID: <509A3A22.5060706@gmail.com> Date: Wed, 07 Nov 2012 10:38:00 -0000 From: Aurelien Buhrig User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: gcc-help@gcc.gnu.org Subject: Testing a Canadian cross Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2012-11/txt/msg00025.txt.bz2 Hi, I successfully build a canadian croos gcc for a private target on a linux x64 build machine for a windows host (mingw32). I suppose I can test such a compiler on the host machine (setting up dejagnu/expect, a site.exp and the target simulator (sid) on the windows host). But in order to centralize on a single machine the build and the test of binary releases for different hosts, I wonder if there is a way to test such a compiler on (or from) the build machine, using an emulator, a RPC-like or whatever. Perhaps this is an issue someone has already addressed hereby? Thanks, Aurélien