-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Triton installation fails #77
Comments
We haven't updated versions on abseil-cpp in a while, mabye do a: spack checksum abseil-cpp 20240116.2 add the resulting version line to the recipe with 'spack edit abseil-cpp' and try and build that version? |
Or alternately, specify that we want gcc@8 for triton and abseil-cpp? |
Thanks, Marc. Unfortunately, I get similar errors in both cases. For example, when building with gcc@8.2.0,
Adding the newer checksum for |
Did it actually build the latest abseil-cpp after you added the version? If so we may need to actually patch that tcp_client.cc |
Yes, I can see this line in the output during the install:
However, it seems like upgrading to |
Sure thing. Which list, specifically? |
Actually, just posting it here on the ticket should be fine. |
Here, I'm using TL;DR I updated to
|
spack install triton
fails when addingfnal_art
into a fresh spack environment. Steps to reproduce the issue:I ran this as myself on
daq.fnal.gov
, which has been upgraded to AL9. The last command fails when buildinggrpc
. The full error output is very long, but I think the relevant bit isAfter a bunch of Googling, it seems like
abseil
andgrpc
have a troubled history of not talking to each other and breaking things. This abseil issue seems to suggest some mutex destructor is missing, but I'm not sure if that's what's causing this problem.In any case, it seems like there's some incompatibility between
grpc
andabseil
in this environment. I've tried a handful of different versions of each with similar results. I also tried compiling withgcc@13.2.0
, which failed with a different error that still appeared to be related to a conflict between these two packages.Any suggestions would be much appreciated.
The text was updated successfully, but these errors were encountered: