public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tstellar at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/97524] New: Compiling with -flto=auto fails in make is not installed Date: Wed, 21 Oct 2020 19:19:58 +0000 [thread overview] Message-ID: <bug-97524-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97524 Bug ID: 97524 Summary: Compiling with -flto=auto fails in make is not installed Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: tstellar at redhat dot com CC: marxin at gcc dot gnu.org Target Milestone: --- Compiling with -flto=auto does not work when make is not installed. The documentation for -flto=auto says it should fallback to autodetection when the make job server is not available. Instructions to reproduce: On a system without make installed run: echo "void main() { }" | gcc -x c -flto=auto - Command output: lto-wrapper: fatal error: execvp: No such file or directory compilation terminated. /usr/bin/ld: error: lto-wrapper failed collect2: error: ld returned 1 exit status
next reply other threads:[~2020-10-21 19:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-21 19:19 tstellar at redhat dot com [this message] 2020-10-22 6:32 ` [Bug lto/97524] " marxin at gcc dot gnu.org 2020-10-22 7:15 ` jakub at gcc dot gnu.org 2020-10-22 7:22 ` rguenth at gcc dot gnu.org 2020-10-22 7:25 ` marxin at gcc dot gnu.org 2020-10-22 12:09 ` marxin at gcc dot gnu.org 2020-10-22 14:05 ` tstellar at redhat dot com 2020-10-23 7:03 ` marxin at gcc dot gnu.org 2020-10-23 7:48 ` cvs-commit at gcc dot gnu.org 2020-10-23 7:55 ` marxin 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-97524-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).