Created attachment 681823 [details] build.log sys-apps/keyutils-1.6.3 fails to build with : cc1plus: error: output filename specified twice make: *** [Makefile:175: cxx.stamp] Error 1 make: *** Waiting for unfinished jobs.... PS:sorry for not provide cleaner logs for the other bugs. hope it is ok the i am running my own GCC-11?
In 1.6.3 failure starts from commit (works if reverted): https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/commit/?id=991c272062a4300bbd5fe22dce17ab2fb5126e3f keyutils-1.6.1 builds fine with gcc-11.0.9999-d54be5a (In reply to andy from comment #0) > PS:sorry for not provide cleaner logs for the other bugs. It's fine, may want to include emerge --info for completeness too. Also, bugzilla can be annoying with mime types so using a ".txt" extension will prevent build.log being auto-recognized as x-log, not that I mind fixing it. > hope it is ok the i am running my own GCC-11? Gentoo does carry a patchset for gcc-11 that you'd be missing, some issues may or may not be reproducible. @toolchain may have a better answer.
I think it's a gcc driver bug. Seems to be reproducible with: ``` $ g++-10.2.0 -x c++-header -fsyntax-only /dev/null <ok> $ g++-11.0.0 -x c++-header -fsyntax-only /dev/null cc1plus: error: output filename specified twice ```
Filed upstream as https://gcc.gnu.org/PR98591
(In reply to Ionen Wolkens from comment #1) > Gentoo does carry a patchset for gcc-11 that you'd be missing, some issues > may or may not be reproducible. @toolchain may have a better answer. i am watching Sergei Trofimovich s commits at github and follow his commit to add his patchset for my ebuilds when i am updating them . the only thing i have changed is to use commits instead of live builds because i am running gcc-11 on 5 machines with distcc and like to have same version/commit on them .
Upstream fixed it as https://gcc.gnu.org/g:492b90f33dfb37576dc7ae424d67b2be8b959bf2. Please give it a try.
(In reply to Sergei Trofimovich from comment #5) > Upstream fixed it as > https://gcc.gnu.org/g:492b90f33dfb37576dc7ae424d67b2be8b959bf2. Please give > it a try. Updated my gcc11 and no issue anymore, thanks for taking these upstream as always.
(In reply to Sergei Trofimovich from comment #5) > Upstream fixed it as > https://gcc.gnu.org/g:492b90f33dfb37576dc7ae424d67b2be8b959bf2. Please give > it a try. i went with : https://github.com/gcc-mirror/gcc/commit/e2559c3945a09521ffe4f59669bc4d902ae77adb but yes it is fixed. thnks for the report.
