public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/26478] New: [4.2 Regression] bootstrap fails with readonly source directory Date: Mon, 27 Feb 2006 03:27:00 -0000 [thread overview] Message-ID: <bug-26478-230@http.gcc.gnu.org/bugzilla/> (raw) Bootstrap (e.g. on i686-pc-linux-gnu) fails if the source directory is readonly (if the individual files are readonly, chmod -R a-w srcdir). To test this it suffices to "chmod a-w gcc/unwind-generic.h" then bootstrap, and it fails with cp ../../gcc-mainline/gcc/unwind-generic.h include/unwind.h cp: cannot create regular file `include/unwind.h': Permission denied make[3]: *** [stmp-int-hdrs] Error 1 rm fsf-funding.pod gfdl.pod cpp.pod gpl.pod gcov.pod gcc.pod make[3]: Leaving directory `/home/jsm28/src/gcc-build/gcc' make[2]: *** [all-stage2-gcc] Error 2 make[2]: Leaving directory `/home/jsm28/src/gcc-build' make[1]: *** [stage2-bubble] Error 2 make[1]: Leaving directory `/home/jsm28/src/gcc-build' make: *** [bootstrap] Error 2 because the previously copied file is readonly. This appeared between revision 111294 and revision 111327 of trunk and is still present as of revision 111469. -- Summary: [4.2 Regression] bootstrap fails with readonly source directory Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jsm28 at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26478
next reply other threads:[~2006-02-27 3:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-27 3:27 jsm28 at gcc dot gnu dot org [this message] 2006-02-27 3:29 ` [Bug bootstrap/26478] " pinskia at gcc dot gnu dot org 2006-02-27 3:41 ` pinskia at gcc dot gnu dot org 2006-03-03 0:31 ` jsm28 at gcc dot gnu dot org 2006-03-03 18:21 ` pinskia at gcc dot gnu dot org
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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-26478-230@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe 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).