| Summary: | update media-video/coriander to version compatible with media-libs/libdc1394 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | RT256 <rar256> |
| Component: | New packages | Assignee: | Stefaan De Roeck (RETIRED) <stefaan> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://sourceforge.net/project/shownotes.php?group_id=17605&release_id=608487 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
RT256
2008-10-15 18:25:40 UTC
Fixed. Ebuild now in tree, sorry, I forgot checking this in a long time ago. (In reply to comment #1) > Fixed. Ebuild now in tree, sorry, I forgot checking this in a long time ago. > Thanks for updating the ebuild. Unfortunately it still complains: configure: error: libdc1394 is too old. ************************************************************************** ** Please install libdc1394 version 2.0.2 or later ** ** Source tarball and SVN at: http://www.sf.net/projects/libdc1394 ** ************************************************************************** * * ERROR: media-video/coriander-2.0.0 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2047: Called econf * ebuild.sh, line 519: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/media-video:coriander-2.0.0:20081029-170218.log'. * The ebuild environment file is located at '/var/tmp/portage/portage/media-video/coriander-2.0.0/temp/environment'. * But I have libdc1394-2.0.2 installed: ~ $ equery list libdc1394 [ Searching for package 'libdc1394' in all categories among: ] * installed packages [I--] [ ~] media-libs/libdc1394-2.0.2 (2) Should I open a new bug? (In reply to comment #2) > (In reply to comment #1) > > Fixed. Ebuild now in tree, sorry, I forgot checking this in a long time ago. > > > > Thanks for updating the ebuild. Unfortunately it still complains: > > configure: error: libdc1394 is too old. > ************************************************************************** > ** Please install libdc1394 version 2.0.2 or later ** > ** Source tarball and SVN at: http://www.sf.net/projects/libdc1394 ** > ************************************************************************** > * > * ERROR: media-video/coriander-2.0.0 failed. > * Call stack: > * ebuild.sh, line 49: Called src_compile > * environment, line 2047: Called econf > * ebuild.sh, line 519: Called die > * The specific snippet of code: > * die "econf failed" > * The die message: > * econf failed > * > * If you need support, post the topmost build error, and the call stack if > relevant. > * A complete build log is located at > '/var/log/portage/media-video:coriander-2.0.0:20081029-170218.log'. > * The ebuild environment file is located at > '/var/tmp/portage/portage/media-video/coriander-2.0.0/temp/environment'. > * > > But I have libdc1394-2.0.2 installed: > ~ $ equery list libdc1394 > [ Searching for package 'libdc1394' in all categories among: ] > * installed packages > [I--] [ ~] media-libs/libdc1394-2.0.2 (2) > > Should I open a new bug? > Actually, the ebuild is good. Thank you again, Stefaan, for your good work! I apologize for not digging deeper into my system to check the root of the problem, prior to re-opening the bug. The problem was that I had manually installed a previous version of libdc1394. After uninstalling it, coriander compiled normally. Word of caution: I configured my kernel NOT to use the new firewire stack (juju). Make sure you emerge libdc1394 with -juju otherwise coriander does not work (obviously!). Note that when emerging libdc1394 with juju use flag, there is no check for enabling the new firewire stack in the kernel. |
