Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
E17 is coming? (part 5)
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3 ... 28, 29, 30  Next  
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
UberPinguin
Guru
Guru


Joined: 20 Nov 2005
Posts: 505
Location: 2416.94 Miles From Home

PostPosted: Sun Jan 07, 2007 2:57 am    Post subject: E17 is coming? (part 5) Reply with quote

Continued from E17 is coming? (part 4)
Long threads hurt the forums...

For those of you interested in the previous incarnations of this topic:


Last edited by UberPinguin on Fri Jan 12, 2007 2:20 pm; edited 1 time in total
Back to top
View user's profile Send private message
UberPinguin
Guru
Guru


Joined: 20 Nov 2005
Posts: 505
Location: 2416.94 Miles From Home

PostPosted: Sun Jan 07, 2007 3:05 am    Post subject: Reply with quote

punter wrote:
UberPinguin wrote:

I'm using e17 w/ Bling enabled w/ AIGLX and XAA on a Radeon Mobility 7500 right now, and it's pretty **** fast.


UberPinguin, why do you have AIGLX enabled?
I'm just double-checking my xorg options.... for the bling module to work, the "composite" extension should be enabled, right?
the AIGLX plays no part in here.

it's rather strange..... even scrolling down a webpage in firefox becomes jumpy and slow when i have bling module enabled... and this is with a solid firefox window (i.e. no transparency involved).
how could the bling module affect the re-drawings of a firefox window?
and this is with all the "shadow", "window in/out" and "fade opacity" options disabled in bling module configuration.

AIGLX provides better overall performance for me.
I found that adjusting the timing on 'fade in/out' makes a difference. I know we have different cards, but parts of my xorg.conf may help you. Or not :lol:
Back to top
View user's profile Send private message
morbus
Tux's lil' helper
Tux's lil' helper


Joined: 10 May 2004
Posts: 139
Location: Munich

PostPosted: Sun Jan 07, 2007 12:41 pm    Post subject: Reply with quote

BTW masking autmake-1.10 to let e compile is just an ugly workarround, you should put E17_WANT_AUTOMAKE="1.9" into make.conf instead (at least until this issues is fixed in the ebuild itself).
Back to top
View user's profile Send private message
UberPinguin
Guru
Guru


Joined: 20 Nov 2005
Posts: 505
Location: 2416.94 Miles From Home

PostPosted: Sun Jan 07, 2007 3:43 pm    Post subject: Reply with quote

morbus wrote:
BTW masking autmake-1.10 to let e compile is just an ugly workarround, you should put E17_WANT_AUTOMAKE="1.9" into make.conf instead (at least until this issues is fixed in the ebuild itself).

Thanks for the tip.
Back to top
View user's profile Send private message
ppurka
Advocate
Advocate


Joined: 26 Dec 2004
Posts: 2782

PostPosted: Sun Jan 07, 2007 8:29 pm    Post subject: Reply with quote

Doesn't work with e_modules :(
Actually everything upto e emerges fine for me, even with automake 1.10. It is e_modules which fails (even when I set E17_WANT_AUTOMAKE="1.9" in /etc/make.conf).
Back to top
View user's profile Send private message
bendy
Apprentice
Apprentice


Joined: 18 May 2002
Posts: 274
Location: Gloucester, UK

PostPosted: Sun Jan 07, 2007 8:47 pm    Post subject: Reply with quote

ppurka wrote:
Doesn't work with e_modules :(

Actually, e_modules doesn't compile properly anyway. Within the monolithic e_modules packages are some individual modules that are broken (e.g. engage and calendar). After emerging fails, you can go into some individual module build directories under /var/tmp/portage/e_modules/work/e_modules/ and type "make install".

I have the mixer, wlan, tclock and screenshot modules working this way.
Back to top
View user's profile Send private message
UberPinguin
Guru
Guru


Joined: 20 Nov 2005
Posts: 505
Location: 2416.94 Miles From Home

PostPosted: Sun Jan 07, 2007 8:52 pm    Post subject: Reply with quote

bendy wrote:
ppurka wrote:
Doesn't work with e_modules :(

Actually, e_modules doesn't compile properly anyway. Within the monolithic e_modules packages are some individual modules that are broken (e.g. engage and calendar). After emerging fails, you can go into some individual module build directories under /var/tmp/portage/e_modules/work/e_modules/ and type "make install".

I have the mixer, wlan, tclock and screenshot modules working this way.

