https://sourceware.org/bugzilla/show_bug.cgi?id=25120
--- Comment #5 from Harald van Dijk <harald at gigawatt dot nl> --- (In reply to Nick Alcock from comment #4) > The C compiler shouldn't affect anything here: the linker in use is what > matters. tcc has its own built-in linker. > I'll try to get tcc working in a bit, but in the absence of that you could > try to figure out which symbol in ctf-open-bfd.c is at fault (or if it's all > of them). I'll take a look. > Surely the thing doesn't just pull in the whole .a file blindly: you'd > hardly be able to link anything when using tcc if that were true (and many > binaries would be enormous: .a files are used as intermediate stages in > building larger projects a *lot*). You're right that it is not as simple as that. tcc's linker has the same whole-archive/no-whole-archive option that binutils ld has and it looks like it does default to no-whole-archive. -- 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
