View previous topic :: View next topic |
Author |
Message |
Pithlit l33t
Joined: 27 Dec 2003 Posts: 887 Location: fuhen
|
Posted: Mon Mar 20, 2006 11:19 pm Post subject: |
|
|
Evas dies: Code: | EVAS_ENGINE_BUFFER_DEPTH_RGB32 | (It went out of the terminal buffer so I really don't know the details, but it died on that).
*edit*Nevermind... if anyone gets hit by this it's been fixed already. _________________ If someone solves a problem for you say thanks... and put [SOLVED] in the title! |
|
Back to top |
|
|
Pithlit l33t
Joined: 27 Dec 2003 Posts: 887 Location: fuhen
|
Posted: Tue Mar 21, 2006 2:07 am Post subject: |
|
|
s0rtd wrote: | After dealing with the evas problem, i am now onto the engage problem
After trying to emerge engage from sourceforge i get this during the compile:
Code: |
config.c:(.text+0x67f): undefined refernece to 'ewl_menu_item_text_set'
config.c:(.text+0x6e8): undefined refernece to 'ewl_menu_item_text_set'
config.c:(.text+0x72a): undefined refernece to 'ewl_menu_item_text_set'
config.c:(.text+0x78b): undefined refernece to 'ewl_menu_item_text_set'
collect2: ld returned 1 exit status
make[3]: *** [engage] Error 1
make[3]: Leaving directory '/var/tmp/portage/engage-9999/work/misc/engage/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/var/tmp/portage/engage-9999/work/misc/engage/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/var/tmp/portage/engage-9999/work/misc/engage/src'
make: *** [all] Error 2
*This is a LIVE CVS ebuild.
*That means there are NO promises it will work
*If it fails to build, FIX THE CODE YOURSELF
*before reporting any issues
!!! ERROR: x11-misc/engage-9999 failed.
!!! Function enlightenment_die, Line 94, Exitcode 0 |
This error seems very similar to the previous, I have tried emerging ewl again before engage - thinking maybe ewl has been updated, but that didnt help.
edit: I just tried this on the tux mirror as well, same failure!
before I emerged it i tried rm -rf both ewl and engage from the /usr/portage/distfiles/cvs-src
and I emerged ewl first then engage - engage still fails.
please help, again
Jurgen |
Enyone have a solution for me? _________________ If someone solves a problem for you say thanks... and put [SOLVED] in the title! |
|
Back to top |
|
|
discomfitor l33t
Joined: 21 Feb 2003 Posts: 927 Location: None
|
Posted: Wed Mar 22, 2006 12:47 am Post subject: |
|
|
Fun new bugs!
After updating last week I now have two of every module loaded, and when I try to unload them I get a segfault.
The next one (which is, in my opinion, the better of the two) is a result of using glibc 2.4 and causes e to crash any time I attempt to add a new background image to the list.
EDIT: Oh yeah, and none of the old themes work. _________________ There is no substitute for experience.
Imperfection indicates a lack of effort. |
|
Back to top |
|
|
Pithlit l33t
Joined: 27 Dec 2003 Posts: 887 Location: fuhen
|
Posted: Wed Mar 22, 2006 1:37 am Post subject: |
|
|
About the modules: Code: | rm ~/.e/e/config/default/* |
Old themes work here (blue eyed 0.5.9 at least)... not completely tho. But yeah. It's been said a number of times to expect things to break. This is exactly why I stopped developing my theme. _________________ If someone solves a problem for you say thanks... and put [SOLVED] in the title! |
|
Back to top |
|
|
matobsk n00b
Joined: 16 Oct 2005 Posts: 64
|
Posted: Wed Mar 22, 2006 5:54 am Post subject: |
|
|
Cant get evas to compile from sf.net cvs
Code: | i686-pc-linux-gnu-gcc -O2 -march=pentium4m -fomit-frame-pointer -pipe -ftracer -frename-registers -Wl,-O1 -Wl,--sort-common -Wl,-Bdirect -Wl,-hashvals -Wl,-zdynsort -o .libs/evas_buffer_test evas_buffer_test-evas_test_main.o evas_buffer_test-evas_buffer_main.o ../../src/lib/.libs/libevas.so -L/usr/lib /usr/lib/libeet.so /usr/lib/libjpeg.so /usr/lib/libfontconfig.so /usr/lib/libfreetype.so -lz /usr/lib/libexpat.so -lm
../../src/lib/.libs/libevas.so: undefined reference to `dlerror'
../../src/lib/.libs/libevas.so: undefined reference to `dlclose'
../../src/lib/.libs/libevas.so: undefined reference to `dlopen'
../../src/lib/.libs/libevas.so: undefined reference to `dlsym'
collect2: ld returned 1 exit status
make[4]: *** [evas_buffer_test] Error 1
make[4]: Leaving directory `/var/tmp/portage/evas-9999/work/e17/libs/evas/src/bin'
|
Am I the only one?
EDIT: Nevermind, clearing my ccache fixed the problem. |
|
Back to top |
|
|
thasheep n00b
Joined: 24 Nov 2005 Posts: 52 Location: Stockholm, Sweden
|
Posted: Wed Mar 22, 2006 2:13 pm Post subject: |
|
|
Does anyone else have a directory full of background pics and finds it a pain in the arse to add them one at a time to the e17 backgrounds, facing the enivitable e17 crash for each one? Well that's me anyway so I decided to write a little script to automate it. It's based on the example at http://www1.get-e.org/E17_User_Guide/English/_pages/3.8.html but I've integrated it into a bash script. Call it as `e17genbg [image1] [image2] ...` and the script will create all the background .edj files in ~/.e/e/backgrounds. The images can be in any directory and in either jpg or png format but they can't have spaces, apostrophes or probably other funny characters in the filename. Make sure you do a `chmod 755 e17genbg` first
e17genbg
Code: | #!/bin/bash
TMPDIR="/tmp"
BGDIR=~/.e/e/backgrounds
for i in ${*}
do
pic=`basename $i .jpg`
echo Making e17 background $pic
echo "images{
image, \"$i\" LOSSY 95;//
}
collections
{
// Customize away ;)
group{
name, \"desktop/background\";
parts {
part {
name, \"background_image\";
mouse_events, 0;
description {
state, \"default\" 0.0;
rel1 {
relative, 0.0 0.0;
offset, 0 0;
}
rel2 {
relative, 1.0 1.0;
offset, -1 -1;
}
image {
normal, \"$i\";
}
fill {
origin {
relative, 0.0 0.0;
offset, 0 0;
}
size {
relative, 1.0 1.0;
offset, 0 0;
}
}
}
}
}
}">$TMPDIR/ebg.edc
edje_cc -id ./ -fd ./ $TMPDIR/ebg.edc $BGDIR/$pic.edj
rm $TMPDIR/ebg.edc
done
|
Let me know if you find this useful or if such a script already exists and I just didn't know about it. |
|
Back to top |
|
|
WladyX Guru
Joined: 25 Nov 2004 Posts: 503 Location: Romania
|
Posted: Wed Mar 22, 2006 7:30 pm Post subject: |
|
|
Hello, during e_modules emerging i get this:
Code: |
*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.22, ltmain.sh = 1.5.8) ***
Please run:
libtoolize --copy --force
if appropriate, please contact the maintainer of this
package (or your distribution) for help.
|
Any ideeas? Thanks. _________________ We are not alone. |
|
Back to top |
|
|
RuiP l33t
Joined: 15 Jan 2005 Posts: 643
|
Posted: Wed Mar 22, 2006 7:35 pm Post subject: |
|
|
WladyX wrote: | Hello, during e_modules emerging i get this:
Code: |
*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.22, ltmain.sh = 1.5.8) ***
Please run:
libtoolize --copy --force
if appropriate, please contact the maintainer of this
package (or your distribution) for help.
|
Any ideeas? Thanks. |
Hi, same here.
But the e_modules from thinktux.net emerged and work fine.
I use those now and wait to see if that is fixed.
Rui |
|
Back to top |
|
|
ppurka Advocate
Joined: 26 Dec 2004 Posts: 3256
|
Posted: Wed Mar 22, 2006 11:07 pm Post subject: |
|
|
thasheep wrote: |
Let me know if you find this useful or if such a script already exists and I just didn't know about it. |
You could use e17setroot to create the edj files. It has a whole lot of options which include tiling, scaling, centering, etc of the background image. |
|
Back to top |
|
|
Trevoke Advocate
Joined: 04 Sep 2004 Posts: 4099 Location: NY, NY
|
Posted: Thu Mar 23, 2006 2:59 pm Post subject: |
|
|
With the sanity problem...
Just edit the following file :
/usr/portage/distfiles/cvs-src/e_modules/evolume/ltmain.sh
Look for the libtool version number you see as being wrong..
Code: | PROGRAM=ltmain.sh
PACKAGE=libtool
VERSION=1.5.8 |
Change it to your libtool version (1.5.22 for me) and then emerge e_modules.
[edit: you may have to do this for more of the modules..] _________________ Votre moment detente
What is the nature of conflict? |
|
Back to top |
|
|
WladyX Guru
Joined: 25 Nov 2004 Posts: 503 Location: Romania
|
Posted: Thu Mar 23, 2006 3:04 pm Post subject: |
|
|
Thanks a lot, i'll try that! _________________ We are not alone. |
|
Back to top |
|
|
overtoperative n00b
Joined: 23 Mar 2006 Posts: 1
|
Posted: Thu Mar 23, 2006 9:51 pm Post subject: |
|
|
thanks trevoke, i was having the same problem as wladyx and the fix worked for me. |
|
Back to top |
|
|
ColdWind Retired Dev
Joined: 08 Dec 2005 Posts: 119 Location: Valencia, Spain
|
Posted: Thu Mar 23, 2006 9:59 pm Post subject: |
|
|
Thanls Trevoke. Worked fine (aplying only to evolume). |
|
Back to top |
|
|
Kaste Guru
Joined: 21 Dec 2005 Posts: 546 Location: /home Sweet /home
|
Posted: Fri Mar 24, 2006 5:49 am Post subject: |
|
|
I just updated my e_modules package and only that one because it was the only one that failed to compile yesterday when i updated the rest. Soon after that e basically crashed.
After killing X and trying to log into e again it just hangs almost imediately, probably trying to load the besaid modules.
Did anyone else encounter that? Workaround? I already tried updating the rest of enlightenment as well to no avail.
I will try getting rid of all configuration for enlightenment next and starting it as it is. |
|
Back to top |
|
|
Xylene Tux's lil' helper
Joined: 01 Sep 2003 Posts: 111
|
Posted: Fri Mar 24, 2006 10:06 pm Post subject: |
|
|
Is there anyway to get entranced to execute another command while loading? I'm trying to get Synergy to load when I start entranced via SSH (this machine is without a keyboard and mouse). |
|
Back to top |
|
|
rand200069 n00b
Joined: 13 Sep 2004 Posts: 10
|
Posted: Sat Mar 25, 2006 4:29 am Post subject: |
|
|
Hey guys, hopefully someone can help with my e17 woes. I am having trouble building ecore...here is the error that I am getting:
Code: | i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib/ecore -I../../../src/lib/ecore_evas -I../../../src/lib/ecore -I../../../src/lib/ecore_evas -I../../../src/lib/ecore_x -O3 -march=pentium4 -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer -pipe -Wall -MT ecore_evas_fb.lo -MD -MP -MF .deps/ecore_evas_fb.Tpo -c ecore_evas_fb.c -o ecore_evas_fb.o >/dev/null 2>&1
ecore_evas_x.c: In function `_ecore_evas_x_alpha_set':
ecore_evas_x.c:1387: error: structure has no member named `destination_alpha'
ecore_evas_x.c:1395: error: structure has no member named `destination_alpha'
ecore_evas_x.c: In function `ecore_evas_software_x11_new':
ecore_evas_x.c:2101: error: structure has no member named `destination_alpha'
ecore_evas_x.c:2109: error: structure has no member named `destination_alpha'
make[4]: *** [ecore_evas_x.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib/ecore -I../../../src/lib/ecore_evas -I../../../src/lib/ecore -I../../../src/lib/ecore_evas -I../../../src/lib/ecore_x -O3 -march=pentium4 -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer -pipe -Wall -MT ecore_evas.lo -MD -MP -MF .deps/ecore_evas.Tpo -c ecore_evas.c -fPIC -DPIC -o .libs/ecore_evas.o
i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib/ecore -I../../../src/lib/ecore_evas -I../../../src/lib/ecore -I../../../src/lib/ecore_evas -I../../../src/lib/ecore_x -O3 -march=pentium4 -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer -pipe -Wall -MT ecore_evas.lo -MD -MP -MF .deps/ecore_evas.Tpo -c ecore_evas.c -o ecore_evas.o >/dev/null 2>&1
make[4]: Leaving directory `/var/tmp/portage/ecore-9999/work/e17/libs/ecore/src/lib/ecore_evas'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/ecore-9999/work/e17/libs/ecore/src/lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/ecore-9999/work/e17/libs/ecore/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/ecore-9999/work/e17/libs/ecore'
make: *** [all] Error 2
* This is a LIVE CVS ebuild.
* That means there are NO promises it will work.
* If it fails to build, FIX THE CODE YOURSELF
* before reporting any issues.
!!! ERROR: x11-libs/ecore-9999 failed.
!!! Function enlightenment_die, Line 94, Exitcode 0
!!! emake failed
!!! SEND BUG REPORTS TO vapier@gentoo.org NOT THE E TEAM
!!! If you need support, post the topmost build error, NOT this status message.
|
Has anyone else seen this? I tried searching the forums for a similar error, but came up empty handed.
I have tried just about everything that I can think of and it still will not compile (going on 2 weeks, so I doubt it is the E CVS code itself). I have unmerged all of the E packages, and removed all of the files in /usr/portage/distfiles/cvs-src/. I have also cleared my ccache, which hopefully shouldn't matter. I have been using one of the scripts on gentoowiki for building e17, but I have also tried emerging each package in the correct order by hand...this is where I noticed something strange.
It looks like the ebuild for evas depends on imlib2, but that is not the correct build order, yet it gets built in that order anyway. I thought that this could be causing my problems with ecore. If Any thoughts? Am I just seriously confused or something?
This is the correct build order from get-e.org:
Code: | 1. e17/libs/eet
2. e17/libs/edb
3. e17/libs/evas
4. e17/libs/ecore
5. e17/libs/embryo
6. e17/libs/imlib2
7. e17/libs/edje
Last few lines removed from list... |
So if I have removed all of the e17 packages (emerge -C), the way portage wants to build it is:
Code: | 1. e17/libs/eet
2. e17/libs/edb
6. e17/libs/imlib2
3. e17/libs/evas
4. e17/libs/ecore
5. e17/libs/embryo
7. e17/libs/edje
|
If I haven't unmerged the packages, it doesn't build imlib2 before evas, but I assume that is because it was already built the last time.
One other thing I should mention I guess...I did try removing the imlib2 dependency from the evas ebuild, but I'm very n00b at editing ebuilds...portage didn't like the changes I made and complained about the ebuild not matching the recorded filesize.
Any help would be very appreciated!
Thanks,
Ryan |
|
Back to top |
|
|
golding Apprentice
Joined: 07 Jun 2005 Posts: 232 Location: Adelaide / South Australia
|
Posted: Sat Mar 25, 2006 12:20 pm Post subject: |
|
|
rand200069
first, when ever I have any build errors reporting problems because of evas linking, I re-emerge Evas.
second, this my E build order, has worked since I got the order right for etk & evfs. I did have e17genmenu on the end, but that is included in e_modules now and deprecated as a single ebuild.
eet
dev-db/edb
evas
ecore
embryo
imlib2
edje
e
epeg
media-libs/epsilon
esmart
entrance
emotion
eclair
ewl
engrave
e_utils
e_modules
etox
erss
entice
engage
etk
exhibit
embrace
examine
emotion
enhance
evfs
entropy
enterminus
third, for any changes to the ebuild, don't forget to digest the ebuild afterwards, before you try to emerge it. i.e. Code: | ebuild app.ebuild digest | from within the ebuild directory. This will cause the manifest to re-register any size and md5 changes.
finally,
If you have insane CFLAGS, CXXFLAGS or LDFLAGS in your make.conf this can trigger all sorts of build problems. The most sane I have come across, not really knowing anything too much about them, are from here, Bob P's Stage 1/3 Installation for Gentoo or leave them at default with no added features.
You would be well advised to read the entire thread E17 is coming?? (all 3 parts) from start to end, everything I have shown above is in it. _________________ Regards, Robert
..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers. |
|
Back to top |
|
|
rand200069 n00b
Joined: 13 Sep 2004 Posts: 10
|
Posted: Sat Mar 25, 2006 3:47 pm Post subject: |
|
|
Thanks for the response golding.
Your build order matches the order that I'm trying to get (at least for the EFL stuff at the beginning). I was just kind of curious as to why evas depends on imlib2 when that is not the posted / correct build order. Each time I have tried to build and failed on ecore, I have removed and re-emerged evas (all of EFL actually) before starting again.
Thanks for the tip on digesting ebuilds...I knew there was a way to do it! I'll try that this afternoon when I get some time to try and build this again.
And lastly on the CFLAGS...mine just about match the ones posted in Bob P's thread...I actually used his Stage 1/3 install method for this box. Here are my CFLAGS:
Code: | CFLAGS="-O3 -march=pentium4 -fforce-addr -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer -pipe"
CXXFLAGS="${CFLAGS}"
|
The only differences that I have from Bob P's suggested ones are "-march=pentium4" (as opposed to p3) and "-momit-leaf-frame-pointer". I don't know much about that last one or if it is one that is considered "insane" I will look up that CFLAG and see what it does and if anyone else has had trouble building with it.
It looks like I may have to read through all 3 of the "E17 is coming" threads...they're just so huge that it is a daunting task
I will probably be back asking for more help, or posting what finally fixed it for me.
Thanks,
Ryan |
|
Back to top |
|
|
RuiP l33t
Joined: 15 Jan 2005 Posts: 643
|
Posted: Sat Mar 25, 2006 4:02 pm Post subject: |
|
|
hi rand200069,
as far as i know the only broken packages of e17 is the e_modules (see some posts above) on sf server (at thinktux are ok) and the evas package of thinktux.net (the sf version are ok). The ecore package is fine on both servers.
You can try to go to -O2 on your CFLAg but i doub't it's that...
Some things one should always do when came to e17 errors are:
Check if you got something related with e17 libraries on /usr/local/lib/ (like evas, eet or ecore .la or .so files) if so delete them and try again.
If that fail, try emerge -C all e packages and move /usr/portage/distfile/cvs-src (or your distfile path if you changed) to a temporary folder. Then try to emerge everything from a fresh begining.
good luck. _________________ ESTRAGON: We've lost our rights?
VLADIMIR: (distinctly) We got rid of them. |
|
Back to top |
|
|
rand200069 n00b
Joined: 13 Sep 2004 Posts: 10
|
Posted: Sun Mar 26, 2006 3:45 am Post subject: |
|
|
RuiP,
I didn't think that any of the e17 packages were broken...it seems to be on my system. I tried setting my optimization in the CFLAGS to -02, but that had no effect...it still failed to compile. I have tried removing all of the source in /usr/portage/distfiles/cvs-src/ and I have also manually removed all of the E related files in /usr/local/lib/. I have also run "emerge -C eet dev-db/edb evas ecore embryo imlib2...etc etc". None of this seems to work.
Another interesting thing to note...I manually downloaded the source from CVS and compiled by hand using: Code: | ./autogen.sh && make | Using this method for each package, ecore builds correctly. The only difference that I can see is that my CFLAGS from /etc/make.conf were not used. So now I have two options, I think.
First, I can force the manual install to use my CFLAGS...but I'm not sure how to do this.
Second, I will remove my CFLAGS one by one and attempt to build ecore and see if one of them is causing the build errors.
Thanks for the help so far guys!
Ryan |
|
Back to top |
|
|
rand200069 n00b
Joined: 13 Sep 2004 Posts: 10
|
Posted: Sun Mar 26, 2006 3:57 am Post subject: |
|
|
Well...now that is weird! After the manual CVS install, I re-emerged the packages and ecore built without the error, using my normal CFLAGS. I don't know why that seems to have fixed it, but I guess I will just continue building the rest of e17...hopefully it goes smoothly now.
Ryan |
|
Back to top |
|
|
krazykit Tux's lil' helper
Joined: 28 Aug 2004 Posts: 91
|
Posted: Mon Mar 27, 2006 6:15 pm Post subject: |
|
|
For those of you wondering, someone committed a bunch of stuff that's supposed to be autogen'd into CVS (for the e_modules).
Relevant IRC stuff from raster:
Code: | [09:04] <@raster> it should not be in cvs
[09:04] <@raster> it is auto-gemerated
[09:04] <@raster> or shoudl be
[09:05] <@raster> unless someone fucked cvs commits up
[09:05] <@raster> aah
[09:05] <@raster> its in evolume
[09:05] <@raster> someone stupidly committed it
[09:05] <@raster> actually
[09:05] <@raster> they committed everythng
[09:05] <@raster> all the auto-generated files
[09:05] <@raster> oh bah
[09:05] <@raster> forget it
[09:06] <@raster> dont build emodules |
So hopefully it's been sorted out, or will be shortly. |
|
Back to top |
|
|
H-Dragon Guru
Joined: 22 Oct 2002 Posts: 547
|
Posted: Tue Mar 28, 2006 10:17 am Post subject: |
|
|
hi guys.... i had e17 running perfectly fine a week ago.
then i updated to 025 and now i am missing my SYSTRAY!
(i dont know where it came from but now its gone)
i did NOT use engage.... i used the ibar-module.
and there was a tiny window-thingy where my systray-icons were (skype and the like...)
does anyone know what that was?????
thanks!!!
_________________ WEBSITE
Do not meddle with the affairs of Dragons, for you are crunchy and tasty with ketchup! |
|
Back to top |
|
|
boneyfrog Apprentice
Joined: 26 Apr 2005 Posts: 152
|
Posted: Tue Mar 28, 2006 4:31 pm Post subject: |
|
|
H-Dragon wrote: | hi guys.... i had e17 running perfectly fine a week ago.
then i updated to 025 and now i am missing my SYSTRAY!
(i dont know where it came from but now its gone)
i did NOT use engage.... i used the ibar-module.
and there was a tiny window-thingy where my systray-icons were (skype and the like...)
does anyone know what that was?????
thanks!!!
|
Line 161 of /e17/apps/e/src/modules/itray/e_mod_main.c wrote: |
e_module_dialog_show(_("Enlightenment ITray Module"),
_("This is the ITray system tray module for Enlightenment.<br>"
"It will hold system tray icons.<br>"
"Beware that this can be buggy due to many systray providing<br>"
"applications not handling the protocol properly, and the way<br>"
"systray icons work being very limiting and hacky. Do not use<br>"
"this module unless you absolutely must, and if you do, beware<br>"
"of issues that will appear."
));
|
basicly raster got fed up with how poorly the protocol was being followed by other developers and the dr17 user based support questions of "how come app X's systray icon works but app Y's systray icon doesn't" the code for the itray module still exist in cvs it is just not being built by default you will have to go in and build it yourself if you realy want it and i don't think that any of the devs are actively mainting (making sure the thing works) it right now |
|
Back to top |
|
|
Marcars n00b
Joined: 20 Aug 2005 Posts: 8 Location: Arnhem, Netherlands
|
Posted: Tue Mar 28, 2006 5:49 pm Post subject: |
|
|
I'm in the process of installing E17 on my laptop on which I have installed E17 before but this time I get the following when emerging EWL:
This is the end of the failed build:
checking for __attribute__... yes
Prefix is /usr
checking for evas-config... /usr/bin/evas-config
checking for evas - version >= 0.9.9... yes
checking for ecore-config... /usr/bin/ecore-config
checking for ecore - version >= 0.9.9... yes
checking for Evas_Engine_Software_X11.h... yes
checking for Ecore_X.h... yes
checking for Evas_Engine_GL_X11.h... no
configure: error: opengl X11 requested but no evas/ecore support found
!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/ewl-9999/work/e17/libs/ewl/config.log
!!! ERROR: x11-libs/ewl-9999 failed.
Call stack:
ebuild.sh, line 1526: Called dyn_compile
ebuild.sh, line 923: Called src_compile
ewl-9999.ebuild, line 30: Called enlightenment_src_compile
enlightenment.eclass, line 142: Called econf '--enable-software-x11' '--enable-opengl-x11' '--disable-fbcon'
ebuild.sh, line 527: Called die
!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
Does anybody have an idea as to what's wrong? My system is built with opengl....
Any ideas? |
|
Back to top |
|
|
|