On Fri, 28 Aug 2009, Alex Riesen wrote: > Nicolas Pitre, Fri, Aug 28, 2009 21:27:53 +0200: > > On Fri, 28 Aug 2009, Alex Riesen wrote: > > > And shouldn't a linker complain regarding duplicated symbols, unless > > > the other (library) symbol is defined as a weak symbol, allowing > > > overriding it with another symbol of stronger linkage? > > > > Normally a linker would search for new objects to link only when there > > are still symbols to resolve. If the library is well architected (mind > > you I don't know if that is the case on Windows or OS X) you should find > > many small object files in a library, so to have only related functions > > together in a single object for only the needed code to be linked in the > > final binary. Hence the printf symbol should be in a separate object > > file than gettimeofday, etc. > > > > Only if the library's object file containing gettimeofday also contains > > another symbol pulled by the linker will you see a duplicated symbol > > error. But this is still a possibility. So your proposal is probably > > cleaner. > > Is it so for dynamic linking as well? Like in libc.so? Yes. The linker still links against stubs in that case. Nicolas -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html