[e-users] e17 + gentoo: install issues

[Phill W. <al...@gm...>]

I've been struggling with the appropriate build environment for e17. I
had been running an older CVS (mid-last year or so), and my build
environment is significantly different now.

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 a Gentoo Forums 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 this and other errors, I unpack the source (and comment out
the AC_C___ATTRIBUTE__ line), 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:

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.

(I manually compiled the cvs-source and it died in the same place.)

I found a related bugzilla bug: http://bugs.gentoo.org/show_bug.cgi?id=142852
But, haven't quite figured out what to do with it yet.

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


Thanks,
PhillW