On Sun, 4 Dec 2011 22:52:59 -0500 mh <mhe...@member.fsf.org> wrote: > > > > > On Sun, 4 Dec 2011 20:20:52 -0500 mh <mhe...@member.fsf.org> wrote: > > > >>> On Sat, 2011-12-03 at 10:56 -0500, mh wrote: > >>>> Any other Debian (sid) users having problems building the latest > >>>> Elementary? I'm getting getting the following error: > >>>> > >>>> /bin/sed: can't read /usr/lib/libglib-2.0.la: No such file or > >>>> directory libtool: link: `/usr/lib/libglib-2.0.la' is not a valid > >>>> libtool archive make[3]: *** [elementary_testql.la] Error 1 > >>>> > >>>> I've tried reinstalling libglib-2.0-0 and libglib2.0-dev without > >>>> success. I understand that Debian has been removing .la files, > >>>> but I've been able to build elementary in the past, and it is > >>>> currently installed (though not at the latest revision). > >>> > >>> On Dec 3, 2011, at 4:59 PM, Ross Vandegrift wrote: > >>> A while ago, Debian shuffled some files around for multiarch. You > >>> have EFL components installed which were built against those older > >>> locations. > >>> > >>> To fix it, you'll need to rebuild all of the EFL components which > >>> are dependencies of elementary and link with libglib. Look > >>> especially for components that you may have built once a while > >>> back to play with and don't keep up to date. You can track down > >>> the components by looking through your $PREFIX/lib/pkgconfig for > >>> '/usr/lib/libglib-2.0.la'. > >>> > >> > >> This solved the problem. I just finished getting everything to > >> compile following Ross's suggestion to rebuild all of the EFL > >> components that are dependencies of elementary and link with > >> libglib. Actually, I couldn't figure out which components needed > >> to be rebuilt, so I just got rid of them all and rebuilt e. > > > > On Dec 4, 2011, at 9:01 PM, David Seikel wrote: > > That is in fact the best solution always. It's all a moving target, > > some days we can't even guarantee that the current state of SVN is > > compilable. Trying to get a new X to compile with an old Y from > > EFL is likely to fail. We do try to make sure that SVN is in a > > healthy state most of the time. We do make releases, just released > > a new version of EFL last week, but we don't expect that parts of > > that release will work flawlessly with parts from a previous > > release. We do test and try to make sure than all the things we > > released last week work together as a whole. > > I started using the easy_e17 script some months ago. I try to stay > within 50 - 100 updates of the current SVN revision, and using > easy_e17.sh -u --packagelist=full makes it very easy. I may have > dropped a package along the way because I was having a problem, which > may have caused this recent problem. > > Is there a more reliable way to stay up to date? This seems fine most > of the time.
I use easy_e17.sh --install --keep --packagelist=full --clean --clean (plus a few more options that are irrelevant here). The double --clean means that it will do a distclean first. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
