On 12/04/13 12:01, Dustin N. Jenkins wrote: > > On 12/04/2013 09:08 AM, Kevin Martin wrote: >>> On 12/03/2013 05:19 PM, Kevin Martin wrote: >>>> elm_win.c: In function '_elm_win_client_message': >>>> elm_win.c:2082:23: error: 'ECORE_X_ATOM_E_ILLUME_ACCESS_ACTION_UP' >>>> undeclared (first use in this function) >>>> ECORE_X_ATOM_E_ILLUME_ACCESS_ACTION_UP) >>>> ^ >>>> elm_win.c:2082:23: note: each undeclared identifier is reported only once >>>> for each function it appears in >>>> elm_win.c:2088:23: error: 'ECORE_X_ATOM_E_ILLUME_ACCESS_ACTION_DOWN' >>>> undeclared (first use in this function) >>>> ECORE_X_ATOM_E_ILLUME_ACCESS_ACTION_DOWN) >>>> ^ >>>> make[2]: *** [libelementary_la-elm_win.lo] Error 1 >>>> make[2]: Leaving directory `/work/e18/elementary/src/lib' >>>> make[1]: *** [install-recursive] Error 1 >>>> make[1]: Leaving directory `/work/e18/elementary/src' >>>> make: *** [install-recursive] Error 1 >>>> >>>> >>>> I didn't see anything in the git commit notes about this being fixed so >>>> thought I'd see what may need to be done to get this corrected. >>>> >>>> Thanks. >>>> >>>> Kevin >>>> >> On 12/03/13 19:23, Dustin Jenkins wrote:> >> >> Did you delete your old installation? >>> Run ldconfig after building efl? >>> >>> Dustin >>> >>> >> The old install is Fedora rpms not installed in /usr/local...do I need to >> remove those and, if so, why? >> >> The install being built from source is going to /usr/local and appears to be >> doing the ldconfig if my log file is any indication: >> >> (cd efl ; ./autogen.sh --disable-pulseaudio; sudo make install) >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/ecore_evas/engines/extn/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/ecore_evas/engines/x/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/ecore_imf/modules/xim/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/ecore/system/upower/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/eeze/modules/sensor/fake/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/eeze/modules/sensor/udev/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/edje/modules/emotion/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/emotion/modules/gstreamer/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/evas/modules/engines/gl_x11/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/evas/modules/engines/software_x11/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/ethumb/modules/emotion/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/evas/modules/loaders/gif/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/evas/modules/loaders/tiff/linux-gnu-x86_64-1.8.1 >> libtool: finish: PATH="/sbin:/bin:/usr/sbin:/usr/bin:/sbin" ldconfig -n >> /usr/local/lib/evas/modules/savers/tiff/linux-gnu-x86_64-1.8.1 >> >> Thanks. >> >> Kevin >> >> > Hi Kevin, > > Do you have /usr/local/lib setup in your /etc/ld.so.conf.d? > > edit/create /etc/ld.so.conf.d/99local.conf > Which only has the /usr/local/lib in it. Or check for an existing one, > as this may not be the problem. > > Then ldconfig would try to look in there, hopefully. Otherwise, it may > try to look at the RPM installed version first, depending on where in > the path it sees it. I've had many cases where I can't figure out where > pkg-config is looking, but simply giving it no other option then where I > want it to look fixed it. > > The Enlightenment developers have been pretty adamant about cleaning out > the old installation first, and this may be why. I admit, when it comes > to library linking, there seems to be some black magic. :) > > Good luck, > Dustin > >
> Ok, so I setup the ld.so.conf.d file that you mentioned, reran ldconfig, removed my old enlightenment install, make distclean, rerun autogen.sh, and make install and nothing has changed. I'm still getting the same error in the same place. Kevin ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
