The Right Thing is, I guess, when given a `.o` file on the command line, to read its interface file, to find what packages it needs, and include
#9938: GHC's link step needs to be told which packages to link -------------------------------------+------------------------------------- Reporter: nomeata | Owner: Type: feature request | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.11 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Compile-time | Unknown/Multiple crash | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Revisions: -------------------------------------+------------------------------------- Changes (by rwbarton): * type: bug => feature request Comment: Replying to [comment:5 simonpj]: those in any link step. A `.o` file on the command line could have come from anywhere, though; it might have been produced by compiling a C file and not have an associated interface file at all. We could record dependency information in the `.o` file in a special section, but that's a bit difficult and nonportable, and doing it just for this purpose seems a bit overkill. I believe GHC is behaving as expected here, and its behavior seems fine to me, so I turned this into a feature request ticket. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/9938#comment:10 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler