>Isn't PIC used for a reason in shared libs? :) Sure it is, but that reason doesn't really apply here. The reason we compile shared libraries as PIC is so that many applications can map the same object at different addresses and have only one copy of the code in memory. PIC code is slightly bigger, and slightly slower, but it's worth it because you avoid the need to have duplicated code all over the place at run time. If the ext2 shared library is only used by mke2fs and e2fsck, you will only derive any advantage from having it PIC if you are running both mke2fs and e2fsck simultaneously, or more than one copy of either program. This doesn't seem all that likely during installation, and anyway the library is small enough that having two copies of it in memory is not going to kill us. p.
Attachment:
pgpWGEWTVnkFY.pgp
Description: PGP signature