public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldot at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/107739] New: --enable-languages= duplicates yield odd error Date: Thu, 17 Nov 2022 20:17:27 +0000 [thread overview] Message-ID: <bug-107739-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107739 Bug ID: 107739 Summary: --enable-languages= duplicates yield odd error Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: aldot at gcc dot gnu.org Target Milestone: --- Mere cosmetics, but the error is contradicting it's own hint in a confusing way. $ ../../src/gcc-13.mine/configure --enable-languages=c++,lto,lto configure: error: The following requested languages could not be built: lto Supported languages are: c,c,c++,fortran,go,lto,objc,obj-c++ or other dups like $ ../../src/gcc-13.mine/configure --enable-languages=c++,c++,lto configure: error: The following requested languages could not be built: c++ Supported languages are: c,c,c++,fortran,go,lto,objc,obj-c++ I'm not sure why duplicates are not ignored silently.
next reply other threads:[~2022-11-17 20:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-17 20:17 aldot at gcc dot gnu.org [this message] 2022-11-17 22:30 ` [Bug bootstrap/107739] " pinskia at gcc dot gnu.org 2022-11-18 3:31 ` pinskia at gcc dot gnu.org 2022-11-18 3:45 ` pinskia at gcc dot gnu.org 2022-11-18 7:55 ` schwab@linux-m68k.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-107739-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).