According an enlightenment developer on the enlightenment mailing list:
> could someone answer why e_modules from anonymous CVS doesn't compile?
Because raster deleted gadman. This broke some modules. Most modules
still work, and e_modules was never meant to be treated as a single,
compilable unit. Compile them individually.
Should e_modules be split up into several separate ebuilds? Under x11-plugins, perhaps? Or how about some USE flags? Or how about some "unofficial" support to control what to build/what not to build via an undocumented environment variable?
no, fix the e_modules code ... i dont feel like maintaining a ton of little ebuilds at this time
Created attachment 96473 [details]
Well, this breakage sucks. Until it's fixed, try this one instead:
- modified ebuild that uses flags for each of the modules (if more modules are added into CVS, they will be built automagically without any flags). Just enable those that compile in /etc/portage/package.keywords
Err, /etc/portage/package.use obviously.
Hmm.... thanks for that. I've already got a solution though - check out the cvs e_modules dir myself, autogen.sh it with 'NOCONFIGURE' set to 1, then go into the directories of the modules I want and do a './configure && make -j2 && make install' myself - after deleting ~/.e/e/modules/* that is.
make install will in this case put stuff by default into ~/.e/e/modules/xxx (i.e. don't do it as root :-) )
Thanks for that tho'
*** Bug 147818 has been marked as a duplicate of this bug. ***
*** Bug 148030 has been marked as a duplicate of this bug. ***
(In reply to comment #2)
> Created an attachment (id=96473) 
> Well, this breakage sucks. Until it's fixed, try this one instead:
> - modified ebuild that uses flags for each of the modules (if more modules are
> added into CVS, they will be built automagically without any flags). Just
> enable those that compile in /etc/portage/package.keywords
I see in your patch something prety usefull. I will gived it a try and hope they will had it to the cvs.
I don't want all the module in first place but it so simple to emerge it... now you've added the control I needed. Thank you Jakub Moc!
*** Bug 150439 has been marked as a duplicate of this bug. ***
*** Bug 158919 has been marked as a duplicate of this bug. ***
I have tried to emerge both e_modules, & just tclock using an overlay.
So is nobody going to fix this bug?
*** Bug 160323 has been marked as a duplicate of this bug. ***
*** Bug 160325 has been marked as a duplicate of this bug. ***
Created attachment 105633 [details]
An updated ebuild...
according to bug #158919 , emerge -C =sys-devel/automake-1.10 may help, but since it is now a requierd dep ... we cant even try this workaround ... I am not sure what to propose instead, nor even ask for ...
fact is, I do have this bug at the moment.
I know you oficially wont fix, but in case any one can think of a workaround ...
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
configure.in:23: required file `./config.rpath' not found
configure.in:10: installing `./missing'
configure.in:10: installing `./install-sh'
po/Makefile.am:6: addsuffix .mo,$(ALL_LINGUAS: non-POSIX variable name
po/Makefile.am:6: (probably a GNU make extension)
po/Makefile.am:8: addsuffix .po,$(ALL_LINGUAS: non-POSIX variable name
po/Makefile.am:8: (probably a GNU make extension)
po/Makefile.am:10: `%'-style pattern rules are a GNU make extension
Makefile.am:39: `%'-style pattern rules are a GNU make extension
Makefile.am: installing `./depcomp'
* 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-plugins/e_modules-weather-9999 failed.
ebuild.sh, line 1614: Called dyn_compile
ebuild.sh, line 971: Called qa_call 'src_compile'
environment, line 3788: Called src_compile
ebuild.sh, line 1304: Called enlightenment_src_compile
enlightenment.eclass, line 140: Called enlightenment_die 'autogen failed'
enlightenment.eclass, line 104: Called die
!!! autogen failed
!!! SEND BUG REPORTS TO email@example.com NOT THE E TEAM
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/log/portage/x11-plugins:e_modules-weather-9999:20070218-235849.log'.
!!! This ebuild is from an overlay: '/usr/portage/local/layman/enlightenment'
(In reply to comment #13)
> Created an attachment (id=105633) 
Where shall I put this ebuild ? when I put it in doublehp/e_modules in my own overlay /opt/doublehp/usr/portage it does not work better than x11-plugins/e_modules from /usr/portage/local/layman/enlightenment
This whole thing moved to an overlay, this bug is not relevant any more.
works for me.