Now a week out of date on GCC trunk builds. We're hitting "multiple definition of `__x86.get_pc_thunk.bx'" during the xgcc build of libgcc_s.so -- and I have no idea how to fix it. Our build scripts have worked OK for years with minimal tweaks, looking for @gnutools help!-mg
GCC trunk build is broken, and has been since 7th January. Investigating. godbolt.org/admin/logs/gcc has logs.
Any binutils folks able to shed light, seems to be libdecnumber.a failing with "ar: no operation specified"
Anyone able to help:
`curl godbolt.org/admin/logs/gcc | less` will get the current failure
Build scripts at: github.com/compiler-explorer… (which is built inside docker).
to repro locally:
$ $ docker run --rm -it compilerexplorer/gcc-builder ./build.sh trunk
thanks in advance!! --mg
As per the docker, we build on Ubuntu 18.04, which ought to be "ok", but I've been meaning to update that soon. I doubt that's the problem, but *shrug* -mg
And indeed, now I tried running again build fails with `multiple definition of `__x86.get_pc_thunk.bx`` in libgcc_s so I suspect something afood in the bintuils build? CC @gnutools in case there's some thread I can follow? Thanks in advance! -mg
logfile updated;
$ curl godbolt.org/admin/logs/gcc | less
if you are able to help point me at what might be going on? Quite possibly could be "gcc build is broken" but I don't know, as it seemed like binutils was broken earlier. All in all, been broken since 7th, which is sad -mg