With cairo in the use flags, updating the liveSVN build of e17 will fail while compiling /var/tmp/portage/x11-libs/evas-9999/work/evas/src/modules/engines/cairo_x11/evas_engine.c at line 934 or so. ( http://pastebin.com/f238d77c6 ) Googling around led me to this: http://firstname.lastname@example.org/msg19996.html where Rasterman says not to use it. USE="-cairo" fixed it (as did editing package.use).
Steps to Reproduce:
1. have 'cairo' in your use flags (note that I didn't have it explicitly in my make.conf but it showed up in emerge --info)
2. emerge evas-9999 (both via emerge-e17.sh and emerge -av @enlightenment-live)
3. watch everything work until evas errors out as in the pastebin above
evas fails to compile, then so does most of the other stuff after that
compiled and run
I see that cairo is included in the IUSE flags in the vapier overlay for both evas-0.9.9.050 and evas-9999. Given the above email from Rasterman, perhaps it should be taken out?
Apologies if this is the wrong place to report this bug, but I know it's not an e17 bug and didn't want to post it in their trac thing.
If nothing else, I'm posting this so nobody else has to pull their hair out over a weekend figuring this out as it was hard to track down.
From what overlay did you take the ebuild? I don't see it in the main tree.
From Vapier's, http://overlays.gentoo.org/dev/vapier/wiki/enlightenment
your sync is out of date
I removed the cairo USE flag from evas some days ago, so this should be fixed.
Thanks all, I see the new ebuild now.
FWIW, I was dealing with this issue the 27th to the 28th, I dunno if that was before the change or not. I probably should have updated my overlay after fixing it before submitting the bug.
Thanks again, I love e17 (&& gentoo).