This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: where do I figure out "relocation R_X86_64_PC32" errors


vamsi krishna wrote:
Hi,

Clearly yuv2rgb.o is not in fPIC mode recompile it with -fPIC.

You can use the following test to verify if a object file is in fPIC
mode or not.

TEST for fPIC:
--------------------

You can use 'objdump -r test.o | grep "R_X86_64_32' if this command
produces some output then this has not been compiled in fPIC mode.

if its a library libtest.a just do a ar -x and find it out.

HTH
Vamsi kundeti

................................

but yuv2rgb _was_ compiled with -fPIC:


gcc -I.. -I/usr/src/redhat/BUILD/ffmpeg
-I/usr/src/redhat/BUILD/ffmpeg/libavutil -fPIC -march=k8
-pthread -g -Wdeclaration-after-statement -Wall -Wno-switch
-Wdisabled-optimization -Wpointer-arith -Wredundant-decls
-Winline -O3 -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_GNU_SOURCE -fPIC -DPIC -c -o
yuv2rgb.o yuv2rgb.c




That's the problem. It was complied with -fPIC.

sean


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]