https://bugs.kde.org/show_bug.cgi?id=440016
--- Comment #4 from Adam Stewart <ajstewart...@gmail.com> --- > What is /opt/cray/atp/2.0.4/libApp/libAtpSigHandler.a No idea. > why are you trying to link it to valgrind? I'm not, Autotools is. > I think there's something very odd about your environment, or how you have > configured valgrind, that is causing it to try and link against that library. Welcome to trying to build software on a Cray supercomputer :) Things are generally more challenging than necessary on Cray, but all of the other software I'm building seems to be working other than valgrind. I'm not sure how to debug this one. > The full log shows that you're using > /mnt/a/u/sciteam/stewart1/spack/lib/spack/env/gcc/gcc as your compiler which > is obviously not a standard system compiler so maybe that gcc has been > configured with unusual defaults that cause it to try and link against that > library? I'm using the Spack package manager (https://spack.io). Spack uses compiler wrappers which inject flags like -L and -I based on dependencies. Note that this weird ATP thing that's getting sucked in isn't one of the dependencies. I'm guessing that this is something to do with the Cray Compiler Environment, not with Spack. Let me try building outside of Spack to see if I can reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
