Re: [DynInst_API:] ExternalProject_Add and dependencies


Date: Thu, 18 Jul 2019 14:43:24 -0500
From: Tim Haines <thaines.astro@xxxxxxxxx>
Subject: Re: [DynInst_API:] ExternalProject_Add and dependencies
>> Could you send me the error message you saw?
> This is the log from our build process. The make is line 346 make -j24 search for "fatal error:" for cases where the include file is not in place yet

Looking at the CMakeLists.txt, I don't see where any dependencies are missing. I've exported the dependency graph into GraphViz, and I'm trying to examine it, but it's crazy complex. I'll let you know if I find anything there.

>> Actually, i just realised that the example i gave won't work because the
>> new build system also solved the long-standing issue of rpathing not
>> working correctly. Without a relink step during install, all rpaths are
>Good point about rpath. So what is done for fedora and rhel to enable finding dyninst libraries is installing into /usr/lib64/dyninst and ldconfig is run to add them to the library cache.  Older linux releases continue to run the older dyninst 9.3.2. For users >who want a more recent version we also have a separate toolset that has more recent versions of tools (gcc, g++, gdb, systemtap, dyninst etc) Those are installed into /opt/rh/gcc-toolset-9/root/usr/ and scl, the toolset enabling routine, adds /opt/../lib64>
>dyninst to LD_LIBRARY_PATH.

In this case, you would probably want to disable rpathing. There's no way to do that in the build interface, so you'll have to comment out the lines 5, 6, and 7 in the base CMakeLists.txt.


I'm also seeing a bunch of weird Boost errors regarding const-qualified objects. Is there a another Boost install in "/opt/rh/devtoolset-9/root/usr/include"?

Thanks.

- Tim




On Thu, Jul 18, 2019 at 7:54 AM Stan Cox <scox@xxxxxxxxxx> wrote:

On 7/16/19 19:46, Tim Haines wrote:
> Actually, i just realised that the example i gave won't work because the
> new build system also solved the long-standing issue of rpathing not
> working correctly. Without a relink step during install, all rpaths are
Good point about rpath. So what is done for fedora and rhel to enable finding dyninst libraries is installing into /usr/lib64/dyninst and ldconfig is run to add them to the library cache.  Older linux releases continue to run the older dyninst 9.3.2. For users who want a more recent version we also have a separate toolset that has more recent versions of tools (gcc, g++, gdb, systemtap, dyninst etc) Those are installed into /opt/rh/gcc-toolset-9/root/usr/ and scl, the toolset enabling routine, adds /opt/../lib64/dyninst to LD_LIBRARY_PATH.
[← Prev in Thread] Current Thread [Next in Thread→]