[arch-general] PKGBUILD - Howto build openmpi w/o valgrind or valgrind w/o openmpi - what's the trick?
All, This seems like a chicken-and-the-egg problem that I'm not understanding. How do you build openmpi when it's makedepends requires valgrind, but you cannot build valgrind because it's makedepends requires openmpi?? Specifically: $ cat /var/abs/extra/valgrind/PKGBUILD pkgname=valgrind ... makedepends=(gdb openmpi) $ cat /var/abs/extra/openmpi/PKGBUILD pkgname=openmpi ... makedepends=(inetutils valgrind gcc-fortran) Is there some type of trick? -- David C. Rankin, J.D.,P.E.
On 06/11/2016 08:56 PM, David C. Rankin wrote:
$ cat /var/abs/extra/valgrind/PKGBUILD pkgname=valgrind ... makedepends=(gdb openmpi)
Looks like openmpi should only be an optdepends of valgrind, not a makedepends... -- David C. Rankin, J.D.,P.E.
On Sat, 11 Jun 2016 20:56:14 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
All,
This seems like a chicken-and-the-egg problem that I'm not understanding. How do you build openmpi when it's makedepends requires valgrind, but you cannot build valgrind because it's makedepends requires openmpi??
Specifically:
$ cat /var/abs/extra/valgrind/PKGBUILD pkgname=valgrind ... makedepends=(gdb openmpi)
$ cat /var/abs/extra/openmpi/PKGBUILD pkgname=openmpi ... makedepends=(inetutils valgrind gcc-fortran)
Is there some type of trick?
This is why we have binary repos. Just install one and build the other.
On 06/11/2016 09:11 PM, Doug Newgard wrote:
This is why we have binary repos. Just install one and build the other.
Yes, but sometimes you want to KISS and build from source. The key way to drop the openmpi makedepends (it is actually an optdepends), build valgrind, then build openmpi. (then you rebuild valgrind if you need openmpi support if needed) -- David C. Rankin, J.D.,P.E.
participants (2)
-
David C. Rankin
-
Doug Newgard