Hi everyone,
Without really paying attention, I recently upgraded the libbullet
libraries on my debian testing system (libbulletsoftbody,
libbulletcollision, etc) from 2.81 to 2.82, breaking efl's dependency on
those libs. It appears the libbullet library files have a hard coded
version number in
I'm here again...
now I have another trouble.
at the end of compiling I have this:
/bin/grep: /usr/lib/libuuid.la: No such file or directory
/bin/sed: can't read /usr/lib/libuuid.la: No such file or directory
libtool: link: `/usr/lib/libuuid.la' is not a valid libtool archive
It's clear it want
On Wed, 16 Apr 2014 23:21:00 +0200 Gabriele Piccini dafras...@gmail.com said:
I'm here again...
now I have another trouble.
at the end of compiling I have this:
/bin/grep: /usr/lib/libuuid.la: No such file or directory
/bin/sed: can't read /usr/lib/libuuid.la: No such file or directory
On Wed, 16 Apr 2014 13:51:51 -0400 Will Hopper wjhopper...@gmail.com said:
Hi everyone,
Without really paying attention, I recently upgraded the libbullet
libraries on my debian testing system (libbulletsoftbody,
libbulletcollision, etc) from 2.81 to 2.82, breaking efl's dependency on
Or you could make a link in /usr/lib that points to it.
I had a similar problem with Slackware, but it was pkgconfig that couldn't
find anything. I had to update my PKG_CONFIG_LIBDIR and PKG_CONFIG_PATH to
include /usr/local/lib64/pkgconfig and /usr/lib64/pkgconfig. I have no
idea why Slackware
On Wed, 16 Apr 2014 20:06:37 -0700 Jeff Grimshaw jeffrey.w.grims...@gmail.com
said:
i ended up on ubuntu editing the offending .la files - but since i moved to
arch i've never had that problem again. :)
Or you could make a link in /usr/lib that points to it.
I had a similar problem with
