From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3052 invoked by alias); 29 Sep 2011 08:40:18 -0000 Received: (qmail 3009 invoked by uid 22791); 29 Sep 2011 08:40:17 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_IB X-Spam-Check-By: sourceware.org Received: from mail-qy0-f175.google.com (HELO mail-qy0-f175.google.com) (209.85.216.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Sep 2011 08:39:43 +0000 Received: by qyk10 with SMTP id 10so3167540qyk.20 for ; Thu, 29 Sep 2011 01:39:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.62.195 with SMTP id y3mr7570372qch.31.1317285582214; Thu, 29 Sep 2011 01:39:42 -0700 (PDT) Received: by 10.229.74.81 with HTTP; Thu, 29 Sep 2011 01:39:41 -0700 (PDT) In-Reply-To: <4E8445DE0200007800058686@nat28.tlf.novell.com> References: <4E8445DE0200007800058686@nat28.tlf.novell.com> Date: Thu, 29 Sep 2011 08:40:00 -0000 Message-ID: Subject: Re: libjava build failure with read-only source tree From: Bryce McKinlay To: Jan Beulich Cc: java@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org X-SW-Source: 2011-09/txt/msg00020.txt.bz2 On Thu, Sep 29, 2011 at 9:18 AM, Jan Beulich wrote: > As this isn't the first time I encounter this in the libjava subtree, can it > be made a requirement for testing changes that they must work with > fully read-only source trees? And/or if there's some sort of automatic > testing in place, could that be adjusted to include a respective check? It would be heavy-handed to require every contributor to test patches with a read-only tree. We don't want to make the patch submission process any more onerous than it already is. Adjusting one of the automated regression testers to run its builds on a read-only tree would probably make sense, however. There are several regression testers operating - see the gcc-testresults list for details. Bryce