Hi, what are y'all thoughts on building Dyninst with a TBB other than
intel-tbb, specifically intel-oneapi-tbb ?

Spack has three providers for the virtural tbb: intel-tbb,
intel-oneapi-tbb and the full intel-parallel-studio.  I get the sense
that intel-tbb is older, to be phased out in favor of intel-oneapi-tbb.
I tried this in spack and the build failed with:

$ spack install dyninst ^intel-oneapi-tbb

-- Searching for tbb...
-- Hints: /home/krentel/tbb/install/linux-fedora26-x86_64/gcc-7.3.1/intel-oneapi-tbb-2021.2.0-t5wd6nm6yz26cs2l6bwfhmuvbo5gke6a/lib /home/kre
ntel/tbb/install/linux-fedora26-x86_64/gcc-7.3.1/intel-oneapi-tbb-2021.2.0-t5wd6nm6yz26cs2l6bwfhmuvbo5gke6a
-- Could NOT find TBB (missing: TBB_INCLUDE_DIRS TBB_LIBRARIES tbb tbbmalloc tbbmalloc_proxy) (Required is at least version "2018.6")
CMake Error at cmake/ThreadingBuildingBlocks.cmake:99 (message):
  TBB not found and cannot be downloaded because build is sterile.
Call Stack (most recent call first):
  CMakeLists.txt:30 (include)

The directory layout is totally different with intel-oneapi-tbb, but
that might be the main or only issue.

So, do you want dyninst to be buildable with intel-oneapi-tbb?

Is it worth the effort?

Do you suspect any issues beyond directory layout?

You want me to file a issue?

Thanks,

--Mark


_______________________________________________
Dyninst-api mailing list
Dyninst-api@cs.wisc.edu
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api

Reply via email to