Question

I m trying to create a shared object using a number of .O files created with the -fPIC command. When I run g++ with the -shared argument it appears to be trying to statically link to the libstdc++.a library, which of course fails. I m trying to figure out why it s automatically trying to link statically when I m not using the -static-stdc++ argument.

when I try creating the shared object I get the error ...libstdc++.a(ios) relocate R_x86_64_325 against vtable for std::ios_base : cannot be used when making a shared object

I ran G++ with the -V argument and received and can see LD receives the argument -lstdc++.

Answer 1

在把单一共有物体连接起来时,你需要从现有的卷宗中这样做。你无法从现有的档案中做到这一点;这将把这些档案与你档案联系起来,但不会把into你档案。 So gcc寻求并找到一份档案(a),并试图将其链接起来。但是,由于没有为搬迁(无——fPIC)进行汇编,因此无法使用这些汇编来编制档案。

Your options are:

dynamically link your .so to the libstdc++ (and thus make it depending on the .so file that is installed in the system)
build .o files for libstdc++ and compile them with -fPIC then compile from those your .so file (here it does not matter if you use the .o files directly or an ar archive)

For the first (that I would recommend) option the following will suffice (it is from a makefile that I use for creating malloc/free intercepting .so files)

gcc -shared -lstdc++ -o your.so yourfiles.o

Answer 2

我不得不首先在图书馆搜索道路上找到静态图书馆,或者在奥尼特找到静态图书馆。确保共同版本的适当版本得到安装并找到。页: 1 您的“g++”可以绕开开放图书馆的顺序。

友情链接