public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dilfridge at gentoo dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/111406] New: libiberty build produces errors with CC=clang, unsupported option '-print-multi-os-directory' Date: Wed, 13 Sep 2023 15:27:31 +0000 [thread overview] Message-ID: <bug-111406-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111406 Bug ID: 111406 Summary: libiberty build produces errors with CC=clang, unsupported option '-print-multi-os-directory' Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: dilfridge at gentoo dot org Target Milestone: --- This is a clone of https://bugs.gentoo.org/913750 With CC=clang, the build of libiberty (as part of gnu binutils) produces errors clang-16: error: unsupported option '-print-multi-os-directory' clang-16: error: no input files However, the build continues apparently fine... This stems from libiberty/Makefile.am: 385 # This is tricky. Even though CC in the Makefile contains 386 # multilib-specific flags, it's overridden by FLAGS_TO_PASS from the 387 # default multilib, so we have to take CFLAGS into account as well, 388 # since it will be passed the multilib flags. 389 MULTIOSDIR = `$(CC) $(CFLAGS) -print-multi-os-directory`
next reply other threads:[~2023-09-13 15:27 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-13 15:27 dilfridge at gentoo dot org [this message] 2023-09-13 15:31 ` [Bug other/111406] " pinskia at gcc dot gnu.org 2023-09-13 15:34 ` dilfridge at gentoo dot org 2023-09-14 9:21 ` rguenth at gcc dot gnu.org 2023-09-15 19:38 ` dilfridge at gentoo 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-111406-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).