search

fusion809 / sabayon-tools-old

My Portage overlay, which contains miscellaneous ebuilds that could be upstreamed to the Portage Tree. This is an old, unmaintained version that became too large to manage.
GNU General Public License v3.0
0 stars 2 forks source link

moksha-9999 fails to build #5

Open fusion809 opened 9 years ago

fusion809 commented 9 years ago

@necrose99

The moksha-9999, while it contains very different contents to moksha-0.1.0's ebuild is giving the same build errors. Namely:

>>> Source compiled.
 * --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
 * LOG FILE: "/var/log/sandbox/sandbox-15170.log"
 * 
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line

F: mkdir
S: deny
P: /run/user/1000/.ecore
A: /run/user/1000/.ecore
R: /run/user/1000/.ecore
C: /usr/bin/efreetd 

F: mkdir
S: deny
P: /run/user/1000/.ecore
A: /run/user/1000/.ecore
R: /run/user/1000/.ecore
C: /usr/bin/efreetd 
 * --------------------------------------------------------------------------------

>>> Failed to emerge x11-wm/moksha-9999, Log file:

>>>  '/var/tmp/portage/x11-wm/moksha-9999/temp/build.log'

here is my sandbox-15170.log, while here is my build.log.

necrose99 commented 9 years ago

deps are not sated last I looked was 12 am gmt -6 versionator https://devmanual.gentoo.org/eclass-reference/versionator.eclass/index.html tends to auto version makes dealing with versions easier , https://github.com/bobwya/bobwya/blob/master/app-backup/fsarchiver/fsarchiver-9999.ebuild https://devmanual.gentoo.org/ebuild-writing/common-mistakes/

as well need to snip moksha-9999 to moksha /usr/bin/moksha or the like point being is Enlightenment side by side though a fork , overnighting enlightenment might really piss of a user.

upstream is removing enlightenment traces over time , so I went the /configure make road, however my Linux drive is dying I need to replace, for now i'm taking a Wild but Educated guess. used the automake tools style ebuild.

Eclass https://raw.githubusercontent.com/coreos/portage-stable/master/eclass/enlightenment.eclass enlightenment.eclass >> https://github.com/fusion809/sabayon-tools/eclass/moksha.eclass (https://raw.githubusercontent.com/fusion809/sabayon-tools/eclass/moksha.eclass)

might have to Modify some of that to work better at forking from Enlightenment over , rename a few functions to be more specific, however that's a real shit can of worms... and exceedingly Likely over our heads

modified an elass to patch Kernel/s of sabayon I have form Pentoo patches based on a rather simple one from Geek sources I have , just grabs user patches and slips/applies them into a kernel

not going to lie this one could take some considerable time... and frustration , and this one might need one of the Gentoo enlightenment teams expertise , so far I've stuck with far simpler fish to fry.... when posible...