| 1 |
On 15/03/11 22:54, Ian Lee wrote: |
| 2 |
> On 15/03/11 19:15, Mick wrote: |
| 3 |
>> I'm trying to emerge the latest dev-libs/efreet-9999, but it fails as shown |
| 4 |
>> below: |
| 5 |
>> |
| 6 |
>> ========================================= |
| 7 |
>>>>> Emerging (1 of 2) dev-libs/efreet-9999 from enlightenment |
| 8 |
|
| 9 |
[snip] |
| 10 |
|
| 11 |
>> efreet_desktop.c: In function 'efreet_desktop_changes_cb': |
| 12 |
>> efreet_desktop.c:1207: error: 'ECORE_FILE_EVENT_CLOSED' undeclared (first use |
| 13 |
>> in this function) |
| 14 |
>> efreet_desktop.c:1207: error: (Each undeclared identifier is reported only |
| 15 |
>> once |
| 16 |
>> efreet_desktop.c:1207: error: for each function it appears in.) |
| 17 |
>> make[3]: *** [libefreet_la-efreet_desktop.lo] Error 1 |
| 18 |
>> make[3]: *** Waiting for unfinished jobs.... |
| 19 |
>> efreet_icon.c: In function 'efreet_icon_changes_cb': |
| 20 |
>> efreet_icon.c:967: error: 'ECORE_FILE_EVENT_CLOSED' undeclared (first use in |
| 21 |
>> this function) |
| 22 |
>> efreet_icon.c:967: error: (Each undeclared identifier is reported only once |
| 23 |
>> efreet_icon.c:967: error: for each function it appears in.) |
| 24 |
>> make[3]: *** [libefreet_la-efreet_icon.lo] Error 1 |
| 25 |
>> efreet.c: In function 'efreet_fsetowner': |
| 26 |
>> efreet.c:323: warning: ignoring return value of 'fchown', declared with |
| 27 |
>> attribute warn_unused_result |
| 28 |
>> make[3]: Leaving directory `/var/tmp/portage/dev- |
| 29 |
>> libs/efreet-9999/work/efreet/src/lib' |
| 30 |
>> make[2]: *** [all-recursive] Error 1 |
| 31 |
>> make[2]: Leaving directory `/var/tmp/portage/dev- |
| 32 |
>> libs/efreet-9999/work/efreet/src' |
| 33 |
>> make[1]: *** [all-recursive] Error 1 |
| 34 |
>> make[1]: Leaving directory `/var/tmp/portage/dev-libs/efreet-9999/work/efreet' |
| 35 |
>> make: *** [all] Error 2 |
| 36 |
>> emake failed |
| 37 |
>> * ERROR: dev-libs/efreet-9999 failed (compile phase): |
| 38 |
>> * (no error message) |
| 39 |
>> * |
| 40 |
>> * Call stack: |
| 41 |
>> * ebuild.sh, line 56: Called src_compile |
| 42 |
>> * environment, line 2998: Called enlightenment_src_compile |
| 43 |
>> * environment, line 1626: Called die |
| 44 |
>> * The specific snippet of code: |
| 45 |
>> * emake || die; |
| 46 |
>> * |
| 47 |
>> * If you need support, post the output of 'emerge --info =dev- |
| 48 |
>> libs/efreet-9999', |
| 49 |
>> * the complete build log and the output of 'emerge -pqv =dev- |
| 50 |
>> libs/efreet-9999'. |
| 51 |
>> * This ebuild is from an overlay named 'enlightenment': |
| 52 |
>> '/var/lib/layman/enlightenment/' |
| 53 |
>> * The complete build log is located at '/var/log/portage/dev- |
| 54 |
>> libs:efreet-9999:20110315-190856.log'. |
| 55 |
>> * The ebuild environment file is located at '/var/tmp/portage/dev- |
| 56 |
>> libs/efreet-9999/temp/environment'. |
| 57 |
>> * S: '/var/tmp/portage/dev-libs/efreet-9999/work/efreet' |
| 58 |
>> ========================================= |
| 59 |
>> |
| 60 |
>> Any ideas? |
| 61 |
> Update Ecore. |
| 62 |
|
| 63 |
Further to that, efl-9999 is not stable and changes to the code are not |
| 64 |
reflected in version number bumps. It's all in svn so who knows what |
| 65 |
you'll get on any given day. From long bitter hard experience: |
| 66 |
|
| 67 |
Just write a little script that rebuilds ALL of efl anytime you want to |
| 68 |
rebuild any part of it. Do not be tempted to short cut this process, too |
| 69 |
often it ends in tears. Just bite the bullet and let it run. |
| 70 |
|
| 71 |
Creating a portage set with all efl & e17 ebuilds in it also works. Then |
| 72 |
you can "emerge @e17" and get the same result as a wrapper script. |
| 73 |
|
| 74 |
-- |
| 75 |
alan dot mckinnon at gmail dot com |
Archives