On 01/09/2017 11:44 PM, Carsten Haitzler (The Rasterman) wrote: > On Mon, 9 Jan 2017 23:14:30 +0000 Peter Flynn <[email protected]> said: >> [...] 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.
You seem to be treating my query as a suggestion :-) I wouldn't dream of it. For those very reasons. > 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 Finding them was fairly easy...but I didn't know if it was safe to nuke 'em or not, as I had no information about what they are or where they came from, and I didn't really want to break the entire system. For all I know, libraries starting libe* could belong to something else, not Enlightenment... On 01/10/2017 12:30 AM, Dave wrote: > In the year 2017, of the month of January, on the 9th day, Peter Flynn wrote: >> 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. > > Yep, that'd be the problem. So it was what I initially suspected; > stale libraries. As Rasterdude says, you'll need to nuke 'em. That was never in doubt; the problem was working out if it was safe to get rid of them, and deciding *how* to get rid of them. >>> $ ldd /usr/local/lib/libecore_file.so > ... > Actually, it highlights exactly your problem. To you :-) Not to me. > The above links are stale. You'll need to clear these libraries out. > They're almost certainly part of existing installed packages. They appear to be part of e17, and perhaps e19, which apparently (in their Ubuntu incarnations) install themselves from a large number of discrete packages, and lack a monolithic driver. Working backwards, I found an actual *package* called libecore-dev, and purging that orphaned a whole bunch of other suspects, so I trashed them as well. BUT that doesn't fix the problem. Having re-run ldconfig and then rebooted, I tried another compile, only for it to come up with the same error, so I am now recursively trying a build, finding yet more stuff to delete, lather, rinse, repeat... I *knew* something was wrong when I upgraded to 16.04 and found that Ubuntu had gone retroverse on Enlightenment. Under 15.* you could install e19, but under 16.* you can only install e17. The result seems to be that all the e19 files and packages have been orphaned by the installation of e17. The answer for the moment is, if you are running Ubuntu, DO NOT use update-manager to perform a system version upgrade. Instead, back up, wipe, and install a fresh system. ///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
