Il 05/09/2013 21:24, Richard Henderson ha scritto: > On 09/05/2013 03:20 AM, Fam Zheng wrote: >> 1) %.o in $(common-obj-m) is compiled to %.o, with >> "QEMU_CFLAGS += -shared -fPIC". Then "linked" to %.mo, which is an >> incremental object with "ln -r". This step is for consistency with >> %.mod case and has no effect. > > As a general rule, you should avoid ld -r unless you know exactly > what that implies for the given machine. This is the sort of thing > that's highly likely to work on x86 while failing elsewhere. > > E.g. ARM and PPC ld would like to add trampolines for direct calls > to reach the PLT entry. If you create one object that's too large > then that's no longer possible. > > E.g. MIPS and Alpha ld require that any one input object file > reference less than 64K worth of got entries. Every separate > object file can address its own 64K segment of the got. If you > combine too many objectsyou could overflow the got subsegments. > > If our modules are small enough, we may never see any of these, but... > > If you really require a single input file to ld for pattern matching > purposes, I highly recommend an ar file, and then use --whole-archive > to force the entire contents of the .a to be included. This preserves > the original translation-unit boundaries for ld.
Yes, this is the reason why I suggested using libtool for this. It increases the cost of compilation by essentially doing it twice, on the other hand you can simply use .la convenience libraries and libtool will be able to link it transparently into either an executable or a shared library. Libtool used to be really bad, but most performance problems have been solved. Paolo
