/srv/irclogs.ubuntu.com/2021/03/20/#ubuntu-devel.txt

=== techalchemy_ is now known as techalchemy
RikMillsdoko: do you have an idea what might need to be done to resolve this? https://paste.ubuntu.com/p/S7Q5y3sYb5/11:12
dokoRikMills: the llvm-12 build on riscv64 just finished 2h ago. maybe just retry?11:14
RikMillsdoko: that is the 1st thing I checked in the build log. it used that llvm build :/11:16
RikMillsIn fact that is why I did that build. to test if the new llvm-12 solved the issue11:18
dokowe were using gcc-11 on riscv64 to build llvm-12. we could revert that now. the needed patch is backported to gcc-1011:18
RikMillsshal I report a bug?11:19
RikMills*shall11:19
dokoI don't understand why libstdc++6 doesn't satisfy that symbol ...11:20
dokoLocutusOfBorg: ^^^11:20
ricotzhi :), could you retry the autopkgtest for vala here? https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#vala11:21
RikMillsdoko: only ref I found online was https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg255111.html11:21
RikMillsbut I am slightly out on my depth on that, so not sure if relevant11:22
dokothese baslines only affect libstdc++ tests11:23
ricotzah sorry, it was retried already :)11:23
dokoRikMills: libllvm12_12.0.0~++rc3-3_riscv64.deb has the correct versioned dep: libstdc++6 (>= 11). odd11:28
RikMillsdoko: if it is relevant, I had a successful build about 24hrs before my 1st fail, and only significant difference I can see in the gcc/llvm stack on that one was libstdc++6:riscv64 (11-20210313-0ubuntu1) used on the successful build vs libstdc++6:riscv64 (11-20210317-0ubuntu1)11:29
RikMillson the fail11:29
RikMillshttps://paste.ubuntu.com/p/5WV9MW8Z4Q/11:31
RikMills^ diff of the deps installed for the build11:31
dokoRikMills: indeed, _ZNSt9once_flag11_M_activateEv is dropped in -1711:39
dokoRikMills: ahh, I remember, that's PR 99341. libstdc++: Remove symbols for new std::call_once implementation. so the action to wait for today's gcc-11 build, then rebuild llvm-toolchain-12. I don't want to back-out that patch11:45
dokoso will take a few days with these multi-day build times11:46
RikMillsdoko: and the new llvm-12 build build with -13 on riscv64 as far as I can see. probably because -17 was taking huge time to finish11:46
RikMillsdoko: that is great, and makes sense. thank you :)11:47
dokoI'll upload a doxygen build with 11 to fix the doxygen issue for now11:48
RikMillsthanks!11:49
=== sem2peie- is now known as sem2peie
LocutusOfBorgdoko, I plan a new llvm-toolchain-12 upload in Debian15:09
LocutusOfBorgso I'll just wait for gcc-11/riscv64 to finish and then sync?15:09
dokoLocutusOfBorg: please revert back to b-d gcc-10 (>= 10.2.1-21)15:21
LocutusOfBorgdoko, for debian too?16:14
LocutusOfBorgits in sid now...16:14
LocutusOfBorgyou mean drop this line     g++-11 [riscv64],16:15
dokoLocutusOfBorg: does it matter? unstable doesn't have gcc-11 either16:15
LocutusOfBorgyes so just drop that line?16:15
dokosur16:15
dokowell, and don't use 11 in the rules16:17
LocutusOfBorgyes I reverted that already16:25
LocutusOfBorgthanks16:25
LocutusOfBorguploaded in sid, will sync later, we don't need to wait for gcc-11 anymore I guess16:29
=== halvors1 is now known as halvors

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!