On Mon, 16 Aug 2010 21:18:40 +0100 Matthew Robbetts <wingfeath...@gmail.com> wrote:
> On 08/16/10 19:20, Iván Briano (Sachiel) wrote: > > On Sun, Aug 15, 2010 at 9:09 PM, Michael Blumenkrantz <m...@zentific.com> > > wrote: > >> On Mon, 16 Aug 2010 00:47:06 +0100 > >> Matthew Robbetts <wingfeath...@gmail.com> wrote: > >> > >>> On 08/16/10 00:23, Michael Blumenkrantz wrote: > >>>> On Mon, 16 Aug 2010 00:05:29 +0100 > >>>> Matthew Robbetts <wingfeath...@gmail.com> wrote: > >>>> > >>>>> On 15 Aug 2010, at 19:41, Michael Blumenkrantz wrote: > >>>>> > >>>>>> On Sun, 15 Aug 2010 19:01:59 +0100 > >>>>>> Matthew Robbetts <wingfeath...@gmail.com> wrote: > >>>>>> > >>>>>>> On 08/15/10 17:00, Michael Blumenkrantz wrote: > >>>>>>>> On Sun, 15 Aug 2010 16:50:37 +0100 > >>>>>>>> Matthew Robbetts <wingfeath...@gmail.com> wrote: > >>>>>>>> > >>>>>>>>> Hi all, > >>>>>>>>> > >>>>>>>>> As of a few days ago (I'm not sure which revision), the efl overlay > >>>>>>>>> won't complete a build. Most packages build fine, but when it gets > >>>>>>>>> to building x11-wm/enlightenment the configure stage fails at the > >>>>>>>>> point of: > >>>>>>>>> > >>>>>>>>> ... > >>>>>>>>> checking whether to install sysactions.conf... yes > >>>>>>>>> checking whether to enable Files menu item... yes > >>>>>>>>> checking which device backend to use... (cached) ehal > >>>>>>>>> checking whether to build documentation... no > >>>>>>>>> checking for E_REMOTE... no > >>>>>>>>> configure: error: in > >>>>>>>>> `/var/tmp/portage/x11-wm/enlightenment-9999/work/trunk/e': > >>>>>>>>> configure: error: The pkg-config script could not be found or is too > >>>>>>>>> old. Make sure it > >>>>>>>>> is in your PATH or set the PKG_CONFIG environment variable to the > >>>>>>>>> full path to pkg-config. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> The emerge command: > >>>>>>>>> > >>>>>>>>> # emerge $(cat /etc/portage/sets/efl) --pretend > >>>>>>>>> > >>>>>>>>> [ebuild N ] dev-libs/eina-9999 > >>>>>>>>> [ebuild N ] dev-libs/embryo-9999 > >>>>>>>>> [ebuild N ] dev-libs/eet-9999 > >>>>>>>>> [ebuild N ] media-libs/evas-9999 > >>>>>>>>> [ebuild N ] dev-libs/ecore-9999 > >>>>>>>>> [ebuild N ] app-benchmarks/expedite-9999 > >>>>>>>>> [ebuild N ] media-libs/edje-9999 > >>>>>>>>> [ebuild N ] dev-libs/e_dbus-9999 > >>>>>>>>> [ebuild N ] dev-libs/efreet-9999 > >>>>>>>>> [ebuild N ] app-text/epdf-9999 > >>>>>>>>> [ebuild N ] dev-libs/eio-9999 > >>>>>>>>> [ebuild N ] dev-libs/eeze-9999 > >>>>>>>>> [ebuild N ] net-libs/eupnp-9999 > >>>>>>>>> [ebuild N ] net-libs/libeweather-9999 > >>>>>>>>> [ebuild N ] net-libs/exchange-9999 > >>>>>>>>> [ebuild N ] media-libs/emotion-9999 > >>>>>>>>> [ebuild N ] media-libs/ethumb-9999 > >>>>>>>>> [ebuild N ] x11-wm/enlightenment-9999 USE="alsa > >>>>>>>>> ..." > >>>>>>>>> > >>>>>>>>> [ebuild N ] media-libs/elementary-9999 USE="X dbus opengl > >>>>>>>>> thumbnails weather xdg -doc -fbcon -sdl -xcb" > >>>>>>>>> [ebuild N ] enlightenment-base/e_module-tclock-9999 USE="nls" > >>>>>>>>> [ebuild N ] enlightenment-base/e_module-notification-9999 > >>>>>>>>> USE="nls" [ebuild N ] media-gfx/ephoto-9999 > >>>>>>>>> > >>>>>>>>> mostly as per the instructions on the website. This efl "set" file > >>>>>>>>> has been working for me for months, but has just stopped. Any ideas? > >>>>>>>>> > >>>>>>>>> Thanks a lot, > >>>>>>>>> Matt > >>>>>>>>> > >>>>>>>>> ------------------------------------------------------------------------------ > >>>>>>>>> This SF.net email is sponsored by > >>>>>>>>> > >>>>>>>>> Make an app they can't live without > >>>>>>>>> Enter the BlackBerry Developer Challenge > >>>>>>>>> http://p.sf.net/sfu/RIM-dev2dev > >>>>>>>>> _______________________________________________ > >>>>>>>>> enlightenment-devel mailing list > >>>>>>>>> enlightenment-devel@lists.sourceforge.net > >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >>>>>>>> This is unrelated to the efl overlay. You are missing one of the > >>>>>>>> following on your system: > >>>>>>>> ecore > >>>>>>>> ecore-ipc > >>>>>>>> eet >= 1.2.3 > >>>>>>>> eina > >>>>>>>> > >>>>>>> Well, I do have ecore-9999 eet-9999 and eina-9999 all installed. The > >>>>>>> emerge installs them successfully right before trying to install > >>>>>>> enlightenment, which fails. I'm not sure what ecore-ipc is, it doesn't > >>>>>>> seem to be in the overlay. I don't have it installed as an explicit > >>>>>>> package and, to the best of my knowledge, never have. > >>>>>>> > >>>>>>> Again, this emerge command has been working continuously for months - > >>>>>>> I rebuild about once a fortnight, so surely something must have > >>>>>>> changed? > >>>>>>> > >>>>>>> ------------------------------------------------------------------------------ > >>>>>>> This SF.net email is sponsored by > >>>>>>> > >>>>>>> Make an app they can't live without > >>>>>>> Enter the BlackBerry Developer Challenge > >>>>>>> http://p.sf.net/sfu/RIM-dev2dev > >>>>>>> _______________________________________________ > >>>>>>> enlightenment-devel mailing list > >>>>>>> enlightenment-devel@lists.sourceforge.net > >>>>>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >>>>>> I assume you're missing ecore-ipc, which you can verify by looking for > >>>>>> the .pc file in /usr/lib/pkgconfig. I would speculate that your USE > >>>>>> has changed recently since nothing in the ebuilds has. > >>>>>> > >>>>>> -- > >>>>>> Mike Blumenkrantz > >>>>>> Zentific: Our boolean values are huge. > >>>>> Thanks a lot, Michael. > >>>>> I do have an ecore-ipc.pc file in there - does this mean it's installed? > >>>>> pkg-config does seem to report its libs and whatnot correctly, but I > >>>>> don't know how to check any more deeply than that. `eix ecore-ipc' > >>>>> doesn't show it, so it doesn't seem to be a package either in portage > >>>>> or in the efl overlay - but I clearly don't know the details of efl at > >>>>> all. > >>>>> > >>>>> I've presumably done something stupid - anything else I can check? > >>>> ecore-ipc is part of ecore, and it is installed by ecore. I am not sure > >>>> how you are managing to cause the enlightenment ebuild to fail, but one > >>>> of those packages listed is not being detected by your pkg-config, which > >>>> is causing the E_REMOTE test to fail and kill your build. > >>>> > >>> pkg-config seems to report on all of them correctly, except that I have > >>> eina-0.pc rather than just eina.pc. Is that normal? The others are fine. > >> yes, eina-o is the correct .pc file. not sure why it would stop being > >> detected like that suddenly... > >> > > Not anymore, raster moved it to be eina.pc just like the rest of the EFL. > > > Hmmmm, thanks all. I've tried it again tonight, and now I have eina.pc > in there instead of eina-0.pc. However, rebuilding from the beginning > now fails much earlier - during the build of eio. It fails with: > > ... > checking for EIO... no > configure: error: Package requirements (eina-0 ecore) were not met: > No package 'eina-0' found > > > Presumably, this is just churn with all the commits taking place and I > should wait a day or two? > > Yes, that specific error is definitely from the migration to alpha status. -- Mike Blumenkrantz Zentific: Our boolean values are huge. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
