public inbox for
 help / color / mirror / Atom feed
From: "Jan Beulich" <>
To: <>
Subject: libjava build failure with read-only source tree
Date: Thu, 29 Sep 2011 08:18:00 -0000	[thread overview]
Message-ID: <> (raw)

When the source tree (including its directories) is read-only I get

rm: cannot remove `asm/org/objectweb/asm/xml/ASMContentHandler$LineNumberRule.class': Permission denied
rm: cannot remove `asm/org/objectweb/asm/xml/ASMContentHandler$ExceptionsRule.class': Permission denied
... (hundreds of similar messages)
rm: cannot remove `classes/sun/rmi/rmic/': Permission denied
rm: cannot remove `classes/sun/rmi/rmic/Messages.class': Permission denied
make[4]: *** [] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-target-libjava] Error 2

as an obvious result of using 

	cp -pR $(srcdir)/asm .
	cp -pR $(srcdir)/classes .

in the commands of the $(TOOLS_ZIP) rule.

This is the change I'm currently checking whether it will overcome the

--- a/libjava/classpath/tools/
+++ b/libjava/classpath/tools/
@@ -371,6 +371,7 @@ endif
 	cp -pR $(srcdir)/asm .
 	cp -pR $(srcdir)/classes .
+	find asm classes -type d -exec chmod u+w \{\} \;
 	if [ -d asm/.svn ]; then \
 	  find asm classes -depth -type d -name .svn -exec rm -rf \{\} \;; \

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?

Regards, Jan

             reply	other threads:[~2011-09-29  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29  8:18 Jan Beulich [this message]
2011-09-29  8:40 ` Bryce McKinlay
2011-09-29  9:06   ` Jan Beulich
2011-09-29  9:32 ` Bryce McKinlay
2011-09-29  9:34   ` Andrew Haley
2011-09-29  9:48   ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).