public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/111027] [11/12/13/14 Regression] `make install` touches the build directory; Install error "tmp-header-vars: Permission denied", build on NFS, improvement possible
Date: Sun, 20 Aug 2023 08:16:14 +0000 [thread overview]
Message-ID: <bug-111027-4-AoOCuojRQ2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111027-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111027
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |4.5.0
Known to work| |4.4.0
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Summary|Install error |[11/12/13/14 Regression]
|"tmp-header-vars: |`make install` touches the
|Permission denied", build |build directory; Install
|on NFS, improvement |error "tmp-header-vars:
|possible |Permission denied", build
| |on NFS, improvement
| |possible
Target Milestone|--- |11.5
Last reconfirmed| |2023-08-20
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.
Introduced in r0-97381-g090fa0ab610a for GCC 4.5.0 so it is techincally a
regression.
next prev parent reply other threads:[~2023-08-20 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 10:51 [Bug other/111027] New: " etienne_lorrain at yahoo dot fr
2023-08-15 13:43 ` [Bug other/111027] " rguenth at gcc dot gnu.org
2023-08-16 23:58 ` pinskia at gcc dot gnu.org
2023-08-20 8:16 ` pinskia at gcc dot gnu.org [this message]
2023-08-21 12:12 ` [Bug bootstrap/111027] [11/12/13/14 Regression] `make install` touches the build directory; " etienne_lorrain at yahoo dot fr
2023-08-23 8:06 ` etienne_lorrain at yahoo dot fr
2024-03-07 23:24 ` law at gcc dot gnu.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-111027-4-AoOCuojRQ2@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: 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).