[GHC] #13113: Runtime linker errors with CSFML on Windows

[GHC]

#13113: Runtime linker errors with CSFML on Windows
-------------------------------------+-------------------------------------
        Reporter:  RyanGlScott       |                Owner:  Phyx-
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Runtime System    |              Version:  8.0.2
  (Linker)                           |
      Resolution:                    |             Keywords:
Operating System:  Windows           |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  GHCi crash        |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:  #13093            |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by Ben Gamari <ben@…>):

 In [changeset:"f41c27d3ffdddbb1afe07de1bd25205061194c93/ghc"
 f41c27d3/ghc]:
 {{{
 #!CommitTicketReference repository="ghc"
 revision="f41c27d3ffdddbb1afe07de1bd25205061194c93"
 Slighly clean up symbol loading error.

 The symbol not found error that is triggered
 during lazy-loading was a bit chaotic before.

 This reformats it a bit to:

 ```
 ghc-stage2.exe:  | E:\...\libLLVMSupport.a: unknown symbol
 `_ZN4llvm5APIntC1Ejyb'
 ghc-stage2.exe:  | E:\...\libLLVMCore.a: unknown symbol
 `_ZN4llvm5APInt14AssignSlowCaseERKS0_'
 ghc-stage2.exe:  | E:\...\libLLVMCore.a: unknown symbol
 `_ZN4llvm13ConstantRangeC1ENS_5APIntES1_'
 ghc-stage2.exe:  | E:\...\libLLVMCore.a: unknown symbol
 `_ZN4llvm14FoldingSetImplC2Ej'
 ghc-stage2.exe:  | E:\...\libLLVMCore.a: unknown symbol
 `_ZN4llvm15LLVMContextImplD1Ev'
 ghc-stage2.exe:  | E:\...\libLLVMLTO.a: unknown symbol
 `_ZN4llvm11LLVMContextD1Ev'
 ghc-stage2.exe:  | E:\...\libLLVMCore.a: unknown symbol
 `_ZNK4llvm5Value10getContextEv'
 ghc-stage2.exe: ^^ Could not load 'LLVMIsMultithreaded', dependency
 unresolved.
 See top entry above.
 ```

 I have also thought about also showing the demangled names, as it may
 be useful for the end user.

 `libgcc` seems to provide a method for this so we wouldn't need any
 extra dependency.

 Any thoughts on this or would it not be useful?

 Reviewers: austin, erikd, simonmar, bgamari

 Reviewed By: bgamari

 Subscribers: RyanGlScott, thomie, #ghc_windows_task_force

 Differential Revision: https://phabricator.haskell.org/D3027

 GHC Trac Issues: #13093, #13113
 }}}

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/13113#comment:2>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler