On 19.11.2012 05:27, Richard Scobie wrote:
I have just upgraded from vdr-1.7.31 to vdr-1.7.32 with S2-6400 and on making 
plugins, I receive the following error:

make[2]: Entering directory 
gcc -O3 -Wall  -fPIC -shared -o libhdffcmd-0.1.0.so bitbuffer.o hdffcmd_av.o 
hdffcmd_base.o hdffcmd_generic.o hdffcmd_hdmi.o hdffcmd_mux.o hdffcmd_osd.o 
/usr/bin/ld: bitbuffer.o: relocation R_X86_64_PC32 against undefined symbol 
`memset@@GLIBC_2.2.5' can not be used when making a shared object; recompile 
with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
make[2]: *** [libhdffcmd-0.1.0.so] Error 1

As "-fPIC" is being used, I am not sure how to handle the comment, "recompile with 

Maybe this was caused by the change I introduced in order to be able to
easily build a 32-bit version of VDR (and all its plugins) on a 64-bit

--- PLUGINS/src/dvbhddevice/libhdffcmd/Makefile 2012/01/18 12:25:20     1.2
+++ PLUGINS/src/dvbhddevice/libhdffcmd/Makefile 2012/10/09 09:54:26     1.3
@@ -24,6 +24,18 @@
 AR      ?= ar

+### The directory environment:
+VDRDIR ?= ../../../..
+### Make sure that necessary options are included:
+include $(VDRDIR)/Make.global
+### Allow user defined options to overwrite defaults:
+-include $(VDRDIR)/Make.config
 ### Implicit rules:

 %.o: %.c

However, I got no such error message here, and I do use a TT S2-6400.
Maybe check your Make.global and/or Make.config files.


vdr mailing list

Reply via email to