On Tue, Jan 5, 2010 at 9:19 PM, Romain Couturat <coutu...@esiee.fr> wrote:
> It's definitely due to mandriva's distribution (The vlc dev package > installs itself in /usr/lib) but i don't know why the behavior is kept > against src/src.pro file. > > > 2010/1/5 Romain Couturat <coutu...@esiee.fr> > > Here are the results : >> >> [rom...@localhost vlmc]$ ldd bin/vlmc >> linux-gate.so.1 => (0xffffe000) >> libvlc.so.5 => /usr/lib/libvlc.so.5 (0xb777c000) >> ... >> >> Despite of those 3 lines in src/src.pro >> >> LIBS += -L/usr/local/lib \ >> -lvlc \ >> $$[VLMC_ADDITIONAL_LIBS] >> >> I got around this (see my previous message) but it's still odd >> >> 2010/1/4 Hugo Beauzee-Luyssen <beauz...@gmail.com> >> >> On Sun, Jan 3, 2010 at 9:18 PM, Romain Couturat <coutu...@esiee.fr>wrote: >>> >>>> Why is vlmc trying to load libvlc.so.5 from /usr/lib/ and not from >>>> /usr/local/lib/ , which seems to be its default location (at least with a >>>> mandriva) ? >>>> I got vlmc to work doing >>>> ln -s /usr/local/lib/libvlc.so.5 /usr/lib/libvlc.so.5 >>>> but I wonder : why is this necessary and won't this fix cause >>>> unnecessary problems ? >>>> >>>> Keep the good work. >>>> >>>> >>>> >>> Hi, >>> >>> This is rather odd, as we explicitly specify /usr/local/lib in the .pro >>> file... >>> Moreover, when I check which shared library are to be loaded (using ldd >>> bin/vlmc) it clearly says : >>> libvlc.so.5 => /usr/local/lib/libvlc.so.5 >>> >>> Could you try to run "ldd bin/vlmc" yourself, and post back your result ? >>> >>> Regards, >>> >>> >>> I think I forgot the first question... do you use the git version of vlc ? If not, you should (well... must actually) -- Hugo Beauzée-Luyssen
_______________________________________________ vlmc-devel mailing list vlmc-devel@vlmc.org http://vlmc.org/mailman/listinfo/vlmc-devel
