I was trying to write an ebuild for KimDaBa, part of kdeextragear-2, an image database. A simple ebuild with no special feature failed at the beginning of make time. However, doing the same thing manually with ./configure && make && make install did the trick flawlessly. I suspect some environment variable issues. Reproducible: Always Steps to Reproduce: 1. Write a simple ebuild e.g. in media-gfx/kimdaba, see attachment 2 [details]. Make the digest: # ebuild /usr/portage/media-gfx/kimdaba/kimdaba-1.0.ebuild digest 3. emerge kimdaba Actual Results: At make time, make cannot find its files and crashes instantaneously. Expected Results: make should have found its files as normal. A simple ./configure && make && make install works fine, but the emerge refuses to function. Already tried taking out inherit kde\nneed-kde 3.1 . General info on kimdaba from http://ktown.kde.org/kimdaba/
Created attachment 21682 [details] [Buggy] Ebuild for KimDaBa
Probably this ebuild does not use the standard source directory convention. Try to find out the name and set the S variable.
Negative, the default S variable is correctly set. Setting another will just crash the config. However, I managed to make it working by writing a simple src_compile(): scr_compile(){ cd ${WORKDIR}{S} ./configure make } It seems that for some reason econf gives buggy configuration, among other things not creating a kimdaba/.deps directory, which is the reason make fails. I'll attach a new, working ebuild, output of config for ./configure and econf, and listings of the source directories after ./configure and econf. Please test the ebuild! :-)
Created attachment 21728 [details] _Working_ ebuild for KimDaBa
Created attachment 21729 [details] Configuration output from econf This is the output one gets when trying an emerge kimdaba with the [buggy] ebuild.
Created attachment 21730 [details] Configuration output from ./configure This is the output one gets when manually launching ./configure in the source directory. Among other things, gcc3 seems to be detected. This configuration results in successful execution of make later on.
Created attachment 21731 [details] File list for econf This is how the source directory looks after an emerge kimdaba with the [buggy] ebuild, notice how .deps directory is missing. Notice that make has _not_ been run (that is, it has crashed immediately not finding the .deps directory)
Created attachment 21732 [details] File list for ./configure This is how the tree looks after a successful, manual ./configure . Notice how .deps directory is present an non-empty. A following make will work.
For one S is normally defined as S=${WORKDIR}/kimdaba-1.0, so with a correct S your compile statement should not work. On another area. I found out why econf does not work. The package is broken. It has a --disable-dependency-tracking function, but it cannot actually work with disable dependency tracking.
KimDaBa works now in portage. We might close this bug.
Closing.