Bug 141152 - lam-mpi-7.1.2 fails because of missing patch file sys-cluster/lam-mpi/files/7.1.2-lam_prog_f77.m4.patch
|
Bug#:
141152
|
Product: Gentoo Linux
|
Version: 2006.0
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: hp-cluster@gentoo.org
|
Reported By: fmccor@gentoo.org
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: lam-mpi-7.1.2 fails because of missing patch file sys-cluster/lam-mpi/files/7.1.2-lam_prog_f77.m4.patch
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2006-07-20 04:50 0000
|
As per summary: The ebuild for lam-mpi-7.1.2 contains
epatch "${FILESDIR}"/${PV}-lam_prog_f77.m4.patch
in src_unpack, but there is no such file (in cvs, currently). So, an attempt
to emerge this version of lam-mpi gets
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /usr/portage/sys-cluster/lam-mpi/files/7.1.2-lam_prog_f77.m4.patch
* ( 7.1.2-lam_prog_f77.m4.patch )
same here:
lam-mpi-7.1.2.ebuild, line 43: Called epatch
'/usr/portage/sys-cluster/lam-mpi/files/7.1.2-lam_prog_f77.m4.patch'
eutils.eclass, line 190: Called die
!!! Cannot find $EPATCH_SOURCE!
!!! If you need support, post the topmost build error, and the call stack if
relevant.
# ls -l /usr/portage/sys-cluster/lam-mpi/files/
total 36
-rw-r--r-- 1 portage portage 63 Mar 3 2004 digest-lam-mpi-7.0.4
-rw-r--r-- 1 portage portage 63 Jul 13 2004 digest-lam-mpi-7.0.4-r1
-rw-r--r-- 1 portage portage 63 Jul 13 2004 digest-lam-mpi-7.0.6
-rw-r--r-- 1 portage portage 61 Sep 23 2004 digest-lam-mpi-7.1
-rw-r--r-- 1 portage portage 63 Aug 14 2005 digest-lam-mpi-7.1.1-r3
-rw-r--r-- 1 root root 235 Jul 20 01:19 digest-lam-mpi-7.1.2
-rw-r--r-- 1 portage portage 10522 Aug 14 2005
lam-mpi-7.1.1-shared-romio.patch
Fixed, sorry for the delay, I was on vacation and then at a conference. kyron
if you still want the trillium thing (despite saying you probably didn't),
please reopen the relevant bug.
(In reply to comment #3)
...
> if you still want the trillium thing (despite saying you probably didn't),
> please reopen the relevant bug.
Re-opened... just so we make official the addition of the use flag I guess (not
to confuse with the Trillium multi-chat client under Windows...some people
could get ideas...)