Two of the paths contained in the shell scripts for the erts package under /usr/lib/erlang/erts contain the build path /var/tmp/portage somehow. Clearly after building, this path is no longer valid. Removing /var/tmp/portage from the beginning made everything work again.
George, you still looking into this one?
Well, did not really get to this before now. However I had a quick look and I issued a fix - the -r3 version in in portage now. Please test, check the changes and let me know if you have any suggestions. The wrapper scripts should be fixed now. However I do not like that many binaries have ${D} hardwired in them. I will try to get back to this at some point, but if anybody has any ideas, they are definitely wellcome. The (-r3) ebuild is protected with KEYWORDS="-*" for now, untill there is a consensus. I also added support for amd64. Looks like erlang's configure somewhat misdetects CHOST on this arch, so I needed to do some ugly wrapping. There should be a better way to deal with it, I'll try to check on that as well.. Brian: are you interested in this package? George
This workaround worked for me on x86_64 when installing. http://www.erlang.org/ml-archive/erlang-questions/200403/msg00105.html (I. e. editing makefile temporarily). /A
Hi guys. Sorry for long silence, I was mostly away on interview trips for new position. Now I am back to business for a few month before I relocate :). I just added erlang-10.2.0 to the tree (the R10B-0 version, according to discussed before renumeration to solve naming problems). Please test if you still experience this problem and let me know. If yes, I'll try to comeup with something in src_compile or src_install along the lines to what is suggested in that link. George
No responce in a long time and *many* new versions are in since then.. Closing the bug.