Actually, ppurka is quite aware of this and wrote a modified ebuild to deal with it: http://forums.gentoo.org/viewtopic-p-3554929-highlight-emodules+modified.html#3554929
It uses USE flags to disable malfunctioning modules.
Back to top
View user's profile Send private message
bendy
Apprentice
Apprentice


Joined: 18 May 2002
Posts: 274
Location: Gloucester, UK

PostPosted: Sun Jan 07, 2007 9:09 pm    Post subject: Reply with quote

UberPinguin wrote:
Actually, ppurka is quite aware of this and wrote a modified ebuild to deal with it: http://forums.gentoo.org/viewtopic-p-3554929-highlight-emodules+modified.html#3554929
It uses USE flags to disable malfunctioning modules.

Sorry, ppurka.....
Back to top
View user's profile Send private message
ppurka
Advocate
Advocate


Joined: 26 Dec 2004
Posts: 2782

PostPosted: Sun Jan 07, 2007 9:18 pm    Post subject: Reply with quote

bendy wrote:
Sorry, ppurka.....
Heh, nothing to be sorry about. :) I was only wondering if someone had everything working good with the E17_WANT_AUTOMAKE hack in /etc/make.conf that was mentioned in the bug report.
As for e_modules, bling and cpu get past the automake stage, but it is mem, net, tclock which fails. Haven't tried the other modules, since I don't use them.
Back to top
View user's profile Send private message
UberPinguin
Guru
Guru


Joined: 20 Nov 2005
Posts: 505
Location: 2416.94 Miles From Home

PostPosted: Sun Jan 07, 2007 11:32 pm    Post subject: Reply with quote

ppurka wrote:
bendy wrote:
Sorry, ppurka.....
Heh, nothing to be sorry about. :) I was only wondering if someone had everything working good with the E17_WANT_AUTOMAKE hack in /etc/make.conf that was mentioned in the bug report.
As for e_modules, bling and cpu get past the automake stage, but it is mem, net, tclock which fails. Haven't tried the other modules, since I don't use them.

That's progress at least. Last time I tried with 1.10, bling was failing.
Back to top
View user's profile Send private message
sudharsh
n00b
n00b


Joined: 20 Apr 2006
Posts: 12
Location: Chennai, India

PostPosted: Mon Jan 08, 2007 5:37 am    Post subject: Reply with quote

