public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/98314] New: [11 Regression] Install fails with "install -C" Date: Wed, 16 Dec 2020 09:49:56 +0000 [thread overview] Message-ID: <bug-98314-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98314 Bug ID: 98314 Summary: [11 Regression] Install fails with "install -C" Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: rsandifo at gcc dot gnu.org CC: nathan at gcc dot gnu.org Target Milestone: --- It can be convenient to do: make install INSTALL="/path/to/install -C" to avoid touching files that haven't in fact changed (and so avoid rebuilds of makefile rules that depend on the timestamps of the installed tools). That no longer works with c++tools: /usr/bin/install -C -p g++-mapper-server …/libexec/gcc/aarch64-none-linux-gnu/11.0.0 /usr/bin/install: options --compare (-C) and --preserve-timestamps are mutually exclusive Try '/usr/bin/install --help' for more information. Makefile:92: recipe for target 'install' failed I guess the simplest fix is to drop the -p, but maybe that's bad for other reasons.
next reply other threads:[~2020-12-16 9:49 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-16 9:49 rsandifo at gcc dot gnu.org [this message] 2020-12-16 12:58 ` [Bug bootstrap/98314] " nathan at gcc dot gnu.org 2020-12-16 14:15 ` rsandifo 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-98314-4@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).