libjava build failure with read-only source tree

Thu Sep 29 08:40:00 GMT 2011

On Thu, Sep 29, 2011 at 9:18 AM, Jan Beulich <JBeulich@suse.com> 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