Build fails on Big Sur

[vthost]

I try to build revision 34ea0d1, because it still contains the json adjacency output.
The problem is only with the python part (see below), but I need exactly that. Google finds various people with this (or a similar library) problem in general, but I assume someone must have found a solution for semantic specifically already?
Thank you so much already!

[1 of 8] Compiling Language.Python.AST ( src/Language/Python/AST.hs, /Users/xyz/Desktop/git/semantic-34ea0d1dd6ac1a142e2215f097f17abeed66de34/dist-newstyle/build/x86_64-osx/ghc-8.8.1/semantic-python-0.0.0.0/build/Language/Python/AST.o )

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

<no location info>: warning: [-Wmissed-extra-shared-lib]
    dlopen(libstdc++.dylib, 5): image not found
    It's OK if you don't want to use symbols from it directly.
    (the package DLL is loaded by the system linker
     which manages dependencies by itself).

[robrix]

I think I encountered this once while working on #659, but not thereafter. Were you building with cabal or bazel? (I was building with cabal at the time, if I recall correctly.)

[patrickt]

I’m not sure how much we can do about this; this is probably a GHC+Big Sur issue. We certainly don’t have any explicit dependencies on libstdc++.