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

2023-09-15 Thread dilfridge at gentoo dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111406 --- Comment #4 from Andreas K. Huettel --- (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

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

2023-09-14 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111406 --- Comment #3 from Richard Biener --- 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

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

2023-09-13 Thread dilfridge at gentoo dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111406 --- Comment #2 from Andreas K. Huettel --- 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'

2023-09-13 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111406 --- Comment #1 from Andrew Pinski --- >This stems from libiberty/Makefile.am: You mean Makefile.in, libiberty does not use automake.