https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220103
--- Comment #20 from Dimitry Andric <d...@freebsd.org> --- (In reply to Jan Beich from comment #9) > (In reply to Antoine Brodin from comment #8) > Probably. I can reproduce mplayer issue with LLD 7.0 but not 6.0[1] nor > 5.0[2]. Being runtime issue it's not clear how many ports are affected. > > [1] LDFLAGS+=-fuse-ld=lld60 + BUILD_DEPENDS+=ld.lld60:devel/llvm60 > [2] LDFLAGS+=-fuse-ld=/usr/local/llvm50/bin/ld.lld + > BUILD_DEPENDS+=lld50:devel/llvm50 Hm, this is still strange to me. I think we need to investigate some more if this is really not something that has changed due to another revision in lld. E.g. https://bugs.llvm.org/show_bug.cgi?id=40176 is talking about this specific use case: FOO { foo*; }; BAR { *; }; causing symbols starting with "foo" to end up in the BAR namespace with lld. As far as I know, this has always been the case. But with all the chromium based ports, I am not so sure. Does anybody know what kind of linker script(s) are used in those? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. _______________________________________________ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
