Date: | Sun, 4 Nov 2018 21:46:20 +0000 |
---|---|
From: | Benjamin Welton <welton@xxxxxxxxxxx> |
Subject: | Re: [DynInst_API:] spack dyninst/package.py file changes? |
Mark,
Packages.yaml is site/user specific (at least as per my understanding).
> Spack will take the latest version from intel-tbb by default.
I do not believe this is true. Spack will only do this if no version of TBB was installed by spack already. If a site has the oldest version of TBB supported by spack already installed, that will be used with Dyninst (likely something we dont want).
Jim, if you want to give it a try my suggested changes are the following (if these work, then it is likely good to submit to spack as a pull request):
TBB Package.py:
version('2018.6', ' 9a0f78db4f72356068b00f29f54ee6bc')
Dyninst Package.py:
depends_on("tbb@2018.6:")
(then your other changes). As for going forward, I am going to suggest on Monday that we (dyninst) keeps a running github fork of spack where we make changes to the packages for dyninst. That way we have a single location that we can grant access to and allow for commits/testing
before submitting a pull request to the main spack repo.
Ben
On Sun, Nov 4, 2018 at 1:24 PM Mark W. Krentel <krentel@xxxxxxxx> wrote:
I know that dyninst will download and build TBB, elfutils, boost if |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | [DynInst_API:] [dyninst/dyninst] d7d2fd: fix doNotOverflow for int64, picked from 2b21d59, LER0ever |
---|---|
Next by Date: | Re: [DynInst_API:] spack dyninst/package.py file changes?, Jim Galarowicz |
Previous by Thread: | Re: [DynInst_API:] spack dyninst/package.py file changes?, Mark W. Krentel |
Next by Thread: | Re: [DynInst_API:] spack dyninst/package.py file changes?, Jim Galarowicz |
Indexes: | [Date] [Thread] |