I read recently that someone was not able to link statically to a
library which was placed alongside a shared library. Having gained some
knowhow from the good people on this list I checked first the ld manpage
and found this:
ld will search a directory for a library with an extension of .so before
searching for one with an extension of .a.
Does anyone know of a way to subvert this behaviour and force linking to
the static library?
Also, why is this behaviour made this way? Is there a reason or is it
arbitrary?
Thanks as ever, for all your help.
Shriramana Sharma.
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
