Hi Gerald,
Gerald Dachs wrote:
If you would take a deeper look into your post you would have noticed
that the mentioned file bitbuffer.o is not
build to this time. It must have been build in a former stage. So there
is still no proof that it
has been build with -fPIC.
You are correct. It
Richard Scobie r.sco...@clear.net.nz wrote:
Hi Gerald,
Gerald Dachs wrote:
If you would take a deeper look into your post you would have noticed
that the mentioned file bitbuffer.o is not
build to this time. It must have been build in a former stage. So there
is still no proof that
Hi Olover,
Oliver Endriss wrote:
The attached patch should fix this problem.
Many thanks, that has fixed it.
And bonus points for decoding the mangled grammer in my previous post...
Regards,
Richard
___
vdr mailing list
vdr@linuxtv.org
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
`/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice/libhdffcmd'
gcc -O3 -Wall -fPIC -shared -o
Hi Klaus,
Klaus Schmidinger wrote:
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
machine:
---
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
`/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice/libhdffcmd'
gcc -O3 -Wall -fPIC -shared -o libhdffcmd-0.1.0.so bitbuffer.o
hdffcmd_av.o
Am 19.11.2012 05:27, schrieb Richard Scobie:
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
`/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice/libhdffcmd'
gcc -O3 -Wall -fPIC -shared -o
