| View previous topic :: View next topic |
| Author |
Message |
MADcow
l33t
Joined: 23 Jan 2003
Posts: 742
Location: RIT (Henrietta, New York, United States)
|
 Posted: Fri Feb 06, 2004 1:50 am Post subject: Enlightenment-cvs dependencies compile problems |
 |
|
| Code: | root@Helix> ACCEPT_KEYWORDS="~x86" emerge enlightenment-cvs
(...)
entice.c:13:21: Epsilon.h: No such file or directory
entice.c: In function `entice_init':
entice.c:103: warning: implicit declaration of function `epsilon_init'
entice.c:125: warning: implicit declaration of function `e_container_layout_plugin_set'
entice.c: In function `_entice_thumb_load':
entice.c:272: warning: implicit declaration of function `e_container_scroll_to'
gcc -DHAVE_CONFIG_H -I. -I. -I../../src -Wall -I../lib -I/usr/X11R6/include -I/usr/include -march=athlon-mp -O3 -finline-functions -fomit-frame-pointer -pipe -fforce-addr -funroll-loops -frerun-loop-opt -frerun-cse-after-loop -falign-functions=4 -fexpensive-optimizations -falign-jumps=4 -ffast-math -mmmx -msse -fprefetch-loop-arrays -mfpmath=sse -c prefs.c
entice.c: In function `entice_file_add_job_cb':
entice.c:436: error: `Epsilon' undeclared (first use in this function)
entice.c:436: error: (Each undeclared identifier is reported only once
entice.c:436: error: for each function it appears in.)
entice.c:436: error: `e' undeclared (first use in this function)
entice.c:463: warning: implicit declaration of function `epsilon_new'
entice.c:465: warning: implicit declaration of function `epsilon_exists'
entice.c:465: error: `EPSILON_FAIL' undeclared (first use in this function)
entice.c:467: warning: implicit declaration of function `epsilon_generate'
entice.c:472: warning: implicit declaration of function `epsilon_free'
make[3]: *** [entice.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: *** Waiting for unfinished jobs....
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/var/tmp/portage/entice-0.9.0.20040201/work/entice/src/bin'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/entice-0.9.0.20040201/work/entice/src'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/var/tmp/portage/entice-0.9.0.20040201/work/entice/src'
make: *** [all-recursive] Error 1
!!! ERROR: media-gfx/entice-0.9.0.20040201 failed.
!!! Function enlightenment_src_compile, Line 71, Exitcode 2
!!! emake failed
|
| Code: |
root@Helix> ACCEPT_KEYWORDS="~x86" emerge edje
(...)
../../src/lib/.libs/libedje.so: undefined reference to `evas_object_text_font_source_set'
collect2: ld returned 1 exit status
make[3]: *** [edje_ls] Error 1
make[3]: *** Waiting for unfinished jobs....
(a couple more gcc lines)
../../src/lib/.libs/libedje.so: undefined reference to `evas_object_text_font_source_set'
collect2: ld returned 1 exit status
make[3]: *** [edje_cc] Error 1
../../src/lib/.libs/libedje.so: undefined reference to `evas_object_text_font_source_set'
collect2: ld returned 1 exit status
make[3]: *** [edje] Error 1
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/edje-0.0.1.20040201/work/edje/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/edje-0.0.1.20040201/work/edje'
make: *** [all-recursive-am] Error 2
!!! ERROR: media-libs/edje-0.0.1.20040201 failed.
!!! Function enlightenment_src_compile, Line 71, Exitcode 2
!!! emake failed
|
and elicit, of course, won't compile without entice. ewl won't compile without edje.
ARGH. is it the developers' fault (i know enlightenment-cvs is unstable)? or is it a gentoo-specific problem?
*wants e-17 to work; used it a while ago when it DID build...* |
|
| Back to top |
|
 |
Mindstab
Apprentice
Joined: 02 Jan 2003
Posts: 271
Location: Vancouver, Canada
|
| Posted: Fri Feb 06, 2004 7:51 am Post subject: |
|
|
its kind of moot
the enlightenment wm in cvs in gentoo is dead source
there currently is no enlightenment 0.17 wm.
Taht code is 8 or so months old (june of last year)
all the libraris that E will use haev been developed much further, and some of the stuff that the enlightenment in cvs depends on have been dropped.
Its buggy and not being fixed because it will be rewritten soemtime.
might just want to abandon it aswell and wait the long wait  |
|
| Back to top |
|
|
MADcow
l33t
Joined: 23 Jan 2003
Posts: 742
Location: RIT (Henrietta, New York, United States)
|
| Posted: Fri Feb 06, 2004 4:08 pm Post subject: |
|
|
oh. ok.
i have been waiting a long time though
it's just that the website was updated some, and they said that they got a bunch of new developers, so i was thinking that maybe it had been updated...
any clue why we haven't had a DR16 release in a few months, either? KWo fixed a whole bunch of bugs, but then the releases just sorta stopped :-\
oh well. i've been using 16 for this long. why not another 2 years... |
|
| Back to top |
|
|
tomthewombat
Apprentice
Joined: 29 Mar 2003
Posts: 244
Location: NY State
|
| Posted: Sat Feb 07, 2004 1:18 am Post subject: |
|
|
I don't think years is a good scale. From what I understand they are yanking most of the core code from the Window Manager (well the code not specific to window managing) and further adding to their libraries. This means that the WM should be fairly easy to code. I read a post from the first few weeks of January that said they had some working e17 WM code but not something CVS commitable.
Anyway, its worth the wait. |
|
| Back to top |
|
|
|
Desktop Environments
