https://sourceware.org/bugzilla/show_bug.cgi?id=23460
--- Comment #14 from Evangelos Foutras <evangelos at foutrelis dot com> --- (In reply to Nick Clifton from comment #11) > I just do not like the idea of not tidying up after ourselves. Mind you it > is only linker plugins that call dlclose. Plugins for other tools (eg ar, > nm, etc) do not bother with the call. Plus the linker only calls dlclose > when it is closing *all* plugins as part of its exit sequence. So I am not > sure if there really is a problem (for the binutils) here. (To reproduce the following on Fedora Rawhide, rebuild binutils with the patch from comment #7 and pass "--plugin /usr/lib64/LLVMgold.so" to ar/nm. The examples below are without the --plugin option, because LLVMgold.so is symlinked from /usr/lib/bfd-plugins on Arch.) The main issue seems to be with ar and nm: $ touch a.c b.c $ gcc -c a.c b.c $ ar r ab.a a.o b.o ar: creating ab.a : CommandLine Error: Option 'asm-instrumentation' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options $ nm a.o b.o a.o: : CommandLine Error: Option 'asm-instrumentation' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options I believe the above error is caused by a sequence of "dlopen -> dlclose -> dlopen" on LLVMgold.so. (liblto_plugin.so doesn't seem to mind being unloaded and loaded again.) Is the repeated dlopen expected here? -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils