couldn't find the following symbol recursionzmschemeszm5zi...

locallycompact commented 2 years ago

Summary

Hi, I'm trying to build plutus-core without haskell.nix and running in to the following linker error.

[ 43 of 201] Compiling PlutusCore.Core.Instance.Recursive ( plutus-core/src/PlutusC>

<no location info>: error:

GHC.ByteCode.Linker.lookupCE
During interactive linking, GHCi couldn't find the following symbol:
  recursionzmschemeszm5zi2zi2zi2zm5juhDHHdVvn1FQv0AeZZDtg_DataziFunctorziFoldablezi>
This may be due to you not asking GHCi to load extra object files,
archives or DLLs needed by your current session.  Restart GHCi, specifying
the missing library using the -L/path/to/object/dir and -lmissinglibname
flags, or simply by naming the relevant files on the GHCi command line.
Alternatively, this link failure might indicate a bug in GHCi.
If you suspect the latter, please report this as a GHC bug:
  https://www.haskell.org/ghc/reportabug

[ 44 of 201] Compiling PlutusCore.Core.Instance.Pretty.Common ( plutus-core/src/Plu>
[ 45 of 201] Compiling PlutusCore.Evaluation.Machine.Exception ( plutus-core/src/Pl>
[ 46 of 201] Compiling PlutusCore.Core.Instance.Pretty.Readable ( plutus-core/src/P>
[ 47 of 201] Compiling PlutusCore.Core.Instance.Pretty.Classic ( plutus-core/src/Pl>
[ 48 of 201] Compiling PlutusCore.Core.Instance.Pretty.Plc ( plutus-core/src/Plutus>
[ 49 of 201] Compiling PlutusCore.Core.Instance.Pretty.Default ( plutus-core/src/Pl>
[ 50 of 201] Compiling PlutusCore.Core.Instance.Pretty ( plutus-core/src/PlutusCore>
[ 51 of 201] Compiling PlutusCore.Core.Instance.Eq ( plutus-core/src/PlutusCore/Cor>
[174 of 201] Compiling UntypedPlutusCore.Evaluation.Machine.Cek.CekMachineCosts

Is this a known issue? Repro below.

Steps to reproduce the behavior

nix build "git+https://gitlab.homotopic.tech/horizon/horizon-plutus#plutus-core"

Actual Result

Doesn't link

Expected Result

Should link

Describe the approach you would take to fix this

No response

System info

Nixos

locallycompact commented 2 years ago

This seems to only be a problem with profiling enabled. Closing unless someone is really interested.

michaelpj commented 2 years ago

Yes, this comes up from time to time, nobody knows why :( There is a workaround: set -fexternal-interpreter for plutus-core in your cabal.project.

IntersectMBO / plutus