本文介绍了GCC编译动态库时的-fpic和-fPIC选项的区别，前者总是可用但可能导致代码增大，后者可能产生更小、更快的代码但有平台限制。同时，文章讨论了-static的作用，并详细阐述了-march选项，特别是-march=native如何让编译器自适应探测并优化目标架构。当遇到‘no such instruction’错误时，建议删除-march=native或使用正确的目标架构名称。
（1）fpic 和 fPIC 区别
在64位下编译动态库的时候，经常会遇到下面的错误
/usr/bin/ld: /tmp/ccQ1dkqh.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC
Use -fPIC or -fpic to generate code. Whether to use -fPIC or -fpic to generate code is target-dependent. The -fPIC choice always works, but may produce larger code than -fpic (mnenomic to remember this is that PIC is in a larger case, so it may produce larger amounts of code). Using -fpic option usually generates smaller and faster code, but will have platform-dependent limitations, such as the number of globally visible symbols or the size of the code. The linke
最低0.47元/天 解锁文章
993
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
