Re: [Valgrind-developers] vgdb does not link on (macbook, Darwin 9.8.0 i386)

[John R. <jr...@bi...>]

>> gcc  -arch 
>> i386 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length 
>>  -fno-strict-aliasing -mmacosx-version-min=10.5 -fno-stack-protector -fno-pic -fno-PIC -Wno-long-long  -Wno-pointer-sign -fno-stack-protector 
>>   -arch 
>> i386 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length 
>>  -fno-strict-aliasing -mmacosx-version-min=10.5 -fno-stack-protector -fno-pic -fno-PIC -lpthread  -o vgdb vgdb-vgdb.o
>> ld: absolute addressing (perhaps -mdynamic-no-pic) used in _vmalloc from vgdb-vgdb.o not allowed in slidable image. Use 
>> '-read_only_relocs suppress' to enable text relocs
>> collect2: ld returned 1 exit status

The conflict between "gcc ... -fno-pic -fno-PIC" and the message
"ld: absolute addressing... not allowed..." suggests a mixup in flags to ld.

What were the actual flags to ld?  Run with "gcc -v", then re-run the last part with
"collect2 -v" to see.  (It is a bug that "gcc -v" does not forward the -v to collect2.)
Or, run the whole thing under "strace -f -e execve gcc ...".

--