On 15/03/11 22:54, Ian Lee wrote:
> On 15/03/11 19:15, Mick wrote:
>> I'm trying to emerge the latest dev-libs/efreet-9999, but it fails as shown 
>> below:
>>
>> =========================================
>>>>> Emerging (1 of 2) dev-libs/efreet-9999 from enlightenment

[snip]

>> efreet_desktop.c: In function 'efreet_desktop_changes_cb':
>> efreet_desktop.c:1207: error: 'ECORE_FILE_EVENT_CLOSED' undeclared (first 
>> use 
>> in this function)
>> efreet_desktop.c:1207: error: (Each undeclared identifier is reported only 
>> once
>> efreet_desktop.c:1207: error: for each function it appears in.)
>> make[3]: *** [libefreet_la-efreet_desktop.lo] Error 1
>> make[3]: *** Waiting for unfinished jobs....
>> efreet_icon.c: In function 'efreet_icon_changes_cb':
>> efreet_icon.c:967: error: 'ECORE_FILE_EVENT_CLOSED' undeclared (first use in 
>> this function)
>> efreet_icon.c:967: error: (Each undeclared identifier is reported only once
>> efreet_icon.c:967: error: for each function it appears in.)
>> make[3]: *** [libefreet_la-efreet_icon.lo] Error 1
>> efreet.c: In function 'efreet_fsetowner':
>> efreet.c:323: warning: ignoring return value of 'fchown', declared with 
>> attribute warn_unused_result
>> make[3]: Leaving directory `/var/tmp/portage/dev-
>> libs/efreet-9999/work/efreet/src/lib'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory `/var/tmp/portage/dev-
>> libs/efreet-9999/work/efreet/src'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory 
>> `/var/tmp/portage/dev-libs/efreet-9999/work/efreet'
>> make: *** [all] Error 2
>> emake failed
>>  * ERROR: dev-libs/efreet-9999 failed (compile phase):
>>  *   (no error message)
>>  * 
>>  * Call stack:
>>  *     ebuild.sh, line   56:  Called src_compile
>>  *   environment, line 2998:  Called enlightenment_src_compile
>>  *   environment, line 1626:  Called die
>>  * The specific snippet of code:
>>  *       emake || die;
>>  * 
>>  * If you need support, post the output of 'emerge --info =dev-
>> libs/efreet-9999',
>>  * the complete build log and the output of 'emerge -pqv =dev-
>> libs/efreet-9999'.
>>  * This ebuild is from an overlay named 'enlightenment': 
>> '/var/lib/layman/enlightenment/'
>>  * The complete build log is located at '/var/log/portage/dev-
>> libs:efreet-9999:20110315-190856.log'.
>>  * The ebuild environment file is located at '/var/tmp/portage/dev-
>> libs/efreet-9999/temp/environment'.
>>  * S: '/var/tmp/portage/dev-libs/efreet-9999/work/efreet'
>> =========================================
>>
>> Any ideas?
>  Update Ecore.

Further to that, efl-9999 is not stable and changes to the code are not
reflected in version number bumps. It's all in svn so who knows what
you'll get on any given day. From long bitter hard experience:

Just write a little script that rebuilds ALL of efl anytime you want to
rebuild any part of it. Do not be tempted to short cut this process, too
often it ends in tears. Just bite the bullet and let it run.

Creating a portage set with all efl & e17 ebuilds in it also works. Then
you can "emerge @e17" and get the same result as a wrapper script.

-- 
alan dot mckinnon at gmail dot com


Reply via email to