search

kunitoki / roxxorx-gentoo-overlay

Repository of cool gentoo portage ebuilds.
2 stars 3 forks source link

lightworks - source directory '${S}' doesn't exist #11

Closed ghost closed 9 years ago

ghost commented 10 years ago

Running emerge -pv cause this error:

So I decided to run: ebuild lightworks-12.0.ebuild digest

But after this operation I'm getting another error:

What should I do?

Saigut commented 10 years ago

There may be an issue in Manifest file. I regenerated the Manifest using 'ebuild lightworks-12.0.ebuild manifest' and then things seem going right.

ghost commented 9 years ago

I noticed that updated gcc and thought that was the reason of this error. (I forgot to change the gcc using gcc-config etc.) But after recompiling the whole system I'm still getting this error. :(

If I understand correctly there is a problem with variable ${S} which points to the non-existing folder.

ls -l /var/tmp/portage/media-video/lightworks-12.0/work/ -rw-r--r-- 1 portage portage 17559 11-09 20:24 control.tar.gz -rw-r--r-- 1 portage portage 62632690 11-09 20:24 data.tar.gz -rw-r--r-- 1 portage portage 4 11-09 20:24 debian-binary drwxr-xr-x 3 portage portage 72 09-24 13:07 lib lrwxrwxrwx 1 portage portage 72 11-09 20:24 lwks-12.0-amd64.deb -> /var/tmp/portage/media-video/lightworks-12.0/distdir/lwks-12.0-amd64.deb drwxr-xr-x 5 portage portage 120 09-24 13:07 usr

There is no folder named "lightworks-12.0" here. Perhaps I need to set the ${S} in ebuild file?

ghost commented 9 years ago

I found the solution for this error. According to this link: http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/upgrade-ebuild-eapis I had to add this line: S="${WORKDIR}" to the ebuild file. After this change it installs with no errors. I think this change should be included in ebuild file to avoid future problems.