On Mon, 9 Jan 2017 23:14:30 +0000 Peter Flynn <[email protected]> said:
> On 01/09/2017 10:36 PM, Dave wrote: > > OK, I did a little more looking, and the functions referenced are to be > > found in the libecore.so library. So, seems like your libecore_file.so > > can't find this library. > > Thanks very much for digging into that. > > There are copies of libecore.so and libecore_file.so (and other > libecore*) in /usr/lib/i386-linux-gnu/, all version 1.8.6 whereas EFL is > trying to create 1.18.99 There's also something called libecore1 which > seems to be EFL-specific. > > So presumably at some point EFL's build is referencing the older > libecores, which either shouldn't be there, or should be disabled for > the duration. I am assuming that deleting them would be A Very Bad > Thing. How is EFL intended to build new versions and install them in > /usr/local/lib if /usr/lib/i386-linux-gnu/ is stuffed full of the > existing system-installed ones? that would create issues. you CAN have multiple libs installed in differing locations but you have to be careful. very careful. so you have an efl 1.8 install still in addition to 1.18 that you compile. when efl compiles it places EVERYTHING it builds in the same prefix (eg in /usr/local that's the default or if you use --prefix=/opt/e then everything would be in /opt/e so you can nuke your compiled install cleanly by rm -rf /opt/e as long as you placed nothing else in that same prefix) so those libs in /usr obviously come from something else that efl's build. e.g. packages. figure out which and remove them. look at al the libe*.so.1.* files in /usr/local and find similar ones elsewhere (likely versioned earlier) and find out what/who owns them... and nuke > > So, next step would be to check your /etc/ld.so.conf file (and possibly > > /etc/ld.so.conf.d/* files) to see if "/usr/local/lib" is listed as a system > > library location. > > Yep, in /etc/ld.so.conf.d/libc.conf as normal. > > > Another check would be to run the command > > "ldd /usr/local/lib/libecore_file.so". That could provide a clue as to the > > issue. > > Not a whole lot, unfortunately. > > > $ ldd /usr/local/lib/libecore_file.so > > linux-gate.so.1 => (0xb77ad000) > > libeina.so.1 => /usr/lib/i386-linux-gnu/libeina.so.1 (0xb7714000) > > libeo.so.1 => /usr/lib/i386-linux-gnu/libeo.so.1 (0xb7701000) > > libecore.so.1 => /usr/lib/i386-linux-gnu/libecore.so.1 (0xb76c9000) > > libecore_con.so.1 => /usr/lib/i386-linux-gnu/libecore_con.so.1 > > (0xb7696000) libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 > > (0xb7679000) libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb74c3000) > > libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb746e000) > > libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb7468000) > > librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb745f000) > > libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 > > (0xb7336000) libgnutls.so.30 => /usr/lib/i386-linux-gnu/libgnutls.so.30 > > (0xb71de000) libeet.so.1 => /usr/lib/i386-linux-gnu/libeet.so.1 (0xb71b9000) > > libgcrypt.so.20 => /lib/i386-linux-gnu/libgcrypt.so.20 (0xb7109000) > > /lib/ld-linux.so.2 (0x800f6000) > > libpcre.so.3 => /lib/i386-linux-gnu/libpcre.so.3 (0xb7094000) > > libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb7079000) > > libp11-kit.so.0 => /usr/lib/i386-linux-gnu/libp11-kit.so.0 > > (0xb7018000) libidn.so.11 => /usr/lib/i386-linux-gnu/libidn.so.11 > > (0xb6fe4000) libtasn1.so.6 => /usr/lib/i386-linux-gnu/libtasn1.so.6 > > (0xb6fce000) libnettle.so.6 => /usr/lib/i386-linux-gnu/libnettle.so.6 > > (0xb6f92000) libhogweed.so.4 => /usr/lib/i386-linux-gnu/libhogweed.so.4 > > (0xb6f5d000) libgmp.so.10 => /usr/lib/i386-linux-gnu/libgmp.so.10 > > (0xb6ed1000) libjpeg.so.8 => /usr/lib/i386-linux-gnu/libjpeg.so.8 > > (0xb6e72000) libgpg-error.so.0 => /lib/i386-linux-gnu/libgpg-error.so.0 > > (0xb6e5b000) libffi.so.6 => /usr/lib/i386-linux-gnu/libffi.so.6 (0xb6e52000) > > ///Peter > > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today. http://sdm.link/xeonphi > _______________________________________________ > enlightenment-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
