[Bug other/111406] New: libiberty build produces errors with CC=clang, unsupported option '-print-multi-os-directory'

[Bug other/111406] New: libiberty build produces errors with CC=clang, unsupported option '-print-multi-os-directory'

[dilfridge at gentoo dot org]

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`

[Bug other/111406] libiberty build produces errors with CC=clang, unsupported option '-print-multi-os-directory'

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111406

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>This stems from libiberty/Makefile.am:

You mean Makefile.in, libiberty does not use automake.

[Bug other/111406] libiberty build produces errors with CC=clang, unsupported option '-print-multi-os-directory'

[dilfridge at gentoo dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111406

--- Comment #2 from Andreas K. Huettel <dilfridge at gentoo dot org> ---
Indeed, sorry

https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=libiberty/Makefile.in#l388

[Bug other/111406] libiberty build produces errors with CC=clang, unsupported option '-print-multi-os-directory'

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111406

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
These are only used in the install targets which when bootstrapped will have
used GCC from earlier stages.  When building cross compilers we require GCC as
host compiler.

So I think this isn't an issue unless you try to build libiberty stand-alone
or as part of binutils and also install it?

The sourceware bugzilla instance also doesn't have a libiberty component,
so tracking it here is possibly good enough but as said above you'll not hit
it in practice?

[Bug other/111406] libiberty build produces errors with CC=clang, unsupported option '-print-multi-os-directory'

[dilfridge at gentoo dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111406

--- Comment #4 from Andreas K. Huettel <dilfridge at gentoo dot org> ---
(In reply to Richard Biener from comment #3)
> 
> So I think this isn't an issue unless you try to build libiberty stand-alone
> or as part of binutils and also install it?
> 

We have a binutils-libs package, which installs libbfd, libctf, libopcodes,
libsframe, and a statical libiberty.a