Helmut Auer wrote: > vdr@xxxxxxxxxxxxx schrieb: >> Hello List >> The em84xx plugin is using the libEM84xx.so library. This beast is >> only available binary and seems to be incompatible with glibc > 2.3.5 >> What can I do to get this combination working in a glibc >=2.4 >> environment ? >> Is it possible to create a static .la library bundled with these >> dependend libraries: >> >> ldd /usr/lib/libEM84xx.so >> linux-gate.so.1 => (0xffffe000) >> libpthread.so.0 => /lib/libpthread.so.0 (0xb7e03000) >> libm.so.6 => /lib/libm.so.6 (0xb7dde000) >> libc.so.6 => /lib/libc.so.6 (0xb7cbf000) >> /lib/ld-linux.so.2 (0x80000000) >> >> or are there any other possibilities >> >> > Are there no linking guru's on that list with an idea ? > I remember fixing realplayer plugin for netscape years ago, by linking it against a static version of the old libc... Anyway, as you are already building em84xx plugin, you might try linking against a static version of the correct libc by simply adding the full path to the lib as an object to the plugin linking call, e.g. change the Makefile here: libvdr-$(PLUGIN).so: $(OBJS) $(CXX) $(CXXFLAGS) -shared $(OBJS) -o $@ -lEM84xx -losd @cp $@ $(LIBDIR)/$@.$(APIVERSION) to libvdr-$(PLUGIN).so: $(OBJS) $(CXX) $(CXXFLAGS) -shared $(OBJS) -o $@ \ /path/to/correct/libc.a -lEM84xx -losd @cp $@ $(LIBDIR)/$@.$(APIVERSION) But I do not give any guarantees that this works or crashes earlier of later. Maybe vdr runs for some time but crashes later because some code initiates a call which gets routed to the old libc code. So long, -- Patrick Cernko | mailto:errror@xxxxxxxxxx | http://www.errror.org "Wer HTML postet oder gepostetes HTML quotet oder sich gepostetes oder gequotetes HTML beschafft, um es in Verkehr zu bringen, wird geplonkt." (anonym) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://www.linuxtv.org/pipermail/vdr/attachments/20070208/66f9aaa6/signature.pgp