i did compile all the thingies from the e17 cvs, to save yourselves some aspirin, you will need automake 1.9 and autoconf 2.60...For some reason automake1.10 just didnt work..:(
_________________
sudharsh
Back to top
View user's profile Send private message
UberPinguin
Guru
Guru


Joined: 20 Nov 2005
Posts: 505
Location: 2416.94 Miles From Home

PostPosted: Mon Jan 08, 2007 1:43 pm    Post subject: Reply with quote

sudharsh wrote:
i did compile all the thingies from the e17 cvs, to save yourselves some aspirin, you will need automake 1.9 and autoconf 2.60...For some reason automake1.10 just didnt work..:(

Ahhhhhh. I'll bet that's it. What do you want to bet that you also need to specify WANT_AUTOCONF="2.60" (assuming that's a valid variable...)? I think that's why just 'WANT_AUTOMAKE' is failing. Note that I have not yet tested either WANT_AUTOMAKE or WANT_AUTOCONF, I'm just working based on what others have posted.
I'm behind a fw/proxy for most of today, so I won't be able to test anything until later.
Back to top
View user's profile Send private message
wwonderllama
n00b
n00b


Joined: 07 Mar 2005
Posts: 14

PostPosted: Mon Jan 08, 2007 7:07 pm    Post subject: Reply with quote

I've been struggling with the appropriate build environment for e17 as well. Currently, I'm at:

# equery list autoconf
[ Searching for package 'autoconf' in all categories among: ]
* installed packages
[I--] [ ] sys-devel/autoconf-2.13 (2.1)
[I--] [ ] sys-devel/autoconf-2.59-r7 (2.5)
[I--] [ ] sys-devel/autoconf-wrapper-4-r3 (0)

# equery list automake
[ Searching for package 'automake' in all categories among: ]
* installed packages
[I--] [ ] sys-devel/automake-1.4_p6 (1.4)
[I--] [ ] sys-devel/automake-1.5 (1.5)
[I--] [ ] sys-devel/automake-1.6.3 (1.6)
[I--] [ ] sys-devel/automake-1.7.9-r1 (1.7)
[I--] [ ] sys-devel/automake-1.8.5-r3 (1.8)
[I--] [ ] sys-devel/automake-1.9.6-r2 (1.9)
[I--] [ ] sys-devel/automake-1.10 (1.10)
[I--] [ ] sys-devel/automake-wrapper-1-r1 (0)

I'm using

WANT_AUTOCONF="2.50" (suggested by get-e.org)
E17_WANT_AUTOMAKE="1.9" (suggested in this thread)
with automake-wrapper-1-r1 (suggested elsewhere.. forums of get-e.org, IIRC)

If I simply emerge e-9999, it errors out with:

Quote:
***** autoconf *****

configure.in:19: error: possibly undefined macro: AC_C___ATTRIBUTE__
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.


To avert other errors, I unpack the source, then run autopoint -f.
At which point, I can ebuild e-9999 compile, which completes. When I attempt the ebuild e-9999 install, it hums along nicely until:

Quote:

make[3]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e/data'
make[2]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e/data'
make[1]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e/data'
Making install in doc
make[1]: Entering directory `/var/tmp/portage/e-9999/work/e17/apps/e/doc'
make[2]: Entering directory `/var/tmp/portage/e-9999/work/e17/apps/e/doc'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/share/enlightenment/doc" || mkdir -p -- "/var/tmp/portage/e-9999/image//usr/share/enlightenment/doc"
/bin/install -c -m 644 'documentation.html' '/var/tmp/portage/e-9999/image//usr/share/enlightenment/doc/documentation.html'
/bin/install -c -m 644 'FDO.txt' '/var/tmp/portage/e-9999/image//usr/share/enlightenment/doc/FDO.txt'
/bin/install -c -m 644 'cache.txt' '/var/tmp/portage/e-9999/image//usr/share/enlightenment/doc/cache.txt'
/bin/install -c -m 644 'enlightenment.png' '/var/tmp/portage/e-9999/image//usr/share/enlightenment/doc/enlightenment.png'
make[2]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e/doc'
make[1]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e/doc'
Making install in po
make[1]: Entering directory `/var/tmp/portage/e-9999/work/e17/apps/e/po'
/bin/sh @MKINSTALLDIRS@ /var/tmp/portage/e-9999/image//usr/share
/bin/sh: @MKINSTALLDIRS@: No such file or directory
make[1]: *** [install-data-yes] Error 127
make[1]: Leaving directory `/var/tmp/portage/e-9999/work/e17/apps/e/po'
make: *** [install-recursive] Error 1
* 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-wm/e-9999 failed.


So, I'm at my 3rd brick wall. Can anyone offer suggestions?


Thanks,
PhillW
Back to top
View user's profile Send private message
UberPinguin
Guru
Guru


Joined: 20 Nov 2005
Posts: 505
Location: 2416.94 Miles From Home

PostPosted: Tue Jan 09, 2007 1:48 pm    Post subject: Reply with quote

I don't know whether this will help you or not, but here's what I've got:
Code:
$ equery list autoconf
[ Searching for package 'autoconf' in all categories among: ]
 * installed packages
[I--] [  ] sys-devel/autoconf-2.13 (2.1)
[I--] [  ] sys-devel/autoconf-2.60 (2.5)
[I--] [  ] sys-devel/autoconf-wrapper-3.2-r2 (0)

$ equery list automake
[ Searching for package 'automake' in all categories among: ]
 * installed packages
[I--] [  ] sys-devel/automake-1.4_p6 (1.4)
[I--] [  ] sys-devel/automake-1.5 (1.5)
[I--] [  ] sys-devel/automake-1.6.3 (1.6)
[I--] [  ] sys-devel/automake-1.7.9-r1 (1.7)
[I--] [  ] sys-devel/automake-1.8.5-r3 (1.8)
[I--] [  ] sys-devel/automake-1.9.6-r2 (1.9)
[I--] [  ] sys-devel/automake-wrapper-2-r1 (0)
I just updated e17 last night, and everything (that's not actually broken) built and installd just fine. Perhaps you need autoconf-2.60 (which, for whatever reason, is still in the 2.5 slot o.O)?
Back to top
View user's profile Send private message
wwonderllama
n00b
n00b


Joined: 07 Mar 2005
Posts: 14

PostPosted: Tue Jan 09, 2007 2:46 pm    Post subject: Reply with quote

Actually, I was at Autoconf 2.60, but downgraded to a 2.5x series in case 2.60 wasn't fully a "2.5" like the e17 build wants. I notice your autoconf-wrapper is an older version too. I'll go ahead and install the versions you have and see if that helps. Thanks for the reply!

Edit: I think my problem may be that once I get the compile going (after commenting out the AC_C___ATTRIBUTE_ in configure.in), I get a warning:

config.status: WARNING: po/Makefile.in.in seems to ignore the --datarootdir setting

The po/ directory is where my install stops. (as you can see in my previous post)

Any thoughts on how to fix it?
Back to top
View user's profile Send private message
wwonderllama
n00b
n00b


Joined: 07 Mar 2005
Posts: 14

PostPosted: Tue Jan 09, 2007 3:11 pm    Post subject: Reply with quote

Present versions recommended are GNU m4 1.4, autoconf 2.54, automake 1.7, libtool 1.4.3, and gettext 0.11.5.

Can someone post their working versions from:
equery list m4
equery list libtool
equery list gettext
equery list autoconf
equery list automake

I'd like to get a sane build environment if I can, so I can better figure out where the problem is.

Thanks much.
PhillW
Back to top
View user's profile Send private message
UberPinguin
Guru
Guru


Joined: 20 Nov 2005
Posts: 505
Location: 2416.94 Miles From Home

PostPosted: Tue Jan 09, 2007 3:32 pm    Post subject: Reply with quote

Code:

$ equery list m4
* installed packages
sys-devel/m4-1.4.8

$ equery list libtool
 * installed packages
sys-devel/libtool-1.5.22

$ equery list gettext
 * installed packages
dev-perl/Locale-gettext-1.05
sys-devel/gettext-0.16.1

$ equery list autoconf
 * installed packages
sys-devel/autoconf-2.13
sys-devel/autoconf-2.60
sys-devel/autoconf-wrapper-3.2-r2

$ equery list automake
 * installed packages
sys-devel/automake-1.4_p6
sys-devel/automake-1.5
sys-devel/automake-1.6.3
sys-devel/automake-1.7.9-r1
sys-devel/automake-1.8.5-r3
sys-devel/automake-1.9.6-r2
sys-devel/automake-wrapper-2-r1
Back to top
View user's profile Send private message
wwonderllama
n00b
n00b


Joined: 07 Mar 2005
Posts: 14

PostPosted: Tue Jan 09, 2007 6:57 pm    Post subject: Reply with quote

Thanks for that, UP. From those packages, I assume you're using some ~x86 packages?

I've updated my packages to reflect yours, but I'm still having the same problem.

Are you able to simply emerge e-9999 and the whole thing goes off without a hitch, or do you have to use autopoint mid-way through the emerge?



Edit: spelling
Back to top
View user's profile Send private message
ppurka
Advocate
Advocate


Joined: 26 Dec 2004
Posts: 2782

PostPosted: Tue Jan 09, 2007 7:34 pm    Post subject: Reply with quote

wwonderllama wrote:
Thanks for that, UP. From those packages, I assume you're using some ~x86 packages?
Try these versions, all stable packages:
Code:
~> equery -q list m4
[I--] [  ] sys-devel/m4-1.4.7 (0)
~> equery -q list libtool
[I--] [  ] sys-devel/libtool-1.5.22 (1.5)
~> equery -q list gettext
[I--] [  ] dev-perl/Locale-gettext-1.05 (0)
[I--] [  ] sys-devel/gettext-0.15 (0)
~> equery -q list autoconf
[I--] [  ] sys-devel/autoconf-2.13 (2.1)
[I--] [  ] sys-devel/autoconf-2.61 (2.5)
[I--] [  ] sys-devel/autoconf-wrapper-4-r3 (0)
~> equery -q list automake
[I--] [  ] sys-devel/automake-1.4_p6 (1.4)
[I--] [  ] sys-devel/automake-1.5 (1.5)
[I--] [  ] sys-devel/automake-1.6.3 (1.6)
[I--] [  ] sys-devel/automake-1.7.9-r1 (1.7)
[I--] [  ] sys-devel/automake-1.8.5-r3 (1.8)
[I--] [  ] sys-devel/automake-1.9.6-r2 (1.9)
[I--] [  ] sys-devel/automake-wrapper-3-r1 (0)

Do note that you should not only emerge e, but also all the libraries it depends upon in a specific order. My order of building e is as follows:
Code:
eet imlib2 imlib2_loaders evas ecore embryo edje epeg epsilon esmart exml e e_modules entrance
Back to top
View user's profile Send private message
wwonderllama
n00b
n00b


Joined: 07 Mar 2005
Posts: 14

PostPosted: Tue Jan 09, 2007 8:46 pm    Post subject: Reply with quote

Thanks ppurka, your package list looks exactly like mine did before I started downgrading/upgrading. The only difference is I was at autoconf-1.10. Downgrading was the first thing I did, which gave me the packages you list.

I'm pole-axed as to why I get the AC_C___ATTRIBUTE__ error while noone else does, as it seems to be some auto* problem.

Currently, I can get to compile via acrobatics and ebuild e compile/install, but it's ignoring my USE flags apparently. If I try to run e, it complains about not finding ecore_directfb.lib, but I put -directfb in my USE flags.

I just ran a standard emerge, ctrl-z'ing at opportune points to edit the configuration files but letting emerge do the heavy lifting, and it's not complaining about directfb. Looks like I have a fair amount of testing to do to see if this is workable.

However, I'd really appreciate any help on figuring out my actual problem. I hate using hacks and this is obviously working for other people.

For what it's worth, I'm running stable with select packages (e and a few others) ~x86.
Back to top
View user's profile Send private message
UberPinguin
Guru
Guru


Joined: 20 Nov 2005
Posts: 505
Location: 2416.94 Miles From Home

PostPosted: Tue Jan 09, 2007 9:58 pm    Post subject: Reply with quote

wwonderllama wrote:
Thanks for that, UP. From those packages, I assume you're using some ~x86 packages?

I've updated my packages to reflect yours, but I'm still having the same problem.

Are you able to simply emerge e-9999 and the whole thing goes off without a hitch, or do you have to use autopoint mid-way through the emerge?

Yeah, my system's almost purely ~x86, plus a few x86 and some -* :twisted:
I haven't had to do any of the acrobatics you're describing. Perhaps you should use the easy_e17.sh script maintained by Morlenxus instead? I've heard it's very good, but haven't used it myself. It doesn't use ebuilds, but IIRC has the advantage of putting everything in the proper place for pre-alpha software - /opt/.
Back to top
View user's profile Send private message
sudharsh
n00b
n00b


Joined: 20 Apr 2006
Posts: 12
Location: Chennai, India

PostPosted: Wed Jan 10, 2007 10:00 am    Post subject: Reply with quote

the easy_e17 script is good...but you might want to keep in mind the following things

Default installation downloads all sorts of nonsense you wouldnt need...select packages that you want, and the etk_server froze package my box with 100% CPU usage during compilation, I have an athlon xp 2000+ with 768 megs of RAM..no not errors, just grinds the box like a windows 95 machine. The guys in #e say that, it expected...
If anyone had that etk_server compiled without problems, please let me know
_________________
sudharsh
Back to top
View user's profile Send private message
GODLiKE
n00b
n00b


Joined: 11 Jan 2007
Posts: 49

PostPosted: Thu Jan 11, 2007 3:17 am    Post subject: Reply with quote

Hey people. Been reading the forums anonymously for a while (this E thread is the longest I've ever seen!)

Well, I had installed E a few weeks back, miraculously on the first try. Just unmasked, emerged and it was it. This time around had a few more problems (imlib2 being broken on CVS, which got fixed later, but I emerged an older version of imlib2, and evas with all the directfb thing). But I got it running in the end :).

The problem is that any application other than those native to E (like the control panel or stuff) don't show any icons (well, they show the classic tiny little white window, much like Windows' "unknown application"does. Excuse my reference to Windows here, but it's been only a month since I started with Linux (right on Gentoo 8)) and I still haven't completely migrated to it). This happens not only on the upper left corner of the app window but also on iBox and on the Pager. I was wondering if anyone ever had the same issue and how did he/she manage to fix it, since on my first try of E a few weeks back it was perfectly fine from the beginning.

Thanks in advance!
_________________
GERÓNIMOOOOOOOOOOOOOOOOOOOO!!!
Back to top
View user's profile Send private message
stobbsm
Guru
Guru


Joined: 23 May 2004
Posts: 452

PostPosted: Thu Jan 11, 2007 3:40 am    Post subject: Reply with quote

My question: When will e17 ever NOT be coming? It's been coming for many years now, and it just keeps coming.
_________________
Sysadmin of Ubuntu systems and servers....
Although my own server is gentoo....
Back to top
View user's profile Send private message
ppurka
Advocate
Advocate


Joined: 26 Dec 2004
Posts: 2782

PostPosted: Thu Jan 11, 2007 4:01 am    Post subject: Reply with quote

stobbsm wrote:
My question: When will e17 ever NOT be coming? It's been coming for many years now, and it just keeps coming.
As long as there exists cvs ;) Hail cvs! :twisted:
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2, 3 ... 28, 29, 30  Next
Page 1 of 30

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum