ebuild for imlib2-1.1.0 untars to /var/tmp/portage/imlib2-1.1.0/work/imlib2-1.0.0 but ${WORKDIR}/${P} expands to /var/tmp/portage/imlib2-1.1.0/work/imlib2 Since ${S}="${WORKDIR}/${PN} econf cannot find the configure script because it's looking in imlib2 instead of imlib2-1.1.0 ${S} should probably equal "${WORKDIR}/${P}" instead Thanks! Reproducible: Always Steps to Reproduce: 1. emerge unmerge imlib2 2. emerge sync 3. emerge imlib2 Actual Results: Error message reads: ERROR: media-libs/imlib2-1.1.0 failed. Function econf, Line 340, Exitcode1 no configure script found Expected Results: it should have compiled cleanly and made me feel like someone who is empowered with the almighty imlib2 library.
sorry, my first line should have read "but ${WORKDIR}/${PN} expands to /var/tmp/portage/imlib2-1.1.0/work/imlib2" my bad.
In the ebuild file on my system (synced 12:00pm 15-Oct-03), the definition for S is commented out. If the notes here are applied (replacing PN with P) and the line is uncommented then the build succeeds.
Exactly Right. I imagine the comment is there for the sake of documentation. Ie.. the developer knew that ${S} was being set to ${WORKDIR}/${PN} somewhere else in the build process, and put the comment there to remind him/herself.
yeah, the stuff in the ebuild that is commented out is because the ebuild doubles as a cvs snapshot ebuild and as a release ebuild ... this broke when i updated the enlightenment eclass by making S default to ${WORKDIR}/${PN} (all the cvs snapshots do this) instead of the portage default of ${WORKDIR}/${P} now fixed in cvs, thanks
